Its time to move to HTTPS. July 23rd marks the day that Google will begin to put a heavy spotlight on any site without HTTPS, essentially highlighting to consumers that the site it not secure, in Chrome.
Although there has been significant improvement since the early part of this year in using SSL certificates and encrypting your HTTP, Google will be on the prowl for those existing sites that haven’t conformed to this change since their announcement, in less than a month’s time.
What does this mean for my website?
For websites who have not been following the HTTPS protocol so far, this update means that a Not Secure warning will appear in the address bar for any web pages collecting visitors data through a form. However if you have been using the HTTPS protocol thus far, then your website will not feel the affects of this update.
So, the first step to make sure you are adhering to Googles update is making sure you have an SSL certificate for your site. This could be a Let’s Encrypt, a RapidSSL or a GeoTrust certificate, and we suggest ensuring you install an SSL certificate to your site in the next few weeks. All SSL certificates offer the same level of security, however the more you choose to pay for your SSL certificate on the spectrum, the stronger level of visitor assurance you are giving to your visitors. Once this has been completed, then you must ensure you have redirected your site from HTTP to HTTPS.
By doing this, you are ensuring the safety and privacy of the users visiting your site, even if performance is not a key area for you. Essentially, Google will soon block unencrypted connections by default, making your site more difficult or virtually impossible to be found by a consumer using Chrome. This will have a significant impact on your SEO, so in order for your SEO performance to develop, this is a key step to implement.
For our users of the STORM platform, obtaining an SSL certificate is free for a Let’s Encrypt specification, where you can choose which of your sites you wish to apply it to very simply. Using the STORM server interface, you can essentially enable an HTTP to HTTPS redirect in a single click of the toggle, simply and securely.