The time has come for all websites to migrate to HTTPS.

Google has pushed the update back a couple time trying to avoid the massive disruption that will occur when websites start getting labeled as “Not Secure.”

Here is what you need to know:

Google and the rest of the browsers have been working on this for a long time.

Last year Google and Mozilla Firefox began to push towards universal encryption by changing the UI on their browsers. In addition to the padlock icon, any website with SSL is marked “Secure.”

The plan was that website owners would gradully adopt SSL as more and more features were being taken away.

The browesers also began marking HTTP sites “Not Secure.” This was done more gradually.

The warning started out just warning users when they were about to enter a password in an unencrypted field. 

Then in the Fall they turned up the volume even more and started marking any HTTP page with text fields “Not Secure.” Now, with the release of Chrome 68 in July, Google is cranking it up to 11.

Any website served via HTTP is going to get the “Not Secure” indicator.

What’s the Big Deal with HTTPS?

HTTP is ancient by computer standards. It’s a protocol for communication and it worked fine for a while. Unfortunately, HTTP is not secure.

When you make an HTTP connection with a website that connection is not secure. That means that anyone can eavesdrop on the connection and steal or manipulate any data passed back-and-forth.

HTTPS is secure. When you make a connection with a website the data being sent is encrypted. That essentially makes it worthless to anyone without the corresponding key.

Beyond security, HTTPS also blocks ISPs from injecting ads on your website, it is faster and performs better than HTTP and, finally, you have to have encryption in order to use HTTP/2, which is becoming more widely adopted by the day.

What do I need to do?

You need to install an SSL certificate and migrate your website to HTTPS. Before you order one though, take stock of what you need to secure.

You may just have a single domain or you may have something more complicated like sub-domains or even multiple domains, in which case you’ll want to find the right certificate.

Don’t worry, there’s a diverse set of offerings that cover just about every use case.

Next you’ll need to migrate to HTTPS, you can do this by changing the protocol in your URLs to HTTPS, then using 301 redirects.

Either way, the key takeaway is that you have until July to get an SSL certificate, lest you anger Google.

And trust me, no one wants to cross Google.