February 9, 2018 | Google | by Christopher Hendrickson

Chrome 68: The Clock Is Ticking for Publishers To Migrate To HTTPS

In a post on its Security Blog yesterday Google announced that from July onwards, Chrome will mark all HTTP sites as “not secure”. This change will come into play with the release of Chrome 68, and is the latest in a large chain of steps that Google has taken to drive HTTPS adoption across the web.

Here is how the omnibox will look in Chrome 68 compared to current versions:


In making this change, Chrome users will have a clearer understanding of which websites pose a security risk to them. This means that those websites that have yet to migrate to HTTPS could see drops in traffic and engagement on their websites.

In the post Google shared strong statistics regarding the rapid adoption of HTTPS across the web:

  • Over 68% of Chrome traffic on both Android and Windows is now protected
  • Over 78% of Chrome traffic on both Chrome OS and Mac is now protected
  • 81 of the top 100 sites on the web use HTTPS by default.

Beyond avoiding the non-secure label, there are a host of benefits for publishers to migrate to HTTPS. Discover those in our free ebook:


We have also written extensively on HTTPS in the past, whether that was about the impact that WPA2 had on HTTPS, the wider role HTTPS plays in a free web, or why even websites without forms need to migrate.

Marfeel will continue to keep you updated on the latest developments like these, so be sure to subscribe to updates from our newsletter using the form below: