Due to an impending upgrade to Chrome as well as recent updates to Google ranking algorithms, I *strongly* recommend all site owners immediately update their entire site to use an SSL Certificate.  

Google’s Chrome web browser version 56 is about to be released which will include a noticeable warning on the address bar for non-HTTPS websites – in other words, websites that don’t have a SSL Certificate will be labeled “Not secure” in the browser location bar. 

For most websites without an ecommerce aspect, this was previously not seen as a requirement because sensitive data wasn’t being handled.  Security of a site itself has not changed and the sites are no less secure than yesterday, however, your visitors perception will change and some people will see find this off-putting at least and alarming at worst- possibly leading them to abandon your site altogether.

Fortunately, it’s a relatively Easy enough solution—Add an SSL certificate to your site to make it HTTPS.  SSL Certificates are purchased through your domain registrars or hosting companies and applied to your domain through your hosting account.  Many sites will need a settings change as well, for instance, in WordPress settings to define your site URL as HTTPS (https://example.com).  

SSL Certificates are sold with an ANNUAL charge for the certificate – these vary wildly in price depending on complexity and level of validation of the domain owners.  For a simple SSL that you can receive by changing a DNS setting or receiving an email at the domain owner’s known WHOIS email, here are some example prices (as of the date of publish): GoDaddy ($55.99/year), Network Solutions ($54.99/year), RapidSSL ($59/year), ComodoSSL ($76.95/year).

YNot Web is currently discounting their Standard (Turbo) SSL certificates by 40%, starting at $29/year.  For the highest savings, a 3-year term can be used.  These certificates can be used at many hosting accounts, including YNot Web, GoDaddy, HostGator, BlueHost and more.  Check your hosting provider for instructions on implementing a 3rd-Party SSL Certificate.