How HTTPS Affects SEO and Why You Should Make the Move

How HTTPS Affects SEO and Why You Should Make the Move

Dr. Peter J. Meyers of Moz recently published his findings on HTTPS. Almost a year ago, Dr. Pete wrote that 30% of page-1 Google results that they studied were secure in that they were using HTTPS. He went on to reveal that recently this week, that number has peaked to 50%.

Percentage of HTTPS Results on Google Page 1

Based on what Dr. Pete wrote, it can be inferred that the steady increase without any sudden spikes are a result of people slowly accepting and converting to HTTPS and not because of Google’s constant algorithm changes.

Rank Ranger tweets

Dr. Pete and Moz justified their findings by collaborating with Rank Ranger who operate on a separate data set; which more or less generated and proved their findings. What this means is that if two tracking tools were able to come to more or less the same answer, then the both of them are more or less correct if not on to something interesting.

Percentage of HTTPS Results by the end of 2017

Dr. Pete thinks that by the end of 2017, HTTPS websites will cover at least 65% of Google’s front page SERP. Google confirmed, however, that even if more people are converting their websites to HTTPS, they have no plan (yet) to boost more ranking signals for HTTPS websites.

Dr. Pete thinks that by the end of 2017, HTTPS websites will cover at least 65% of Google's front page SERP

While Dr. Pete and Gary Illyes of Google’s exchange resulted in a polarizing statement whose validity would definitely be debated upon by people; Dr. Pete shared in his blog post that he believed in Gary and that Google is currently “…happy with the current adoption rate and wary of the collateral damage that an aggressive HTTPS ranking boost (or penalty) could cause.” I would have to agree with Dr. Pete on this one because it makes more sense for Google to take their time with these changes.

HTTPS websites are more secure according to Google and they are starting to occupy the first page of Google’s SERP. This is all well and good but the problem is that not all of the bigger websites have embraced HTTPS yet. MozCast released their data set and out of the 20 subdomains that are listed there, these are examples of websites that have not yet converted their websites to HTTPS:

MozCast data set

This might surprise a lot of you who are still on the fence about switching over to HTTPS because knowing that 20 ‘big’ websites have yet to make the switch, is it really worth it to take the leap?


I wrote an entire article on this a few years back and it is more relevant now more than ever.  More on that later.

Moving forward with HTTPS, webmasters have to remember that there’s more than the ranking aspect to consider when it comes to HTTPS. There are a lot of factors that should be considered, for example, Google will start marking non-HTTPS websites as ‘non-secure’ as soon as they start asking for sensitive information such as passwords and the like.

Dr. Pete believes that HTTPS is going to start ‘forcing’ people to convert to HTTPS. From what I understand, Dr. Pete believes that a lot of people who have yet to take make the change will start to feel pressure especially because there are some ‘risks’ involved, which I wrote extensively about in the article I linked above.

Dr. Pete recommends (and I agree with him,) that new websites should convert to HTTPS especially because security certificates are somewhat affordable and newer sites face ‘fewer risks’ when it comes to changing from HTTP to HTTPS. Dr. Pete recommends that people should at least start to secure pages that ask for sensitive information – which is a good start, to begin with.

Moving forward, how do you change your entire site from HTTP to HTTPSHere’s a brief summary of what my developer and I did for my sites before.

  1. We used the SSL Insecure Content Fixer plugin to make sure that all of our pages reflect their HTTPS status properly.SSL Insecure Content Fixer plugin
  2. We changed our MaxCDN pullzone settings from HTTP to HTTPS.
  3. We purged ALL of our caches which includes CDN’s cache so that we could pull all of the static files from HTTPS rather than HTTP.
  4. We fixed seo-hackercom’s internal caching system to work with HTTPS. To that end, we used the W3 Total Cache plugin.MozPoll on HTTPS
  5. Back then, I reviewed Cyrus Shepard’s post entitled: “The Big List of SEO Tips and Tricks for Using HTTPS on Your Website” just to make sure that we did everything right. It doesn’t hurt to make sure that everything that you’re doing is correct as it was very risky to change your website from HTTP to HTTPS – and it still is risky, like what Dr. Pete pointed out in his blog post.
  6. We deactivated our manually coded social sharing buttons and then we switched over to Ultimate Social Deux because it works well HTTPS.
  7. We made sure to renew our SSL certificate annually – and we still do. It’s an expense but it’s an expense I consider an investment and it’s worked out well for us so far.renewing our SSL certificate
  8. We started using MaxCDN’s SPDY technology which basically increased our site load speed tremendously. You can use something similar but this is what we used back then.

And that’s how we did it. We took a lot of risks back then but look at where we are right now. We’re doing well and I would love it if you were to do well yourself, if you aren’t already.

What do you think about HTTPS? Do you have any experience that you would like to share? Let’s talk about it in the comments section, I look forward to hearing from you.


Share on:
Sean Si

About Sean

is a Filipino motivational speaker and a Leadership Speaker in the Philippines. He is the head honcho and editor-in-chief of SEO Hacker. He does SEO Services for companies in the Philippines and Abroad. Connect with him at Facebook, LinkedIn or Twitter. Check out his new project, Aquascape Philippines.