Moving custom domain names from http to https in Blogger

Google had been pondering and emphasizing on blogs, websites, e-commerce and online business owners operating on (HTTP) to move their businesses to (HTTPS) as the most advanced and secure communication over a computer network, being a widely used on the internet. Although, moving HTTP to HTTPS was since made available for BlogSpot and just recently, Google official released the availability of (HTTPS) for Blogger blogs with custom domain names, that was formally using (HTTP). 

Whether you’re blogging with other CMS or blogging with Blogger blog (Blogger custom domain name), adhering to Google instruction by moving your website from (HTTP) to (HTTPS) is an “adaption of a secured communication” which the data sent is encrypted by Secured Socket Layer (SSL) providing three extra layer of connections. 

The addition of “S” to HTTP – (Hypertext Transfer Protocol) makes it Hypertext Transfer Protocol Security – HTTPS, and that’s the advancement or version of security which brings communication protocol between browser (users’ computer) and the encrypted site, protecting users’ integrity and confidentiality.

Three layers of protection by moving from HTTP to HTTPS

The migrating of sites from HTTP to HTTPS instruction was made by Google, and October 2017 was said to be the deadline.
We encourage you to adopt HTTPS in order to protect your users’ connections to your website, regardless of the content on the site” – Google.
The adoption of (HTTP) to (HTTPS) via (TLS) provides three key layers of protection which includes:
1. Encryption – encrypting the exchanged of data to keep it secure from eavesdroppers. While user is browsing the website, nobody can listen to their conversation, track their activities or steal their information.
2. Data Integrity – data cannot be modified or corrupted during transfer, intentionally or otherwise without being detected.

3. Authentication – protect s against middle man attacks, build user trust and prove that your users communicate with the intended website safely which translates into other business benefits.
Security of a sites is one ranking factors considered by Google, thats why in 2014, Google rolled out an updated algorithms across the board in favor of HTTPS secured encrypted websites. As a lightweight component of ranking then, sites with HTTPS experiences a slight ranking increases. 

In 2015, Google stated that HTTPS ranking boost may serve as a tie breaker – if your competitor’s website is HTTPS and yours isn’t, Google will most likely rank theirs over yours. 

Currently, 50% of Google page on organic search result feature an HTTPS sites, and Google has encourages webmasters to make the migration to a secure encrypted HTTPS and has been giving an increasing amount of weight in ranking boost to websites that are HTTPS.
Interestingly, in a study conducted by Brian Dean, SEMRush, Ahrefs, SimilarWeb and MarketMuse, there was a moderate correlation between HTTPS and higher ranking, reflecting what Google had already confirmed – “it would act as a tie breaker, not a major ranking factor”. 

Searchers looking at the search result may be force to click on secured sites as a signal of trust and authority since according to GlobalSign survey, 84% of users would abandon a purchase if data was sent over an insecured connection since large majority are concern about their data being interpreted or misused online.

      Google Chrome version 62 on October 2017, started labeling sites with HTTP as ‘Not Secure’ within the URL bar, and has stared changing HTTP security indicator to the red tringle used for broken HTTPS when enter text into a form on an HTTP page, and for all HTTP pages in incognito mode. This new warning is the part of a long term plan to mark all pages served over HTTP as “not secure”. 
      Started from September till December 2017 period of Google HTTP to HTTPS migration instruction deadline, my Google Blogger blog (with 'no HTTPS Availability') SEO has been dropping drastically in-spite how much content I was adding and optimizing the content. 

      This shows that Google didn't spare its own Blogger sites with custom domain name with the “Non secured” and non encrypted connection label with its effect. Thanks to Google who finally introduces HTTPS Availability at the dying minute to it own Blogger dashboard for blogs with custom domain names.

      Advantages of Activating HTTPS Availability in Blogger Blog


      The importance of turning on HTTPS availability in Blogger blog is not just subject to only Blogger blog, but to all other web-portals on the web. Below are the following reasons why HTTPS is most preferred to HTTP
      • Google personally emphasis all blogs, websites, e-commerce sites and anything web-portals with HTTP to activate or move to HTTPS.  
      • Turning on custom Blogger blog from HTTP to HTTPS encrypted connection makes your blog more professional. 
      • Makes a secured connection between your blog and the visitors.
      • Improves your blog search engine ranking.
      • Enable Secure Socket Layer (SSL) of your blog.
      • Improve your blog search engine result pages (SERP).

      Turning on HTTPS Availability Setting in Blogger blog


      Before moving your Blogger blog to a secure encrypted connection (HTTPS), you have to note that only two things involves, and you are required to tick them from “NO” to “YES”. And that is;
      • HTTPS Availability – (Tick “NO” to “Yes”)
      • HTTPS Redirect – (Wait for 2hrs to automatically set from “NO” to “YES”)
      1. Log into your Blogger blog dashboard.
      2. Choose the blog you want to update.

      3. On the left sidebar, click on ‘Settings’.

      4. Scroll down the setting panel to ‘HTTPS’.

      5. Turn on ‘HTTPS Availability’ to “YES”.
      move blogger blog from http to https encrypted connection

      By turning on (YES) ‘HTTPS Availability’ of your Blogger blog, you now allow visitors to view your blog over an encrypted connection by visiting for example, or 
      6. At the initial time of turning on HTTPS availability from “NO’ to “YES”, your blog will try to save the setting while the page get refreshed. At that moment, you’ll see a notification on the HTTPS Availability tab like this;
      HTTPS Availability is being processed. Try again later”. 
      You have to leave the HTTPS availability setting to the already turned ON – (YES) tab.

      7. Now, its time for ‘HTTPS Redirect’ – to enable visitors stumbling your blog from HTTP server (unencrypted connection) automatically redirect to HTTPS encrypted connection version of your blog.
      You have to note that the HTTPS availability setting you've just turned (YES) will affect your blog HTTPS Redirect setting. 

      The HTTPS Redirect setting at while still on the ‘NO’ option will turn un-clickable, and will be displaying on it tab as;

      This setting is unavailable while HTTPS Availability is processing. Try again later”.

      See image bellow….
      move blogger blog from http to https encrypted connection1

      At this point, just shut down your system and check back later while the system process or synchronized itself, ensuring all of your blog content, files and images re well synchronized and be served to HTTPS encrypted connection.

      That’s exactly want I did, after about few hours, I visited back my Blogger dashboard >> Settingto >> HTTPS Availability and HTTPS Redirect settings only to discovered that the un-clickable HTTPS Redirect – “NO” setting has been automatically turned to “YES”.

      Thereafter, I proceeded immediately to view my blog on a browser, and discovered that my blog has already started operating on (HTTPS) encrypted connection.

      8. After successfully moving your blog (pointing HTTPS Availability and HTTPS Redirect to ‘YES’), you’ll see a massage like this from your blogger dashboard;

      Your HTTPS settings have changed. All visitors are now able to view your blog over an encrypted connection by visiting Existing links and bookmarks to your blog will continue to work”.

      And remember, even while turned on both ‘HTTPS availability’ and ‘HTTPS Redirect’, if eventually, HTTPS Redirect is later turned off – ‘NO’, visitors to your blog will be served over HTTP, being un-encrypted connection.

      In conclusion, while Google gave October 2017 as HTTPS adoption deadline for all blogs, websites and online service providers, many bloggers using custom domain names blogging with Blogger blog started rushing and moving their Blogger blogs from HTTP to HTTPS with the help of Cloudflare. Little did they knew that Google who gave this instruction wasn't foolish to neglect it own Blog – Blogger and the users.

      So now, what’s would be the faith of those unsettle bloggers who rush-fully moving their blogs to HTTPS using Cloudflare? Should they remain there or retard back to turn on HTTPS Availability and HTTPS Redirect from their Blogger dashboard? 

      I'm quite aware of the disadvantages this malicious migration, which  according to most of those who moved, Blogger HTTPS using Cloudflare is full of poor redirection, inability to index sitemap with HTTPS URLs, and blog SEO falling drastically.
      That’s why Patient they say, is a virtue. To those who hold on to Google without rushing to migrate their Blogger blogs to HTTPS using Cloudflare, they should be dancing Shekem by now – Lol, and should be able to easily move their Blogger blogs from HTTP to HTTPS secured encrypted connection, even with the help of this article.

      Hence, that comes to the end on this article - moving (turning on) blogger blog with custom domain name from HTTP to HTTPS. Pls, kindly share with friend and connection using the social media share buttons bellow. 


      1. Thank you for this explanation
        Now I've applied the lesson on my blog and it worked

        1. I'm glad you did got it correct @ Maryfa. Enjoy secured (HTTPS/SSL) internet network.

      2. Okay.. I'm glad you found value

      3. I’ve read some good stuff here. Definitely worth bookmarking for revisiting. I surprise how much effort you put to create such a great informative website. Learn more


      Non related comments and comments with promoted links will be disapproved.