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.