Blogger webmaster took a look: Blogs with customized domains can also support HTTPS.

(opens in a new tab)

Google recently announced that Chrome browser version 68, released this summer, will display all HTTP websites that have not been upgraded to encrypted protection as “unsafe to access” websites. When I saw this news (opens in a new tab), I was almost scared to death. I was a little worried. I wonder if the “Content Hacker” website built using the Blogger platform can support HTTPS encryption?

In fact, I know that Blogger already supports general blogs to use HTTPS encryption, but it has not yet supported custom domain blogs to use HTTPS settings. I have also read Wayne Fu’s article before, “Using HTTPS for Blogger’s custom URL is a path of no return, please consider it carefully (opens in a new tab)”, so I dare not rush onto this “path of no return”.

Beginning in July 2018 with the release of Chrome 68, Chrome (opens in a new tab) will mark all HTTP sites as “not secure”.

But I saw this news (opens in a new tab) again two days ago. I was a little unwilling to give up, so I searched online again to see if there is any solution? In the past, if you wanted to apply HTTPS encryption settings to a Blogger blog using a custom domain, you might need the help of a third-party CDN, but now you don’t have to be so troublesome!

Friends who use Blogger Webmaster, if you enter the “Settings/Basic” option in the background, you should see the following words:

Warning: HTTPS settings for custom domain blogs are not currently supported.

(opens in a new tab)

The system will also prompt that if you enable the HTTPS redirect function: your blog visitors will always be connected to https://originally (opens in a new tab) set site name.blogspot.com.

But it doesn’t matter. If we enter the blog backend from here (opens in a new tab), we will see a completely different scenery:

(opens in a new tab)

Taking the “Content Hacking” website as an example, you will see the following prompt:

After turning on the HTTPS availability setting, visitors can view your blog through an encrypted connection by visiting 內容駭客.

Just change the “HTTPS Availability” option from “No” to “Yes” and it will take effect in a few minutes after saving! That’s right, your blog already supports HTTPS!

Of course, you can also go back to the background and change the “HTTPS Redirect” option from “No” to “Yes”. In this way, future visitors to your blog will always be connected to the custom domain that begins with HTTPS.

It is important to note that if the HTTPS Redirect (opens in a new tab) feature is turned off: 內容駭客 visitors will be redirected via HTTP (unencrypted connection) to the target URL; visitors to 內容駭客 will connect to the target URL through HTTPS (encrypted connection).

I guess the reason why this feature has not yet been updated to the official blog backend is because the Blogger development team is still conducting some tests, right? However, this simple trick does allow my website to support HTTPS encryption. Moreover, after several days of testing, no side effects have been seen so far.

Therefore, webmaster friends who are interested may also want to give it a try! Well, I hope this will not be a road of no return, but a broad road.

★ Content Hacking Lecture Series (CHL5): How to run corporate official websites, blogs and publications [Registration now] (opens in a new tab)

★ Content Hacking Lecture Series (CHL6): How to use presentations for content marketing [Registration now] (opens in a new tab)

★ To improve your content power, please don’t miss the online course “Content Power: The Super Power of Building Brands (opens in a new tab)”

★ Photo Credit: NordWood Themes (opens in a new tab)

---

Further reading

• Blogger webmaster takes a look: SEO strategy, start with writing the “search description”
• Do you need to consider setting up your own blog in order to operate in the Chinese mainland market?
• Blogger webmaster takes a look: To pursue SEO effects, don’t forget to customize the article URL