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
-
Sudden drop in organic traffic after migration from Django to Wordpress.
I have seen a sudden drop organic reach in a particular page of our website www.hackerearth.com/innovation earlier this was www.hackerearth.com/sprint. I although understand that it happens while migration but it has been a while we did the migration. The migration happened around May month. Something similar has happened to our blog. Earlier it was a blog.hackerearth.com now hackerearth.com/blog _Could anyone suggest me what could be the possible issue for the drop in traffic? _
Intermediate & Advanced SEO | | Rajnish_HE0 -
Legacy domains
Hi all, A couple of years ago we amalgamated five separate domains into one, and set up 301 redirects from all the pages on the old domains to their equivalent pages on the new site. We were a bit tardy in using the "change of address" tool in Search Console, but that was done nearly 8 months ago now as well. Two years after implementing all the redirects, the old domains still have significant authority (DAs of between 20-35) and some strong inbound links. I expected to see the DA of the legacy domains taper off during this period and (hopefully!) the DA of the new domain increase. The latter has happened, although not as much as I'd hoped, but the DA of the legacy domains is more or less as good as it ever was? Google is still indexing a handful of links from the legacy sites, strangely even when it is picking up the redirects correctly. So, for example, if you do a site:legacydomain1.com query, it will give a list of results which includes pages where it shows the title and snippet of the page on newdomain.com, but the link is to the page on legacydomain1.com. What has prompted me to finally try and resolve this is that the server which hosted the original 5 domains is now due to be decommissioned which obviously means the 301 redirects for the original pages will no longer be served. I can set up web forwarding for each of the legacy domains at the hosting level, but to maintain the page-by-page redirects I'd have to actually host the websites somewhere. I'd like to know the best way forward both in terms of the redirect issue, and also in terms of the indexing of the legacy domains? Many thanks, Dan
Intermediate & Advanced SEO | | clarkovitch0 -
Traffic drop on this site
I am SEO'ing this site but need some assistance in the analysis. it was doing not too bad but in the last 4 months the google traffic has really fallen off, i suspect the keywords may need improving but any tips or observations would be great.
Intermediate & Advanced SEO | | crowng0 -
Splitting and moving site to two domains - How to redirect
I have a client who is going to split their retail and wholesale business and rebrand the retail biz. So let’s say they are going to move everything from currentdomain.com to either retaildomain.com or wholesaledomain.com. The most important business for them is the retail site, so they want to pass on as much ranking power as they can from currentdomain.com to retaildomain.com. I see two choices here: We can 301 redirect all of currentdomain.com to retaildomain.com, and then redirect any wholesale pages to wholesaledomain.com. The advantage is that we can use GSC’s change of address tool to report the change to Google. The downside is that there is a redirect chain (2 hops) to wholesaledomain.com. Would this confuse Google? Or we can 301 redirect page by page from currentdomain.com to the appropriate page on either new site. This means no redirect chains but it also means that we can’t use GSC’s change of address tool. Which would you do and why? And is there another option that I'm missing? I appreciate any insights you can share.
Intermediate & Advanced SEO | | rich.owings1 -
Very strange HTML docs - what should I do with them through site migration?
I've just been looking at a website and it includes numerous web pages with addresses like this. I click on the URL and it takes me to a fully functional web page (not an image) and when I run it through Screaming Frog this comes up as an HTML page. The site has around 150 unique pages and over 450 pages like this one - how should I deal with these pages during an SEO migration (only a few are backlinked to)? I look forward to reading your thoughts. http://www.[companyname].co.uk/property/caravan-sleeps-4/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/images/cottageTypes/blank.png
Intermediate & Advanced SEO | | McTaggart0 -
Consolidating two different domains to point at same site, duplicate content penalty?
I have two websites that are extremely similar and want to consolidate them into one website by pointing both domain names at one website. is this going to cause any duplicate content penalties by having two different domain names pointing at the same site? Both domains get traffic so i don't want to just discontinue one of the domains.
Intermediate & Advanced SEO | | Ron100 -
Does using a sub-domain lessen the effectiveness of your main domain?
For example a website without a blog and is a simple html site with no blogging capabilities. We go out to Blogger or Wordpress and set up the blog portion of the website using something like blog.yourdomain.com. Does this make a difference SEO wise? Is is more effective to be sure that you are using the main domain and not a sub-domain? I have heard both sides before but can't seem to find the concrete answer. Thanks for any advise out there.
Intermediate & Advanced SEO | | d25kart0 -
Rebuilding a site with pre-existing high authority subdomains
I'm rebuilding a real estate website with 4 subdomains that have Page Authorities between 45 and 50. Since it's a real estate website it has 20,000+ pages of unique (listing) content PER sub-domain. The subdomains are structured like: washington.xyzrealty.com and california.xyzrealty.com. The root domain has a ~50 Page Authority. The site is about 7 years old. My preference is to focus all of my efforts on the primary domain going forward, but I don't want to waste the power of the subdomains. I'm considering: 1. Putting blogs or community/city pages on the subdomains 2. 301 redirecting all of the existing pages to matching pages on the new root domain. 3. Any other ideas??
Intermediate & Advanced SEO | | jonathanwashburn0