Google Warns: Secure Your Site By October or Else…

Home

What’s New

Start Here

Contact

2 Create a Website Blog

Google Warns: Secure Your Site By October or Else…

Filed Under: New | 62 Comments

If you don’t want the Chrome browser scaring your visitors away, here’s what you need to know…

Pages with form fields require HTTPS encryption.
Starting in October 2017, Google Chrome will display a "NOT SECURE" warning for sites not using encryption.
This includes email opt-in forms.
Encrypted pages show a padlock and "Secure" in the address bar.

Don’t Be Afraid to Ask for Help

Let me start by saying this: if technical stuff makes you nervous, call your host and ask for assistance. They might have better suggestions. I’ll be emphasizing this throughout, so take my advice if you feel uncomfortable with any steps.

This post is more of a heads-up than a tutorial; where you host your site determines your specific actions.

Did You Receive This Email?

If you have a Google Webmaster account, you might have received an email listing pages that will show the "NOT SECURE" warning in October.

How to Get Free Encryption

LiquidWeb (affiliate link) offers free AutoSSL for many hosting plans, including high-end options like VPS and dedicated servers.
It took just 3 minutes to set up on my server.
I used the Real Simple SSL WordPress plugin to redirect all pages from HTTP to HTTPS.
Alternatively, you can manually set this up with a .htaccess file; contact your host for help.
Validate SSL here.

If Your Host Doesn’t Have AutoSSL Yet…

Consider Let’s Encrypt, a free SSL certificate option supported by some hosts (see links). Back up your site and database before making changes. Website Palace (GoDaddy) users should call support for manual installation guidance.

Why Doesn’t Everyone Support Let’s Encrypt?

Hosting companies prefer you buy an SSL certificate, but AutoSSL and Let’s Encrypt are gaining traction. Free options like these are slowly becoming more widely available.

Free AutoSSL vs. Paid SSL Certificate

I won’t attempt to explain the technical differences here…