Domain Migration of high traffic site:
-
We plan to perform a domain migration in 6 months time.
I read the different articles on moz relating to domain migration, but some doubts remain:-
Moving some linkworthy content upfront to new domain was generally recommended. I have such content (free e-learning) that I could move already now to new domain.
Should I move it now or just 2 months before migration?
Should I be concerned whether this content and early links could indicate to google a different topical theme of the new domain ? E.g. in our case free elearning app vs a commercial booking of presential courses of my core site which is somehow but not extremely strongly related) and links for elearning app may be very specific from appstores and from sites about mobile apps. -
we still have some annoying .php3 file extensions in many of our highest traffic pages and I would like to drop the file-extension (no further URL change). It was generally recommended to minimize other changes at the same time of domain migration, but on the other hand implementing later another 301 again may also not be optimum and it would save time to do it all at the same time. Shall I do the removal of the file extension at the same time of the domain migration or rather schedule it for 3 months later?
-
On the same topic, would the domain migration be a good occasion to move to https instead of http at the same time, or also should we rather do this at a different time?
Any thoughts or suggestions?
-
-
Marcus, Arnout, Cyrus, excellent comments. Thanks a lot.
-
uuhh thats a long time for bouncing back.
I would use a 301 redirect to assets from old to new domain. This should give clear signal to google to where content lives, or do I oversee anything here?
My key concern really is that google may get signals that new domain is about topic of asset I am moving first and then when I migrate later my core content, it may be more difficult to rank for core content since google associates the new domain with the topical focus of content that was moved first. Is this something you would be concerned about? -
It took us 6-8 months to bounce back.
Yes, I'm actually worried about sending confusing signals to Google about where the content is suppose to live.
I don't like making Google think
-
Cyrus, thanks a lot for the advice.
In the long-run, what do you think is the percentage of organic traffic you lost at moz.com due to the domain migration? 30% was just short-term effect, right?
Regarding moving assets upfront, it would be quite easy to do in our case.
But would you be concerned about giving google wrong signals about topic of domain which may make it more difficult later to rank our core content well? -
Keep in mind this is a complex situation with lots of moving parts, so there are no "right" answers.
That said, you're dealing with a lot of potential redirects:
- Site migration
- HTTPS
- .php extension rewriting
On one hand, I'm concerned if you stagger these out, you'll be diluting your authority through several 301 redirects.
In this case, might be best to do it all at once.On the other hand, doing it all at once greatly increases the chance of something going wrong. In this case, best to stagger things out.
At Moz, we went with "do it all at once" when we migrated to moz.com. Needless to say, we didn't do everything perfect and our organic traffic dropped nearly 30%, instead of the 15% we would have normally expected from a smaller migration.
Regardless, I'd still preference the "all at once" approach, and just be very diligent with your redirects, making sure not to drop pages, rewrite content, change title tags, etc.
As for moving big assets over ahead of time, I know some people endorse it, but I haven't seen a ton of evidence that it makes a significant difference. If it complicates things, I'd likely avoid it.
Hope this helps! Best of luck with your SEO.
-
- we still have some annoying .php3 file extensions in many of our highest traffic pages and I would like to drop the file-extension (no further URL change). It was generally recommended to minimize other changes at the same time of domain migration, but on the other hand implementing later another 301 again may also not be optimum and it would save time to do it all at the same time. Shall I do the removal of the file extension at the same time of the domain migration or rather schedule it for 3 months later?
I would do it all in once.
- On the same topic, would the domain migration be a good occasion to move to https instead of http at the same time, or also should we rather do this at a different time?
I would do it at the same time but make sure you have all variations of the URL http and https and www and non-www verified in GWT so you can point GWT the best one.
-
Hey
This is one of those jobs that has to be done very carefully and as a rule of thumb I would always look to minimise the number of variables. If you are simply changing the URL from one domain to another then it should be fairly straightforward with 301 redirection for the domain itself and an update to the domain in webmaster tools.
With regards to HTTPS and the .php3 pages you have two options
1. make that change now
2. make that change some point after everything else is changed and stabilised
My thinking here would be to get everything as dialled in as possible BEFORE the move to the new domain. Conduct a full technical audit, SEO audit and do whatever you can to optimise the technical aspects of the site. I am talking squeaky clean technical SEO you can see your face in. So, a change to the php3 files, a move to HTTPS - you could do all of that now (along with anything else you find during the technical audit).
Main thinking here is to get everything as perfect as possible pre move - minimise the surface area for potential problems - minimise the number of variables when you make the change - then should anything go wrong you have as clear an idea as possible where the problem lies.
My main advice is to simplify the move as much as possible so anything you can do now rather than later will only make your life easier and the move simpler.
Hope that helps!
Marcus
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
-
I need help on how best to do a complicated site migration. Replacing certain pages with all new content and tools, and keeping the same URL's. The rest just need to disappear safely. Somehow.
I'm completely rebranding a website but keeping the same domain. All content will be replaced and it will use a different theme and mostly new plugins. I've been building the new site as a different site in Dev mode on WPEngine. This means it currently has a made-up domain that needs to replace the current site. I know I need to somehow redirect the content from the old version of the site. But I'm never going to use that content again. (I could transfer it to be a Dev site for the current domain and automatically replace it with the click of a button - just as another option.) What's the best way to replace blahblah.com with a completely new blahblah.com if I'm not using any of the old content? There are only about 4 URL'st, such as blahblah.com/contact hat will remain the same - with all content replaced. There are about 100 URL's that will no longer be in use or have any part of them ever used again. Can this be done safely?
Intermediate & Advanced SEO | | brickbatmove1 -
Still Seeing GSC Traffic in HTTP Property Post-Migration
We migrated to HTTPS in June 2017, so why would I still be seeing a bit of traffic in our HTTP property in Google Search Console? QyqQ2
Intermediate & Advanced SEO | | catbur0 -
Should I revive the old domain or just redirect all the juicy links to my new site?
I'm about to acquire a domain with a lot of great/highly authoritative backlinks. The links pointing to the domain are quite powerful and the domain is an exact match TLD. I have two options (that I know of 😞 1. I could redirect all the links to their new home(s) on my new site which offers the same resources the old site used to offer. or 2. I could rebuild the tools/content on this site. Ideally, I'd transfer to my new site as all those powerful links could help all my rankings. However, I'm worried that some of the powerful links will de-link once they see the site redirects elsewhere, even though it's offering the same content. Also, option one isn't an exact match domain. Which, I know, shouldn't make a difference now-a-days but regardless of what people say, it still seems to help out some sites in less competitive niches. One more thing to note: The domain that I'm purchasing is about 25 years old. I'm leaning toward option one. I want to make sure I put my best foot forward on this investment and thought it wise to consult the SEO gods.
Intermediate & Advanced SEO | | ninel_P0 -
301 redirecting a site that currently links to the target site
I have a personal blog that has a good amount of back links pointing at it from high quality relevant authoritative sites in my niche. I also run a company in the same niche. I link to a page on the company site from the personal blog article that has bunch of relevant links pointing at it (as it's highly relevant to the content on the personal blog). Overview: Relevant personal blog post has a bunch of relevant external links pointing at it (completely organic). Relevant personal blog post then links (externally) to relevant company site page and is helping that page rank. Question: If I do the work to 301 the personal blog to the company site, and then link internally from the blog page to the other relevant company page, will this kill that back link or will the internal link help as much as the current external link does currently? **For clarity: ** External sites => External blog => External link to company page VS External sites => External blog 301 => Blog page (now on company blog) => Internal link to target page I would love to hear from anyone that has performed this in the past 🙂
Intermediate & Advanced SEO | | Keyword_NotProvided0 -
Content From One Domain Mysteriously Indexing Under a Different Domain's URL
I've pulled out all the stops and so far this seems like a very technical issue with either Googlebot or our servers. I highly encourage and appreciate responses from those with knowledge of technical SEO/website problems. First some background info: Three websites, http://www.americanmuscle.com, m.americanmuscle.com and http://www.extremeterrain.com as well as all of their sub-domains could potentially be involved. AmericanMuscle sells Mustang parts, Extremeterrain is Jeep-only. Sometime recently, Google has been crawling our americanmuscle.com pages and serving them in the SERPs under an extremeterrain sub-domain, services.extremeterrain.com. You can see for yourself below. Total # of services.extremeterrain.com pages in Google's index: http://screencast.com/t/Dvqhk1TqBtoK When you click the cached version of there supposed pages, you see an americanmuscle page (some desktop, some mobile, none of which exist on extremeterrain.com😞 http://screencast.com/t/FkUgz8NGfFe All of these links give you a 404 when clicked... Many of these pages I've checked have cached multiple times while still being a 404 link--googlebot apparently has re-crawled many times so this is not a one-time fluke. The services. sub-domain serves both AM and XT and lives on the same server as our m.americanmuscle website, but answer to different ports. services.extremeterrain is never used to feed AM data, so why Google is associating the two is a mystery to me. the mobile americanmuscle website is set to only respond on a different port than services. and only responds to AM mobile sub-domains, not googlebot or any other user-agent. Any ideas? As one could imagine this is not an ideal scenario for either website.
Intermediate & Advanced SEO | | andrewv0 -
Sub domain on root domain
Hello,
Intermediate & Advanced SEO | | dror999
I have a question that I can't find a good answer on.
I have a site, actually a "portal"/ "directory" for service providers.
Now, for start, we opened every service provider own page on our site, but now we get a lot of applications from those providers that thy want sites from their own.
We want to make every service provider his own site, but on sub domain url. ( they don’t mind… its ok for them)
So, my site is www.exaple.com
There site will be: provider.exaple.com
Now I have two questions:
1. can it harm my site in SEO?
2. if one from those sub domain , punished by google because is owner do "black hat seo" , how it will affect the rood domin? It can make the root domain to get punished?
Thanks!!0 -
What's the best way to manage content that is shared on two sites and keep both sites in search results?
I manage two sites that share some content. Currently we do not use a cross-domain canonical URL and allow both sites to be fully indexed. For business reasons, we want both sites to appear in results and need both to accumulate PR and other SEO/Social metrics. How can I manage the threat of duplicate content and still make sure business needs are met?
Intermediate & Advanced SEO | | BostonWright0 -
Googlebot found an extremely high number of URLs on your site
I keep getting the "Googlebot found an extremely high number of URLs on your site" message in the GWMT for one of the sites that I manage. The error is as below- Googlebot encountered problems while crawling your site. Googlebot encountered extremely large numbers of links on your site. This may indicate a problem with your site's URL structure. Googlebot may unnecessarily be crawling a large number of distinct URLs that point to identical or similar content, or crawling parts of your site that are not intended to be crawled by Googlebot. As a result Googlebot may consume much more bandwidth than necessary, or may be unable to completely index all of the content on your site. I understand the nature of the message - the site uses a faceted navigation and is genuinely generating a lot of duplicate pages. However in order to stop this from becoming an issue we do the following; No-index a large number of pages using the on page meta tag. Use a canonical tag where it is appropriate But we still get the error and a lot of the example pages that Google suggests are affected by the issue are actually pages with the no-index tag. So my question is how do I address this problem? I'm thinking that as it's a crawling issue the solution might involve the no-follow meta tag. any suggestions appreciated.
Intermediate & Advanced SEO | | BenFox0