Will the new Google Chrome proposal effect your website?

31st August 2017

Last year, the developers behind Google’s Chrome browser began taking steps designed to protect users and encourage companies to use HTTPS.

Starting October 2017 Chrome will show a “NOT SECURE” warning for HTTP sites.

What is HTTPS you may ask? Well, it basically means Hyper Text Transfer Protocol Secure (HTTPS). This is a secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to.
The ‘S’ stands for ‘Secure’. By having HTTPS means all communications between your browser and the website are encrypted, or ‘Secure’.

You will know if your website is secured because you’ll see a little padlock and “https” in the address bar like this:

Screen Shot 2017-08-31 at 13.14.55

If your website isn’t secure when Google make these changes, you will see this screen when you land on the site rather than your active home page:

chrome-error

This will put people off trying to access your site so you need to act fast. HTTPS is the current leading standard for secure sites, and any webmaster reluctant  change over to ‘https’ is losing ground, not to mention potentially losing the trust of their site users. Chrome flagging HTTP sites as insecure is just one step in a long list of changes soon to come intended to better protect the privacy and security of sensitive information. You may as well just get HTTPS sorted.

Additional information can be found here:

https://www.searchenginejournal.com/google-is-requiring-https-for-secure-data-in-chrome/183756/

https://searchenginewatch.com/2017/03/31/google-chrome-ssl-certificate-proposal-could-affect-millions-of-websites/

https://bisongrid.uk/starting-october-2017-chrome-will-show-a-not-secure-warning-for-http-sites/

https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn