Join our mailing list Subscribe Us

How to Enable HTTPS on A Blogger Having Custom Domain?



      How to migrate from HTTP to HTTPS on blogger blogs with custom domains? Or How to install SSL on Blogger? Do you have any questions like this in your mind? It is good news for all those who use Google Blogger; now, you can enable HTTPS on a Blogger blog with a custom domain. Enabling Blogger HTTPS means your blog has an SSL certificate. Blogger SSL helps to establish a secure connection between your blog and users. After you enable HTTPS on your blog, visitors and readers will access your blog on an HTTPS secure connection instead of HTTP. Before, this feature was limited to the Blogspot sub-domain only. For custom domain owners getting an SSL certificate for Blogger was a dream. Let’s Encrypt powers this SSL certificate.

First, you should learn about the SSL certificate. Then I’ll tell you how to get the HTTPS Blogger custom domain.

Enable Blogger HTTPS on A Blog with a Custom Domain

What is an SSL Certificate?

SSL is a short form of Secure Socket Layer that guarantees your website security. On the internet, when a user sends personal information or does a financial transaction, it must keep this personal data safe and secure. For this, we need an SSL Certificate, which ensures personal data is encrypted between the user device and web server and won’t be accessible to the third person. Learn how it works.

If a website is secured with an SSL certificate, it has an HTTPS connection. When some website believes in having an SSL certificate or web browser unable to validate the certificate, it shows a warning, as shown below.

Pretending ssl certificate https connection

Why Use An SSL Certificate / HTTPS?

Before starting implementation steps, you must know a few advantages of using a free SSL certificate (HTTPS) on a blog.

1. Google has announced a website with an HTTPS connection will rank better in SERP. It means your blog will be ahead of competitors.

2. Your blog will be marked as secured in the eyes of search engines.

3. SSL certificate enables a secure connection between your blog and visitors.

4. The blog looks more professional.

5. Your blog will not get the unsecured connection on Google Chrome and other browsers. It means you will not hesitate to open your blog.

Before you enable Blogger HTTPS, you must take off these things-

– You need to submit your blog to Google Search Console again as your new blog URL is similar to https://www.yourblog.com. Do not forget to remove the existing “Property” of this blog.

– You have to ensure all image URLs are starting with HTTPS. You have to cross-check all the old posts.

– All custom blog gadgets should be checked to have SSL connections. If a third-party blog gadget does not have an HTTPS connection, then remove it.

– Blog traffic may down for some days because Google will reindex it. So you must submit your blog and sitemap in Google Search Console. Do not forget to do the same for other webmaster tools like Bing etc.

Steps to Enable HTTPS on A Blogger Blog with Custom Domain

1. Sign in to the Blogger dashboard.

2. Pick a blog to enable HTTPS

Pick a blog to enable HTTPS

3. Go to Settings > Basic > HTTPS

Go to settings > basic > https

4. Go to HTTPS availability and select YES from Dropdown

Enable https availability YES

It may take a little longer to enable HTTPS. Refresh the web page.

5. Go to HTTPS redirect and select YES from Dropdown

Enable https redirect YES

This option ensures all of the visitors will see your blog on an HTTPS connection.

Congrats! You have successfully enabled Blogger HTTPS on a blog with a custom domain. Share your experience while implementing SSL for the Blogger custom domain. Do not forget to share your old and new posts with new HTTPS URLs.

Special Note-

This option is not available for all Bloggers. But you can take the help of your friend who can enable HTTPS on his blog if you will add him/her admin of your blog. Then he/she will be able to enable HTTPS on your blog from his/her dashboard. It may take a few hours to see the option to enable HTTPS for your blog. You should keep him/her admin until the “enable HTTPS” option available on your dashboard.

Some Fixes Are Required After Enabling HTTPS on Blogger

Analyze and Fix the Mixed Content

It is possible to have a mixed content issue after using an SSL certificate. Mixed content means your blog posts and pages have used links and images with and without HTTPS.

– Open your blog on Google Chrome

– Press Ctrl+Shift+J keys to open the Javascript console tab.

– The mixed content warning may like this.

“Mixed Content: The page at ‘https://yourcustomdomain.tld/’ was loaded over HTTPS, but requested an insecure script ‘http://<some-url>/script.js.’ This request has been blocked; the content must be served over HTTPS.”

– You visit the Google Blogger Support page to fix the errors.

You need to edit your blog posts to fix the mixed content warnings. Unfortunately, you are required to do one by one if your blog is very old. Please do it for all the uploaded images, internal and external links.

Other Important Things

– You may need to re-upload the logo, favicon, and other images in your blog/blog post.

– You may get the mixed content warning on the archive, label, and search pages. Fixed this thing with step 5d.

Edit Robots.txt

– Go to Blogger > Settings > Search Preferences

– Look for Crawlers and indexing. Here edit Custom robots.txt and add the following –

User-agent: Mediapartners-Google
Disallow:
User-agent: *
Disallow: /search
Allow: /
Sitemap: https://www.yourcustomdomain.tld/sitemap.xml

Make sure to change your domain.

Resubmit the Blog Sitemap to Google Search Console

You previously submitted the sitemap for a property that starts with HTTP, not HTTPS, so please cross-check and delete the old property and recreate a new one with HTTPS.  A Guide to resubmit sitemap to Google Search Console, Bing Webmaster Tools, and Yandex.Webmaster.

Your blog sitemap file name is sitemap.xml

and can be found at the following location –

http://yourcustomdomain.tld/sitemap.xml