HTTP HTTPS Migration Gone Wrong - Please Help!
-
We have a large (25,000 Products) ecommerce website, and we did an HTTP=>HTTPS migration on 3/14/17, and our rankings went in the tank, but they are slowly coming back. We initially lost 80% of our organic traffic. We are currently down about 50%.
Here are some of the issues. In retrospect, we may have been too aggressive in the move.
- We didn't post our old sitemaps on the new site until about 5 days into the move.
- We created a new HTTPS property in search console.
- Our redirects were 302, not 301
- We also had some other redirect issues
- We changed our URL taxonomy from http://www.oursite.com/category-name.html to https://www.oursite.com/category-name (removed the .html)
- We changed our filters plugin. Proper canonicals were used, but the filters can generate N! canonical pages. I added some parameters (and posted to Search Console) and noindex for pages with multiple filter choices to cut down on our crawl budget yesterday.
Here are some observations:
- Google is crawling like crazy. Since the move, 120,000+ pages per day. These are clearly the filtered pages, but they do have canonicals.
- Our old sitemaps got error messages "Roboted Out". When we test URLs in Google's robots.txt tester, they test fine. Very Odd.
- At this point, in search console
a. HTTPS Property has 23,000 pages indexed
b. HTTP Property has 7800 pages indexed
c. The crawl of our old category sitemap (852 categories) is still pending, and it was posted and submitted on Friday 3/17 - Our average daily organic traffic in search console before the move was +/-5,800 clicks. The most recent Search Console had HTTP: 645 Clicks HTTPS: 2000 clicks.
- Our rank tracker shows a massive drop over 2 days, bottoming out, and then some recovery over the next 3 days.
- HTTP site is showing 500,000 backlinks. HTTPS is showing 23,000 backilinks.
I am planning on resubmitting the old sitemaps today in an attempt to remap our redirects to 301s.
Is this typical? Any ideas?
-
our dev team has requested to 302 initially and then 301 as the final solution. Could this cause a problem for the temporary 302?
-
Looks like you've done a sterling job GWMSEO. Well done!
I deal with a lot of small sites where the decision to move from http to https was made for them... by Shopify (many without them even realising). Some of these sites take months to recover. So, to see recovery within a few weeks is a good result.
Once question I have for you: how have you resolved the backlinks issue (your observation #6)?
What I have observed is that ahrefs doesn't associate the old (http) backlinks with the new version (https). I believe this then impacts backlink profile and subsequently MOZ Domain Authority, which then impacts rankings and traffic.
301 redirects ensure you don't lost the traffic, but it doesn't move the backlinks from http to https.
Nobody has been able to confirm or deny my suspicions yet. So:
- Do you (or anyone in the MOZ community) know if these lost backlinks DOES impact Domain Authority?
- Is there any way to fix it, other than go through all the old backlinks and manually change to https?
Murray
-
Thanks to all for the help. Our rankings are climbing back. We should be back to status quo in +/-2-3 weeks after the move.
-
Nice, good job! I would double check with your CDN provider to make sure implementation was done correctly according to their process. Unless you're saying you discontinued use of the CDN when you switched?
I wouldn't panic, just make sure your team knows that you can't control the rate at which Google re-indexes the website and that it's still early in the process to tell if there is an issue somewhere. Let Google do their thing and then once your traffic and rankings seem more regular, reevaluate. At that point I would add HTTP/2 support if possible and measure the impact from that because that provides some additional benefits such as a boost to site speed.
-
Thanks for the punch list. Our rankings turned around some when we submitted the old http sitemap.
- Images only on HTTP in CDN. HTTPS, No CDN.
- Yes
- Yes. (I was a stickler on this one)
- Yes
- Yes, Yes, Yes.
- Yes
- Yes, we fixed that.
- Yes. Initially our https redirects were 302 (Not on me, LOL.). We resubmitted our old (http) sitemap file today to crawl so that Google can pick up the change.
- Yes
- Yes
- No disavow file. Our backlink profile is remarkably squeaky clean. TF-57, CF-47
Bonus: Yes.
-
1. Are you using a CDN?
2. Did you update all your internal links to https?
3. Did you update all of your canonical tags?
4. Did you update all of your hreflang tags?
5. Are you using plugins/modules from a third party? Are they secure? Do they have documentation or a rep you can contact about migrating to https?
6. Some CMS's have specific settings that need to be altered when migrating - make sure those were done correctly.
7. Use screaming frog to check for any external scripts, and ensure they're calling https.
8. Did you update your old redirects?
9. Did you update your robots.txt file to include the new https sitemap?
10. Did you enable HSTS?
11. Do you have a disavow file? Did you update it for HTTPS?Bonus:
Did you update all of your other paid campaigns, analytics, etc. to reflect the migration? -
OK, that makes a big difference. Before you resubmit any sitemaps, make sure your technical implementation is perfect. Fix all sitemaps, make sure all URLs are properly 301'd, and make sure you are not generating any type of mixed-content security errors. Make sure all sitemaps are going to the new URLs. Most important, when a user clicks on an old URL (e.g., from search results or an old backlink), they need to be 301 redirected to the same page on HTTPS (not the home page). Then resubmit your sitemaps.
Your transition is still very 'young,' and it will likely take 6-8 weeks before Google completely replaces the old site with the new site in it's algorithms and search results. You should expect a temporary drop in traffic during this transition, but assuming you have done everything correctly, things should normalize after that.
-
Tustind:
Sorry - we did it a week ago - 3/14/17.
We just changed the 302s to 301s yesterday. I believe we need to resubmit our old sitemaps for google to index the 301s.
-
So you made this migration over a year ago now? From my knowledge and experience doing a domain change, which has a lot in common with a https change, we experienced about 2 months of depressed traffic, after which point our traffic normalized and then continued on a growth trajectory. So I suspect that your biggest problem was not properly implementing the 301 redirects. You basically told Google that you were only making a temporary change, which could explain why after an entire year your site has still not been fully picked up. When did you change the 302s to 301s?
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
PLEASE HELP - Old query string URL causing problems
For a long time, we were ranking 1st/2nd for the term "Manual handling training". That was until about 5 days ago when I realised that Google had started to index not only a query stringed URL, but also an old version of the URL. What was even weirder was that when you clicked on the result it 301 redirected to the page that it was meant to display... The wrong URL that Google had started to index was: www.ihasco.co.uk/courses/detail/manual-handling?channel=retail The correct URL that it should have been indexing is: https://www.ihasco.co.uk/courses/detail/manual-handling-training I can't get my head around why it has done this as a 301 was in place already and we use rel canonical tags which point to the main parent pages. Anyway, we slapped a noindex tag in our robots.txt file to stop that page from being indexed, which worked but now I can't get the correct page to be indexed, even after a Google fetch. After inspecting the correct URL in the new search console I discovered that Google has ignored the rel canonical on the page (Which points to itself) and has selected the wrong, query stringed URL as the canonical. Why? and how do I rectify this?
Intermediate & Advanced SEO | | iHasco1 -
Domain Name Migation + HTTPS?
One of our clients is considering migrating their domain name _and _changing protocol (http to https), as well as changing hosting providers, at the same time. Is it fine to make the changes at the same time, or would you recommend 'phasing' the migration?
Intermediate & Advanced SEO | | ThreeShips1 -
Migration Strategy
Hi guys, Just want to check on this site migration strategy. Basically we have an Australian based ecommerce site which is going to launch globally. The company has two site. One is (http://www.domainUS.com – for US market) and one is Australian based (http://www.domain.com.au). Basically the plan is to have one single global .com site (like ASOS.com) on a new domain which would be domain.com and put both the current http://www.domainUS.com (US VERSION) and http://www.domain.com.au (AUSTRALIAN VERSION) on the new domain: domain.com (global) To make it even more complicated the new global domain (domain.com) is in the process of being purchased (someone else has the domain) and won’t be available till January 2016. But the company wants to execute the new global setup in November 2015 temporary on the .com.au version The current migration plan is to create two different sub-folders one for US e.g. http:www.domain.com.au/us and one for AUD http://www.domain.com/au on the current domain Australian domain.com.au for the global launch in November 2015. Then once domain.com is ready in January 2016, then migrate to domain.com with the countries as sub-folder (as shown below in stage 3). I was wondering if you guys think this would be an ideal migration strategy given the circumstances. Link to screenshot of current migration strategy: http://c714091.r91.cf2.rackcdn.com/4c2aae21dcbd548f27d96840227b81bc6b8b00c592.png Any advice would be very much appreciated! Cheers, Chris
Intermediate & Advanced SEO | | jayoliverwright0 -
Redirect HTTP to HTTPS
Hello, Simple question - Should we be redirecting our HTTP pages to HTTPS? If yes, why, if not, why? Thanks!
Intermediate & Advanced SEO | | HB170 -
Problems with a website-help
Soooooo, I did a crawl report on this site : www.greatwesternflooring.com and this was what was on the report. This is a dnn site. I'm guessing the site has a redirect loop given the http status code. Can anyone help me with a fix. (the developers have said there is no redirect on the site......clearly there is....) | http://www.greatwesternflooring.com/ | 2015-01-07T21:32:25Z | 609 : Redirect to already-visited URL received for page request. | Error attempting to request page; see title for details. | 302 | http://www.greatwesternflooring.com | <colgroup><col width="319"> <col width="144"> <col width="378"> <col span="39" width="64"></colgroup>
Intermediate & Advanced SEO | | Britewave
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |0 -
Help with htaccess
I just setup a WP install in a subfolder: domain.com/development/ However, there is an existing htaccess file in the root which contains the following: RewriteRule ^([A-Za-z_0-9-]+)$ /index.php?page=$1 [QSA]
Intermediate & Advanced SEO | | SCW
RewriteRule ^([A-Za-z_0-9-]+)/$ /index.php?page=$1 [QSA]
RewriteRule ^([A-Za-z_0-9-]+)/([a-z]+)$ /index.php?page=$1&comp=$2 [QSA]
RewriteRule ^([A-Za-z_0-9-]+)/([a-z]+)/$ /index.php?page=$1&comp=$2 [QSA] I need to leave the rules as-is due to the nature of CMS (not WP) under the root domain. Is it possible to include an exception or condition which allows URL requests containing /development/ to resolve to that folder? I tried to add: RewriteRule ^development/([A-Za-z_0-9-]+)$ /development/index.php?page=$1 [QSA] but this seems to send it in a loop back to the root. Thanks!!!0 -
Traffic down 60% - about to cry, please help
Hiya guys and girls, I've just spent 6 months, a lot of blood sweat and tears, and money developing www.happier.co.uk. In the last weeks the site started to make a trickle of money, still loss making but showing green shoots. But then on Friday the traffic dropped due to my rankings on google.co.uk dropping. Visits: Thur 25th april = 1950 Fri 26th april = 1284 Sat 27th april = 906 So it looks like Ive been hit with some sort of penalty. I did get a warning on the 20th april about an increase in the number of 404 errors, currently showing 77. I've now remove the links to those 404 pages, ive left the 404 pages as is, as was suggested here: http://www.seomoz.org/blog/how-to-fix-crawl-errors-in-google-webmaster-tools. Could that be the reason? We have spent a lot of time on site design and content. We think the site is good, but I agree it has a long way to go but without income that is hard, so we have been struggling through. Any ideas on the reason/s for the penalty? Big thanks, Julian.
Intermediate & Advanced SEO | | julianhearn0 -
Redirect help
I work for a company that has a domain that is something like www.neat-stuff.com but most people just use www.neatstuff.com without the dash. The redirect for the homepage works fine. We recently launched a new site and if you use www.neat-stuff.com/category it redirects from the old site to the new site just fine. However if you use www.neatstuff.com/category it does not properly redirect to www.neat-stuff.com/category. How do I fix that?
Intermediate & Advanced SEO | | EcommerceSite0