5 HTTPS Mistakes That Could Make Your Blogger Blog Varnish (Totally De-Indexed)

Recently wrote an article on how to enable FREE HTTPS on your Blogspot blog with a custom domain and many persons were afraid to enable it. Some persons did it in Blogspot and most of them attained success on it but meanwhile, I was busying experimenting and I know you would probably wonder I why I would place my blog rankings under risk!

blogger https mistakes

Well, I did it!. For the past few days, my blog was totally deindexed both on HTTPS version and on HTTP version. Why? I made some terrible mistakes out of testing HTTPS on a custom domain. But while making these mistakes I started learning new things to the extent that I got to know a lot about the power of tags in SEO.

Just 2days ago I decided to set this right, so as to get my rankings back. I did it and in just a few days my blog started getting indexed. Each post one after the other just the same way they I. Now you will ask me what I learned?

1. Doing the period of all my posts getting deindexed, my Homepage URL was getting all the keywords and ranking juice from these individual pages. How? Whenever I searched for a particular keyword such as “Free OgbongeBlog Template” I would see my homepage ranking on the first page but the real post page not indexed at all.

Which simply meant Google attributed the ranking juice of my pages to my homepage since it was the only page now indexed. It was so for every other search I conducted.

2. I got to know the power of rel=”canonical” tag in a blog. I know many persons still don’t have an idea about it. This is why I wrote an article on the SEO Importance Of Rel=’Canonical’ And How To Use In BlogSpot SEO wise speaking if you have various versions of your blog linking out and you still have not set this tag on your template properly, you are killing your blog.

Using the rel=”canonical” tag I was able to correct the difference between my HTTPS and my HTTP. At some point, I had over 150 indexed HTTP pages while I had only 9 HTTPS indexed and funny enough the only indexed HTTPS pages were also indexed under HTTP. Duplicated content (Google would have flogged me for that).

3. If you recently moved from a dot com domain to another dot com e.g from obhiabablog.com.ng to bloggingprince.com and you failed to set up 301-redirect just know you are making a terrible mistake that you need to solve in the next 24 hours.

I give thanks to Garanntor on this. When I recently switched domain name, doing the same period I moved to HTTPS. Obviously, this killed my ranking but in a few days, I got them all back and thanks to 301-redirect or domain forwarding as you may know it.

With it, I was able to completely transfer my rankings without dropping any. I even got site-links a few days after doing so.

4. Did you know there is something called Google Change of Address?. Do you know what it is used for? and Do you know you need it when you switch domain name?. Well, I got to meet this while searching for solutions.

I will show you where and how you use in this post. Just continue reading:

5 HTTPS Miskates And Solutions

1. Not Setting Preferred Version ( HTTPS or HTTP)

This is the major cause of Duplicated Content. Google doesn’t give you an option to set your HTTPS as preferred version in the webmaster’s page because according to them in 2015, Google would index the HTTPS version of your blog over the HTTP.

What is preferred version? – This is simply the version you prefer to index your pages with. Normally you find it for www and non-www but when you install HTTPS on your blog, you need to fix duplicated content.

How to set HTTPS as preferred version in blogger

Here we are going to be making use of the rel=”canonical” tag and in less than a week we should start seeing google indexing the HTTPS version over the HTTP.

  1. Go to blogger.com >> Theme >> Edit HTML
  2. Search for <link expr:href=’data:blog.canonicalUrl’ rel=’canonical’/> using CTRL + F
  3. If found, replace with <link expr:href=’data:blog.canonicalUrl.https’ rel=’canonical’/>
  4. If not found, search for <head>
  5. Paste the above code just below <head> and save

2. ALL Posts DeIndexed With Only Homepage showing.

Well, I don’t seriously think any one else will make this SEO bomb apart from me. What caused this problem for me? I was so tensed to get my pages indexed and I didn’t know the rel=”canonical” tag could also kill!. Yes. In just a few days all my pages were deindexed and only the homepage was showing.

What was my mistake?.

I set the preferred version as HTTPS but in the wrong way. I set it as “<link href=’https://www.bloggingprince.com’ rel=’canonical’/> “ which means for all pages on this blog, index them under this URL. This is why all my pages got de-indexed and only my homepage showing. What did the tag do? It simply told google that every other post page on my blog, is another version for https://www.bloggingprince.com and that every other post page should not be index. Only the URL with https://www.bloggingprince.com should be indexed.

How did I fix it? I learned more about blogger URL structure through experimenting and from there I was able to get it done in few days I was getting my ranks back. If you want to use the rel=”canonical” tag in Blogspot, do it the right way which I explained in number 1.

3. Post getting Indexed Under Old URL

You could be badly damaged by this if you recently changed the domain name of your blog. Whether from Blogspot to a custom domain or from a custom domain to another. I encountered this error when I recently changed the domain name.

My basic solution was to redirect all pages on my old domain to my new domain using JS and it worked to an extent. It gave me traffic from my old URL but did not give me my ranking juice. The only solution to this is 301-Redirect.

This solution was suggested to me a co-blogger Victor of EntClass. He got to know about this after moving his domain. Guess he learned from experience too. But wait? you should not learn from experience it could kill your blog.

The easy solution is to set up DNS 301-redirect from your domain registrar. Am really not very good at this so just ask your domain provider for it and in less than 24hours, it should be done. Mine took less, all thanks to Garanntor NG – Always providing awesome customer support.

4. Post still getting indexed under old URL after 301-redirect

Yes, I have seen situations like this when your posts will still be getting indexed under old URL even after setting 301-redirect. What simply happened! Google has a lot of pages to crawl every day and most times they crawl big websites with instantly publishing.

This takes time and due to this, it may take a long time to realize that you have set up 301-redirect (pass all the juice to my new domain permanently) – Since they didn’t index your pages, you need to fix it by telling them yourself.

Solution – Change Of Address

  1. Go to Google webmasters
  2. Verify your two websites (old and new domain)
  3. Go to the dashboard of your old domain >> Click the gear icon at the top >> select change of address
  4. In the drop down menu select your new domain, Google will check for 301-redirects ( if it shows green) agree to the other settings.
  5. Save. Changes will not occur immediately but will in a few days.

google change of address

5. I can’t See my blog – Both Versions not Indexed.

Just a few days after moving to HTTPS, I started having this problem. I faced an issue with slow indexing sometimes it took Google up to 1 week to index my post. I already provided a solution for this and you should read it immediately.

More From Author.

If you are blog developer you would feel these mistakes I made are silly but the way I see it is quite different. I made these mistakes so you won’t make them and also in case you already made them so I can provide a solution for you. HTTPS is safe and secure for blogspot users as long as you know what to do and don’t get things messed up.

Related Articles

2 Comments - Post Yours! How to? ▼


Leave a Reply