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
-
Google Mobile site crawl returns poorer results on 100% responsive site
Has anyone experienced an issue where Google Mobile site crawl returns poorer results than their Desktop site crawl on a 100% responsive website that passes all Google Mobile tests?
Intermediate & Advanced SEO | | MFCommunications0 -
Site migration/ CMS/domain site structure change-no access to search console
Hi everyone, We are migrating an old site under a bigger umbrella (our main domain). As mentioned in the title, We'll perform CMS migration, domain change, and site structure change. Now, the major problem is that we can't get into google search console for the old site. The site still has old GA code, so google search console verification using this method is not possible, also there is no way developers will be able to add GTM or edit DNS setting (not to bother you with the reason why). Now, my dilemma is : 1. Do we need access to old search console to notify Google about the domain name change or this could be done from our main site (old site will become a part of) search console 2. We are setting up 301 redirects from old to the new domain (not perfect 1:1 redirect ). Once migration is done does anything else needs to be done with the old domain (it will become obsolete)? 3.The main site, Site-map... Should I create a new sitemap with newly added pages or update the current one. 4. if you have anything else please add:) Thank you!
Intermediate & Advanced SEO | | bgvsiteadmin0 -
Domain Migration Hell!
5 weeks ago we migrated our site to a new domain. We also installed an SSL certificate on the new domain. The new domain was purchased 5 years ago but we only used it as a redirect address. It was more consistent with our brand so we decided to migrate to it. Great care was taken setting up page to page redirects. A formal domain change request was made to Google. In fact the move was implemented with only a handful of broken links on a 500 page site. Those links were quickly fixed. Our traffic declined from about 350 visitors a week to as low as 40 visitors the first full week after the move. Now the number of organic Google visits is up to 80, a drop of 75% !!! All except 20 (out of 500) pages are reindexed on Google Search Console. MOZ domain authority for the new domain has climbed from 5 to about 12. The old domain had a DA of 23. In Google Search Console hundreds of "URL Not Allowed" errors are the site map for our previous domain that redirects to our new domain. Attached please see image of this. The site map for the new domain appears normal, but about 160 pages are indexed that are not in the sitemap. I wonder if these two issues have somehow contributed to the drop in ranking. I have included images showing GCT for the 2 domains. I posted on MOZ a month ago and was told it just might take time. No improvement and now I am wonder if there is not some issue with the sitemaps causing havoc. Are traffic is down more than 80%. This does not seem normal. Any advice? Any suggestions as to how to expedite recovery? Thanks,
Intermediate & Advanced SEO | | Kingalan1
Alan0 -
Risks of moving a site back to an old domain
Hi Nearly 2 years ago our site was moved from a .co.uk domain to .media. Because this TLD isn't supported for DA, it's hard to measure whether linkbuilding campaigns (for example) are having a positive effect. The old site has a DA of 38 (even after 2 years of inactivity) and the new one is 1, but the new one has better Trust and Citation flow, for example. I'm now investigating whether it's worth moving back to .co.uk and I want to fully understand the risks involved. So far I know of the following potential risks: It's a lot of work so human error is a real risk Could create a redirect loop as the old site has 301 redirects in place to the new one It will take several months for metrics to recover Any thoughts on more risks, how these challenges can be overcome etc will be welcome. Or do I just set fire to the lot and create a new site with yet another 301 redirect from the .media site? What would you do?
Intermediate & Advanced SEO | | AxonnMedia0 -
Community inside the domain or in a separate domain
Hi there, I work for an ecommerce company as an online marketing consultant. They make kitchenware, microware and so on. The are reviewing their overall strategy and as such they want to build up a community. Ideally, they would want to have the community in a separate domain. This domain wouldn't have the logo of the brand. This community wouldn't promote the brand itself. The brand would post content occassionally and link the store domain. The reasoning of this approach is to not interfere in the way of the community users and also the fact that the branded traffic acquired doesn't end up buying at the store I like this approach but I am concerned because the brand is not that big to have two domains separated and lose all the authority associated with one strong domain. I would definitely have everything under the same domain, store and community, otherwise we would have to acquire traffic for two domains. 1. What do you think of both scenarios, one domain versus two? Which one is better? 2. Do you know any examples of ecommerce companies with successful communities within the store domain? Thanks and regards
Intermediate & Advanced SEO | | footd0 -
Is it safe to redirect our .nl (netherlands) domain that we have just purchased to our .com domain?
Hi all! We've recently developed a German version of our website with German translation and now we have just purchased a .nl domain, but with this one, we want all of the copy to remain in English. Is it ok to redirect our .nl domain to our current .com website or will this give us bad SEO points? Thank you!
Intermediate & Advanced SEO | | donaldsze0 -
Move blog from subdomain to main domain on ecom site?
I am wondering what my fellow mozers think. Pretty set about my direction but want to get any other input to aid in my decision. Have an ecom site with a www.blog.maindomain.com. The blog is fairly new and no major rankings. There are only about 30 posts. This isn't a super competitive market and the blogging won't be a huge part of our content strategy but I would like to use it for passing juice etc. Would you go through the trouble to move the blog to www.site.com/blog and redirecting all the old content to new?
Intermediate & Advanced SEO | | PEnterprises0 -
Sub domain versus separate domains, which is better for Search engine purposes?
We are pitching to a hotel client to build two new websites, a summer website and a winter website, two completely different looking websites. The client wants to automatically switch their domain name to point to one or the other, depending on the time of year. The customer does not want to use a landing page where you would choose which site to visit; they want the domain name to go directly to the relevant website. Our options: Set up two new domain names and optimise each website based on the holiday season and facilities offered at that time of year. Then change the exisiting domain name to point at the website that is in season. Or Use the existing domain name and setup two sub domains, switching the home page as necessary. We have been chewing this one over for a couple of days, the concern that we have with both options is loss of search visibility. The current website performs well in search engines, it has a home page rank of 4 and sub-pages ranking 2 and 3’s, when we point the domain at the summer site (the client only has a winter website at present) then we will lose all of the search engine benefits already gained. The new summer content will be significantly different to the winter content. We then work hard for six months optimising the summer site and switch back to the Winter site, the content will be wrong. Maybe because it's Friday afternoon we cannot see the light for the smoke of the cars leaving the car park for the weekend, or maybe there is no right or wrong approach. Is there another option? Are we not seeing the wood for the trees? Your comments highly welcome. Martin
Intermediate & Advanced SEO | | Bill-Duff0