The end of HTTP: Google is reportedly preparing surprises for Google Chrome users and Webmasters alike. From January 2017 (when Chrome 56 Stable is released) all HTTP pages will be marked as "unsafe."
To date, the company uses a neutral list for sites that do not use HTTP. All web pages that contain mixed content (HTTP and HTTPS) fall into this category.
"Chrome is currently showing HTTP connections with a neutral pointer," says Emily Schechter in a blog post.
“This does not reflect the true lack of security for HTTP connections. When loading a by clicking here via HTTP, someone else on the network can view or modify the web page before it reaches you.”
Google will deliberately begin to implement its plan gradually. Schechter reports that according to studies, users do not pay attention to the warnings that appear very often.
So Google will take other measures to encourage the use of HTTPS, such as the use of HTTPS as a positive signal for the ranking of the page.
As of December 2015, it has been adapted to system indexing and crawls HTTPS pages by ranking them better than HTTPS in the results search. The company recently announced that more than half of the pages visited with Chrome from desktops are served over HTTPS.
Last month, Google implemented HTTP Strict Transport Security (HSTS) on the google.com domain to prevent users from connecting to the insecure HTTP protocol on its main page.
