When you move your entire site to https there are good possibilities that you skip some key issues due to the sheer technicality of the job. Resolving those requests later- when they pile up- is time-consuming, complicated and more prone to further errors. So, it is a good practice to evaluate each step of your HTTPS migration process before you move on to the next one.
It is alright to make mistakes but…. You have to move multiple elements during HTTP to HTTPS migration process involving several repetitive, tedious steps. So making mistakes is not uncommon. The best you can do is to evaluate each phase of the migration process before you move to the next one. It helps you to precisely pinpoint the errors and resolve them then and there instead of messing up the things. Here are the common possible errors to look out for:
Challengte#1: Blocking some URLs in the robots.txt
Solution: Its super easy, thanks to Google. All you have to do is to
- Open robots.txt tester tool
- Enter/select your property
- Check if web crawlers are unintentionally blocked to crawl some (or many) URLs of your site
- You can edit the command to “Allow” the “blocked” ones or “Block” the ones that show “Allow”- as per the needs.
Further help: Though the process is self-explanatory, this offers the precise step by step explanation- https://support.google.com/webmasters/answer/6062598?hl=en
Challenge#2: The browsers releasing the mixed content warnings
Solution: There are two types of mixed content warning:
- Active mixed content warning: If your HTTPS site loads a script file over an insecure connection (or HTTP sites) it can seriously interfere with the client’s security and thus attracts severe action by the browser that blocks the URL defeating your very objective of SSL investment
- Passive mixed content: It indicates the loading of non-scripting files like images etc. over the HTTP connection. It is not as harmful as active mixed content but still attracts relatively milder actions. But why to take a chance?
How to resolve it
- Check the SRC=HTTP code in the source code of your website. (Just right-click anywhere in your site and click source code.)
- Change it with HTTPS and check again
Yes, that’s it you are done! Bravo!
Challenge #3: Security or speed - a hard choice
TTPS sites require extended communication process in order to encrypt the message before it travels across servers. This key benefit of HTTPS site adds more milliseconds thus adding more latency to your site. Gaining security in exchange of speed is an unfair trade. Fortunately, you can make it fair. There are tons of ways to speed up your site but most of them don’t deliver what they promise.
Solution: Google helps - seriously!
- So rely on the leader and check different legally speed boosting resources offered by Google itself.
- It's easy, self-explanatory and once you are here you are almost done https://developers.google.com/speed/
Challenge#4: Using 301 redirects (instead of 302)
Another major mistake is to redirect each HTTP URL to HTTPS via 301 redirect instead of temporary 301 redirects. Lack of clarity may also cause automatic 302 redirect
- You first need to check redirect on https://www.screamingfrog.co.uk/redirect-checker/ to have a wholesome view 301/302 redirects
Challenge#5: Https version not registered properly
Hope you are already aware of the need and importance of registering HTTPS version in Google webmaster tools but don't forget to repeat the process in Bing, Yahoo and other major search engines including your local search engines as well Help Google crawl and render your site by using the reader function
Challenge #6: Losing social counts
Not all social media networks will automatically move the likes, shares etc. to your HTTPS URL. Some offer this facility while for others you need to take some action and failing to do so means losing all of your hard earned fb likes, +1's and other key counts on which You have incurred a good amount of resources (cost, time and efforts)
Solution: You need to change your social button codes for the purpose
- <div class="fb-like" data-href="https://Yoursite.com/blog/The-Blog’s-Name" data-send="false" data-layout="box count" </div>
- <a href="https://twitter.com/share" class="twitter-share-button" data-counturl="https://Yoursite.com/blog/The-Blog’s-name " data-url="https://Yoursite.com/blog/The-Blog’s-Name" data-count="vertical" data-via="moz">Tweet</a>
- <div class="g-plusone" data-size="tall" data-href="https://Yoursite.com/blog/The-Blog’s-Name "></div>