Next month, some small business websites are going to get a small but unwelcome label. Starting with Chrome 56, scheduled for January 2017, Google's browser will mark pages as "Not secure" in the address bar if they collect passwords or credit card information over a plain HTTP connection. Google announced the change in September, and said it's only the first step.
Chrome is the most widely used web browser, so this isn't a niche concern. If your site has a customer login, a payment form, or even a password field for staff to reach an admin page, it's worth checking now, before your customers start asking why their browser says your site isn't safe.
HTTP vs. HTTPS in plain English
When someone visits a website over plain HTTP, the information traveling between their browser and your site is sent in the open. Anyone positioned in between, on a coffee shop Wi-Fi network, for instance, can potentially read or even alter it. That includes anything typed into a form.
HTTPS encrypts that connection using an SSL certificate (technically TLS these days, but everyone still says SSL). The visitor sees a padlock and "https://" in the address bar. It also confirms to the browser that it's really talking to your site and not an impostor.
For years, browsers treated HTTP as neutral and rewarded HTTPS with a padlock. Google's change flips that: rather than rewarding the secure sites, it starts flagging the insecure ones.
What exactly is changing
In Chrome 56, the "Not secure" label will appear on HTTP pages that contain a password field or credit card fields. Pages without those fields won't be labeled yet.
But Google has been clear about where this is going. It has said that later releases will extend the warning, starting with HTTP pages viewed in Incognito mode, and that eventually all HTTP pages will be marked as not secure, with the same red warning triangle used for broken HTTPS. In other words, even a simple brochure site with no forms should plan to move to HTTPS.
If your website asks visitors to type anything sensitive and doesn't use HTTPS, Chrome is about to tell them so, right next to your web address.
Why it matters beyond the warning
- Customer trust. A "Not secure" label on your login or checkout page is exactly the wrong message at exactly the wrong moment.
- Search ranking. Google has used HTTPS as a small ranking signal in search results since 2014.
- Real security. Encryption protects your customers' information, and your staff's admin passwords, from being intercepted.
Getting an SSL certificate: easier and cheaper than it used to be
Not long ago, SSL certificates cost real money every year and took some effort to install. That has changed a lot.
Let's Encrypt (free)
Let's Encrypt is a free, automated certificate authority backed by a group of major internet organizations. It came out of beta in April of this year. Its certificates are trusted by all major browsers, last 90 days, and are designed to renew automatically. Many web hosts now offer Let's Encrypt with a single click in the control panel.
Your web host's certificate
Many hosting companies now include a certificate with their plans or sell one inexpensively. Check your hosting control panel before buying anything.
Paid certificates
Commercial certificates are still worth considering if you want an organization-validated or extended validation certificate, which involve verifying your business identity, or if your hosting setup can't use Let's Encrypt. For most small business brochure sites, a basic certificate is plenty.
What to check on your site
Installing the certificate is only part of the job. A proper move to HTTPS includes:
- Redirect HTTP to HTTPS so every visitor, bookmark, and old link ends up on the secure version.
- Fix "mixed content." If a secure page loads images, scripts, or fonts over plain HTTP, browsers will show a warning or block them. Update those links.
- Check forms and plug-ins. Contact forms, booking widgets, and shopping carts should all submit over HTTPS.
- Update your website platform. If you're on WordPress or a similar system, change the site address setting to https:// and update plug-ins.
- Tell Google. Add the HTTPS version of your site in Google Search Console and update your sitemap.
- Update links elsewhere. Your Google business listing, Facebook page, email signatures, and printed materials should point to the https:// address.
- Watch the renewal date. An expired certificate produces a far scarier warning than "Not secure." Make sure renewal is automatic or on someone's calendar.
Your HTTPS checklist before January
- Visit your own website and look at the address bar. Is there a padlock?
- List every page that has a login, password, or payment field.
- Ask your web host or designer whether a free or included certificate is available.
- Install the certificate and set up an HTTP-to-HTTPS redirect.
- Test pages for mixed content warnings.
- Update Google Search Console and your online listings.
- Set a reminder, or confirm auto-renewal, for the certificate.
The bottom line
Google is nudging the whole web toward HTTPS, and the nudge is about to become visible to your customers. The good news is that fixing it is usually quick and inexpensive, sometimes free. If you're not sure where your website stands or who controls its hosting, we can help you sort it out as part of a broader look at your online security. Send us a note at info@pinellasit.com.
