Google is moving towards a more secure web, and it’s dragging your website with it whether you like it or not

 In Connectivity
Imagine the negative effect it could have to your business if 70% of visitors to your website were warned that the site was insecure!

Open up a new tab in your browser and go to your company website. Have a look at the address bar. Does the URL start with HTTPS? If not, then it’s possible that someone else on the network can look at or modify the site before it gets to the reader.

What is HTTPS?

Now I’m going to get a little technical, but stick with me. HTTPS is used to secure communications on the Internet. The main motivation for using HTTPS is proving the authenticity of the visited website and protection of the privacy and integrity of the exchanged data.

By contrast, HTTP is not secure and does nothing to ensure user privacy while surfing the web.

Why does it matter?

So why should you care about this? Well, Google has been pushing for all web traffic to be accessed over HTTPS for a while now. They started by providing more favourable search rankings to HTTPS websites; but they are about to take it to the next level.

From January 2017, password or credit card form fields on non-encrypted sites will be labelled ‘not secure’ in the Chrome web browser; and, eventually, all HTTP pages will be labelled non-secure.

Treatment of HTTP pages with password or credit card form fields in Chrome

Whether this sort of security labelling will roll out to other browsers (e.g. Safari, Firefox, Internet Explorer) remains to be seen; but ProITS isn’t waiting around to find out because 70% of our current website traffic is Chrome-based.

Imagine the negative effect it could have to our business, and to yours, if 70% of visitors to your website were warned that the site was insecure!

Eventual treatment of all HTTP pages in Chrome

Not only would our readers likely turn tail and leave straight away; but, as an IT company who often preaches the importance of security, we’d look pretty silly.

What can you do about it?

We’ve already done the work required to secure our website – you can see the HTTPS in the address bar above this article; so we’re in the clear now, no matter what Google’s timeline turns out to be for rolling out a ubiquitous HTTP security warning.

My advice would be to do yourself a favour and secure your website.

This should be relatively inexpensive to do but you’ll need to contact your website developer to ask them for a quote.

If you you’re no longer in regular contact with your web developer, or you’re unhappy with the figure they quote you, get in contact with ProITS and we can help you move your site to HTTPS.

Recommended Posts
Various web CMS platforms