By Scott Thomas
Not surprisingly, Google made a lot of headlines with its announcements in 2017 and in February of this year that, as of next month (July, 2018) their Chrome web browser would start marking sites “Not Secure” if they used HTTP instead of HTTPS. There are some good reasons for this, but that isn’t the purpose of this post. Wouldn’t it be nice to be able to get a free HTTPS website? Keep reading!
Indeed, going back to 2014, Google has stated that it uses HTTPS as a ranking signal. In other words, all other things being equal, HTTPS sites may rank higher than HTTP sites. Next month Google ups the ante, actually marking HTTP sites as “Not Secure.”
What’s an innkeeper (or other small business) to do?
Fundamentally there are two options for obtaining a site that uses HTTPS. First, you (or your web designer, web hosting company, or a consultant) can purchase a secure certificate and install it on your server. Typically this requires an annual expense to keep the certificate up-to-date.
Second, there is an option for a free HTTPS website. There is more than one way to accomplish this, but I want to point out one that is not only free, but provides additional benefits for your site, as well.
That is to use the Cloudflare platform. Cloudflare has an interesting background, worth a read. For us, it is enough to understand that it acts as sort of a buffer for your site. When a visitor comes to a site using Cloudflare, they see parts of the site served up by Cloudflare (to speed things up) and part from your site (things that might change). Cloudflare also intercepts attacks on your site, and blocks many of them. You can see all of this in your Cloudflare Dashboard.
Now it is possible to set up a free HTTPS website through Cloudflare as well.
How it works
If you just want to know how to install it, skip to the next section. Keep reading to see how it works.
In its normal setup, Cloudflare walks you through the process of changing your site’s DNS server address (DNS is the system that let’s visitors put “yoursite.com” into a browser instead of numbers like 216.58.194.110. So, when you type in “yoursite.com” the browser goes to the DNS server (they are all over the world) and asks it whose address is matched to “yoursite.com”. The answer comes back “216.58.194.110” so off it goes to that address. When Cloudflare has you make this change to your DNS settings, it puts itself (Cloudflare) between the visitor and you, so that the visitor puts in “yoursite.com” but instead of DNS sending back 216.58.194.110, Cloudflare’s DNS sends back 198.41.215.162 so the browser comes to Cloudflare, and then it does some magic — it filters out bad stuff, and serves up parts of your website that it stores at Cloudflare, and forwards the browser to your real website for the rest.
For a secure (HTTPS) site, you can see that we actually need security between the visitor and Cloudflare, and also between Cloudflare and your site. Cloudflare issues its own secure certificate for the first part, and gives you a certificate to put on your site that covers the second part.
How to Set Up HTTPS with Cloudflare
For our purposes, we’ll assume your site is hosted by a company that allows you to use CPanel to manage the site. The same thing will work with other hosting management methods, but that is beyond the scope of what we can cover here.
Enjoy your free HTTPS website!