Thursday, December 17, 2015<\/p>\n
\n At Google, user security has always been a top priority. Over the years, we’ve worked hard to \n As a natural continuation of this, today we’d like to announce that we’re adjusting our indexing \n Although our systems prefer the HTTPS version by default, you can also make this clearer for other \n We’re excited about taking another step forward in making the web more secure. By showing users
\n promote a more secure web and to provide a better browsing experience for users.
\n Gmail<\/a>,
\n Google Search<\/a>,
\n and YouTube have had secure connections for some time, and we also started giving a slight
\n ranking boost to HTTPS URLs<\/a> in search
\n results last year. Browsing the web should be a private experience between the user and the
\n website, and must not be subject to
\n eavesdropping<\/a>,
\n man-in-the-middle attacks<\/a>,
\n or data modification. This is why we’ve been strongly promoting
\n HTTPS everywhere<\/a>.\n<\/p>\n
\n system to look for more HTTPS pages. Specifically, we’ll start crawling HTTPS equivalents of HTTP
\n pages, even when the former are not linked to from any page. When two URLs from the same domain
\n appear to have the same content but are served over different protocol schemes, we’ll typically
\n choose to index the HTTPS URL if:\n<\/p>\n\n
rel=\"canonical\"<\/code> link to the HTTP page.<\/li>\nnoindex<\/code> robots<\/span> meta<\/code> tag.<\/li>\n
\n search engines by redirecting your HTTP site to your HTTPS version and by implementing the
\n HSTS header<\/a>
\n on your server.\n<\/p>\n
\n HTTPS pages in our search results, we’re hoping to decrease the risk for users to browse a website
\n over an insecure connection and making themselves vulnerable to content injection attacks. As
\n usual, if you have any questions or comments, please let us know in our
\n webmaster help forums<\/a>.\n<\/p>\n