: How do I transition to SSL without affecting PageRank? Here at Stack Exchange we're working on moving all traffic to SSL. The reason we're not doing logged-in-users only is that one side of
Here at Stack Exchange we're working on moving all traffic to SSL. The reason we're not doing logged-in-users only is that one side of the login divide would suffer a redirect from Google every time. This happens because Google's only going to have or in the results, not both. Aside from building the SSL infrastructure (details here), the outstanding question we have is:
how do we best transition to SSL?
Here are the relevant bits of our plan (testing on small sites, moving up to stackoverflow.com):
Get SSL ready/enabled (but not linked to) on all domains
Start rendering only the <link rel="canonical"> as Start sending a 301 for all requests to (from our domains...of course we can't do anything about all the existing links pointing to us)
After a transition period, set all user cookies as secure
So the endgame is having all content delivered over SSL and all HTTP requests redirected. What we're primarily concerned with is how this will affect PageRank to our sites. We depend a great deal on traffic that comes from Google and want to ensure that doesn't take a dive as we start delivering more security to our users.
The only bits I've found on this that seem to be substantive are a comment from a Google employee on an older question along similar lines:
@Frank Yes, I'm certain that Google treats HTTP and HTTPS URLs as separate URLs for crawling, indexing and ranking (I work with the web-search team here at Google). Doing canonicalization with a 301 redirect like you mentioned is a great way to solve this :) – John Mueller Oct 23 '10
and the only webmasters video I could find: Can switching to HTTPS harm ranking? The video doesn't have a solid answer, not one I'd base the future of a company on anyway.
Is our transition plan the best way to accomplish an SSL move, at least from an SEO perspective? If there's other more recent or concrete advice around how a move like this affects Google ranking we'd love to hear about it.
More posts by @Phylliss660
5 Comments
Sorted by latest first Latest Oldest Best
I recently moved several of my sites to SSL and the pagerank was not affected either positively or negatively. I followed all of Google's guidelines, which are basically just like you described:
Get your site working smoothly with HTTPS. My biggest needed change was to only use relative and protocol relative links. For example: href="page.html" and when necessary href="//www.example.com/"
Add rel="canonical" tags and point them to the HTTPS address of your page
Use 301 redirects for all HTTP requests to send them to HTTPS
Set up both the HTTP and HTTPS sites in Google Webmaster, and monitor both closely.
About a year ago there was a bug in the permalink generating code for my WordPress site, which gets about 70% traffic from Google. The canonical tag started using the WP short URL format instead of the regular format.
Two weeks later, I found the bug when I noticed that my URLs were showing weird in the Google index. Instead of the full /999999/post-url-format-like-this/ in the results, it was showing ?post_id=99999 (or something similar).
There were no changes in traffic.
The bug was fixed, the canonical tag properly set again, and about a week later, Google had adjusted all of the indexed links back to the normal format. Painless, really.
So based on my experience, your plan should be:
Change the canonical tag to point to the HTTPS URL instead.
Google will automatically update all of the results in the index. This might take a few weeks and requires no 301 redirects. And... 95% of your traffic will be using SSL.
Redirect logged-in users that click from another site.
Since 301 redirects do remove some of the pagerank, I don't see the point in using them right away, especially since the canonical tag should take care of the Google index.
I have been part of a similar transition on a moderately high traffic website, although with a difference: all of the URLs were changed and no 301 redirects were put in place.
I monitored closely the impact on Google rankings for roughly a month, and for most key words, 2-3 positions were gained, although I'm fairly certain that was completely due to better SEO.
I couldn't see any change that could be reasonably attributed to HTTPS only.
Your plan seems spot on, although I'm a bit torn about that second step, I'd personally go straight for 301.
Why not A/B test with a small number of preferably fake questions and check the effects on those?
I believe Google ranks the first URL seen should it be a short URL, HTTP or even HTTPS unless a canonical link has been used so right they are separate rankings so 301 transition would result in some juice lost in the transition.
However as John has also said its doubtful this would hurt stack, since stack has tons authority and trust with Google.
Also for all we know Google may even increase stacks rankings for going SSL since its making the site more secure for its users which in effect increases user experience which Google strongly believe in. Though this speculation but its good to be hopeful? :)
Also:
Google’s Matt Cutts said on a Hacker News comment that those who are
interested in switching their whole web site from HTTP to HTTPS should
go ahead and do that.
Google, want to switch to HTTPS? go ahead
Hacker News, Facebook starts switching all users to HTTPS connections
Your proposed solution is the best way forward from an SEO perspective. You avoid duplicate content by using the canonical URL and the 301 redirect will transfer most of your PageRank (a small amount is lost in the redirect). Plus thanks to the strength of Stack Overflow's pages in Google I would be more then stunned if you saw any fluctuations in your rankings. Smaller sites would see a transition period in their rankings while Google got caught up with their new URLs but I don't forsee that happening to Stack Overflow.
FYI, John Meuller, the Google employee you quoted, is an active member here. With a little luck he'll give us his perspective on this.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.