Google Chrome 62 and HTTPS: A Quick Guide

HomeUncategorizedGoogle Chrome 62 and HTTPS: A Quick Guide


Recently, we let you know that Google Chrome 62 with its HTTPS (HyperText Transfer Protocol Secure) focus were on its way – and that if your site hasn’t been upgraded to the HTTPS standard, you could be in danger of experiencing plummeting Google rankings and a corresponding loss of traffic and conversions.

While Chrome 62 has released to the stable channel, Google is still working away at the HTTPS feature through their Field Testing process. But rest assured, a full public rollout is imminent.

You can view our report here, but the change will mark any non-HTTPS site that asks for a user password or credit card information with a “Not Secure” warning that is likely to scare off potential customers. We’ve explained how this functionality operates and the inevitable consequences thereof, but many of you may still be scratching your head over the more technical aspects of the HTTPS protocol.

Fear not! If you’ve been hoping to wrap your head around this before committing your business site to a changeover, below we’re going to give a technical – but succinct – explanation.

How Does HTTPS Work?

Back in the day, so to speak, network admins knew they wanted and needed an information exchange procedure. A protocol that was reliable and that would enable clients and servers to “speak” to one other.

Hence, HTTP (HyperText Transfer Protocol) was born.

However, as the internet matured, the necessity for a more secure method of information exchange became clear and paramount. And that’s where HTTPS comes in. The new procedure simply builds on what was established by HTTP – clients and servers still “talk” the same way but an encryption layer is involved.

Specifically, that layer is Secure Sockets Layer (SSL), also known as Transport Layer Security (TLS). The purpose of this security layer is the following:

  • Verification – SSL ensures the authenticity of the server you’re communicating with.
  • Privacy – All information exchanged is “coded”, and only the sender and the recipient (the server) can decipher the coded message. Even if your message is intercepted by a hacker, the data will remain encrypted.

As you can see, it’s clear why Google views HTTPS to be such a crucial cog to the future of websites. Their reasoning for baking it into Chrome 62 is strong.

Of course, as we’ve mentioned, on the business side, you have equally strong reason for ensuring your site is upgraded to the HTTPS standard going forward.

Fortunately, here at Marketing Breakthroughs, we’re equipped to help. As the premier Ottawa SEO and website optimization company, we’re primed to prepare your business site for Google Chrome 62 and HTTPS.

Contact us now to get started!

Written by

Founder and CEO