May 6, 2018

How to Turn on HTTPS for Blogger Blog with Custom Domain

Google has been offering HTTPS for subdomains under blogger (e.g. As for custom domains, for sometime, the only available methods were either to use alternative means like Cloudflare or an unannounced method involving Blogger in Draft mode. These methods, while working, were not so ideal. 

It took a while, but Google has now finally and properly extended HTTPS to blogger websites using custom domains too.

To turn on, simply go to Settings > Basic. Look for the "HTTPS" section, there will be two settings as shown below.

Picture showing where to turn on HTTPS for custom domains in blogger websites
Turning on HTTPS for custom domains in blogger websites

Both settings should be quite self explanatory with the descriptions provided and will be set to "No" initially. 

Start by turning on the setting "HTTPS availability". This should result in a message being displayed "HTTPS Availability is being processed. Try again later." Don't panic. What this means is just Blogger processing the request backend. Give it about 10 to 20 minutes before refreshing and the message should no longer be there. 

You can now also turn on the setting "HTTPS redirect" if you want to enforce HTTPS, which is highly recommended anyway.

After this, it is time to check for any issues on your website. Start by confirming that HTTPS is indeed loading. In your browser, you should see the "Secure" lock and https in the address like below.

Photo showing secure lock displayed in browser after turning on HTTPS for custom domain
Secure lock displayed in browser after turning on HTTPS for custom domain

Next, check the website for any Mixed Content errors, like the one below. If you are using Chrome, you can use the Developer Console (Ctrl-Shift-J) to check. 

Photo showing an example of Mixed Content error after turning on HTTPS for custom domain
Mixed Content after turning on HTTPS for custom domain

For most cases involving image and video links to external websites, you can simply change the address from HTTP to HTTPS. 

If you still see any Mixed Content errors, it could be a site wide link in the template. Simply go to the template (Theme > Edit HTML) and change any HTTP to HTTPS. You can also refer to the Google Page for other suggested Mixed Content fixes

If you are using Google Search Console, remember to add a new property for the https version of your website, as the Search Console treats http and https separately.

The only issue I have discovered so far is the Mixed Content error message in the screenshot above for does not seem to be solvable directly, as it is embedded within and called by the blogger template. Not sure if a change in template will resolve. Something that I will have to test separately.

No comments:

Post a Comment