We’ve just hit an important milestone: Google chrome is now displaying a Not Secure warning for sites that don’t make use of SSL certificates.
If you haven’t heard of SSL whatsoever, here’s your chance to read about how it applies to you and your website, WordPress or otherwise.
Introduction to SSL
The basic gist behind your website having an SSL certificate is that it allows visitors to your site & your website to communicate back & forth securely. Information sent between a user & your site being encrypted can be a huge advantage.
Using SSL with your WordPress login & administrative panels, and contact forms is an immense security benefit.
The secure padlock in your browser has become somewhat ubiquitous — you only notice when it’s missing or screams something ugly. With the most recent chrome change, any site not using SSL is going to output a rather ugly error, which, over time will get increasingly uglier with Firefox & Chrome.
The good news is we’ve done all of the difficult work in getting SSL fully operational. Now’s the time to enable it.
Setting up WordPress to use SSL
The change from non-ssl to SSL only takes a few moments, and we’ve compiled a reasonably thorough document on the topic over at SSL for WordPress which you should review & implement.
If you’re hosted at Fused, we took the liberty earlier last year to ensure that we had 100% coverage for Let’s Encrypt SSL certificates for all of our web hosting clients, so while the error might appear scary it takes all but 15 minutes to get your WordPress site loading over SSL.