Tag Archives: google

+John Mueller Hi John, does the rating of the SSL certificate impact the ranking boost? For example does a A rating HTTPS SSL certificate give a bigger ranking boost than a B rating SSL certificate? Or as long as the SSL certificate is valid and comes from a good authority (green locker) there is no ranking boost difference on class A, A-, B, C certificates?

Indexing HTTPS pages by default

At Google, user security has always been a top priority. Over the years, we’ve worked hard to promote a more secure web and to provide a better browsing experience for users. Gmail, Google search, and YouTube have had secure connections for some time, and we also started giving a slight ranking boost to HTTPS URLs in search results last year. Browsing the web should be a private experience between the user and the website, and must not be subject to eavesdropping, man-in-the-middle attacks, or data modification. This is why we’ve been strongly promoting HTTPS everywhere.

As a natural continuation of this, today we’d like to announce that we’re adjusting our indexing system to look for more HTTPS pages. Specifically, we’ll start crawling HTTPS equivalents of HTTP pages, even when the former are not linked to from any page. When two URLs from the same domain appear to have the same content but are served over different protocol schemes, we’ll typically choose to index the HTTPS URL if:

  • It doesn’t contain insecure dependencies.
  • It isn’t blocked from crawling by robots.txt.
  • It doesn’t redirect users to or through an insecure HTTP page.
  • It doesn’t have a rel=”canonical” link to the HTTP page.
  • It doesn’t contain a noindex robots meta tag.
  • It doesn’t have on-host outlinks to HTTP URLs.
  • The sitemaps lists the HTTPS URL, or doesn’t list the HTTP version of the URL
  • The server has a valid TLS certificate.

Although our systems prefer the HTTPS version by default, you can also make this clearer for other search engines by redirecting your HTTP site to your HTTPS version and by implementing the HSTS header on your server.

We’re excited about taking another step forward in making the web more secure. By showing users HTTPS pages in our search results, we’re hoping to decrease the risk for users to browse a website over an insecure connection and making themselves vulnerable to content injection attacks. As usual, if you have any questions or comments, please let us know in the comments section below or in our webmaster help forums.

Source http://googlewebmastercentral.blogspot.ch/2015/12/indexing-https-pages-by-default.html

Google Code Shutdown

As previously announced, most of Google Code will become read-only on August 25th, 2015.

We are still working with Google-affiliated projects (e.g., /p/chromium and /p/android) to get them migrated to other tools and make their projects read-only by the end of the year. These projects will remain read-write until we can transition all their data off of Google Code.

What will happen to the data?

Google Code data will still be accessible, just read-only. You will be able to search for and browse project issues, sync source data, and so on. The Export to GitHub feature will still work as advertised.

However, during this time you will not be able to modify projects. For example: create new issues, push code changes, or even modify admin settings. If you need some administrative action taken, such as deleting a project or setting up an automatic redirect URL, please contact us. (Instructions will also be linked from the /admin page of for project administrators.)

How long will the data remain available?

Google Code’s data will remain online for a long time.

Until January 2016 the Google Code Project Hosting service as it exists today will continue to be available. And you will still be able to use version control clients like git, hg, or svn to access project data.

After January 2016 you will no longer be able to access source code from a version control client; however project data will still be available. We will also be offering project data in more convenient formats for export such as JSON and .zip files. Archived project data will be available throughout 2016 and beyond.

Note that only public data will be archived. If your project has private data, such as issues with the Restrict-View-* label, you will no longer be able to browse those project resources next year. (Public downloads, issues, wikis, etc. will be available.)

Most importantly, project URLs (e.g. http://code.google.com/p/vim) will continue to work, although links to raw source code likehttps://vim.googlecode.com/hg/README.txt will not. But again, Google Code will continue to work as normal until at least January 2016.

Questions?

If you have any questions, please contact [email protected].

Map Reduce: A really simple introduction

Ever since google published its research paper on map reduce, you have been hearing about it. Here and there. If you have uptil now considered map-reduce a mysterious buzzword, and ignored it, Know that its not. The basic concept is really very simple. and in this tutorial I try to explain it in the simplest way that I can. Note that I have intentionally missed out some deeper details to make it really friendly to a beginner.

Read the full article http://ksat.me/map-reduce-a-really-simple-introduction-kloudo/

Continuing Public/Private Surveillance Partnership

The Continuing Public/Private Surveillance Partnership

If you’ve been reading the news recently, you might think that corporate America is doing its best to thwart NSA surveillance.

Google just announced that it is encrypting Gmail when you access it from your computer or phone, and between data centers. Last week, Mark Zuckerberg personally called President Obama to complain about the NSA using Facebook as a means to hack computers, and Facebook’s Chief Security Officer explained to reporters that the attack technique has not worked since last summer. Yahoo, Google, Microsoft, and others are now regularly publishing “transparency reports,” listing approximately how many government data requests the companies have received and complied with.

Read more at
 
https://www.schneier.com/blog/archives/2014/03/the_continuing_.html