Website security
Andrew Talbot
Andy

Non-HTTPS sites are penalised

Don't be left behind, safety first.

Google marking non-HTTPS sites as ‘not secure’

After years of pushing for ‘secure by default’ web sites, Google now identifies insecure sites in the Chrome browser. After marking all sites that have not migrated to HTTPS as “not secure”, the company rolled out its Speed Update.

This move coincided with the release of Chrome 68 and looks like this in a user’s browser:

Effective July 2018, Google’s Chrome browser will mark non-HTTPS sites as ‘not secure’

Google has been pushing webmasters to make the change to non-secure web sites for a long time now – including suggesting small rankings boost as a further incentive to shift. The campaign has proved successful, according to Google’s blog post:

  • 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

Depending upon the size of a site and the scope of the project, a migration from HTTP to HTTPS can be quite an undertaking.