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 am temporarily moving a site to a new domain. Which redirect is best?
A client is having their site redeveloped on a new platform in sections and are moving the sections that are on the new platform to a temporary subdomain until the entire site is migrated. This is happening over the course of 2-3 months. During this time, is it best for the site to use 302 temporary redirects during this time (URL path not changing), or is it best to 301 to the temp. domain, then 301 back to the original once the new platform is completely migrated? Thanks!
Intermediate & Advanced SEO | | Matt3120 -
Can’t put a finger on, what is causing 12 year domain, SEO optimized and decent link profile to rank lower than other less superior domains.
Can’t put a finger on, what is causing 12 year domain, SEO optimized and decent link profile to rank lower than other less superior domains. I have dissected the site and link, content, etc profile using ahrefs tools, still no luck, and unfortunately they do not have a community to ask anyone opinion. Hoping someone on Moz will be able to provide me with a secondary opinion or something I obviously missing here. Looking for any constructive feedback/professional opinion with fresh look on what maybe the cause of our down rankings and what may be a cause of it. Any feedback is very much appreciated. Search Term: 3030 aventura condos / One of our link samples (SE Position #6): https://goo.gl/FbYj4V Competing Domains (SE Position #1): https://goo.gl/fLPKX5 Competing Domains (SE Position #2): https://goo.gl/GqXGse
Intermediate & Advanced SEO | | Im_Jake0 -
Splitting One Site Into Two Sites Best Practices Needed
Okay, working with a large site that, for business reasons beyond organic search, wants to split an existing site in two. So, the old domain name stays and a new one is born with some of the content from the old site, along with some new content of its own. The general idea, for more than just search reasons, is that it makes both the old site and new sites more purely about their respective subject matter. The existing content on the old site that is becoming part of the new site will be 301'd to the new site's domain. So, the old site will have a lot of 301s and links to the new site. No links coming back from the new site to the old site anticipated at this time. Would like any and all insights into any potential pitfalls and best practices for this to come off as well as it can under the circumstances. For instance, should all those links from the old site to the new site be nofollowed, kind of like a non-editorial link to an affiliate or advertiser? Is there weirdness for Google in 301ing to a new domain from some, but not all, content of the old site. Would you individually submit requests to remove from index for the hundreds and hundreds of old site pages moving to the new site or just figure that the 301 will eventually take care of that? Is there substantial organic search risk of any kind to the old site, beyond the obvious of just not having those pages to produce any more? Anything else? Any ideas about how long the new site can expect to wander the wilderness of no organic search traffic? The old site has a 45 domain authority. Thanks!
Intermediate & Advanced SEO | | 945010 -
Is there any problem if we migrate the entire site to HTTPS except for the blog ?
Hello guys,
Intermediate & Advanced SEO | | newrankbg
I have a question to those of you, who have migrated from HTTP to HTTPS. We are planning to migrate the site of our customer to Always SSL. In other words, we want to redirect all site pages to HTTPS, except for the blog. Currently, the whole site is using the HTTP protocol (except the checkout page).
After the change, our customer's site should look like this: https://www.domain.com
http://www.domain.com/blog/ The reasons we do not want to migrate the blog to HTTPS are as follows: The blog does not collect any sensitive user information, as opposed to the site. We all know that on-site algorithms like Panda are having sitewide effect. If the Panda doesn’t like part of the blog (if any thin or low quality content), we do not want this to reflect on the rankings of the entire website. Having in mind that for Google, HTTP and HTTPS are two different protocols, a possible blog penalty should not reflect the web site, which will use HTTPS. Point 2 is the reason I am writing here, as this is just a theory. I would like to hear more thoughts from the experts here. Also, I would like to know your opinion, regarding this mixed use of protocols – could this change lead to a negative effect for any of the properties and why? For me, there should be no negative effect at all. The only disadvantage is that we will have to monitor both metrics – the blog and the site separately in webmaster tools. Thank you all and looking forward for your comments.0 -
Sub Domain or New Domain?
Hi All, We have a client that has a business with three different services. 2 of these services compliment each other in a really obvious way, but the 3rd, while related is not such a obvious complimentary service. For this reason, service 3 kind of weakens the content of the website SEO wise for the two main services. Also, internally at the business it is run by an entirely different team so it feels culturally somewhat different. So, the client wants to pull all the content about service 3 and put it on a different website. Which would you chose as a domain for this new site: service3.existingdomain.co.uk or www.service3+brandname.co.uk
Intermediate & Advanced SEO | | NoisyLittleMonkey0 -
Is it possible to Spoof Analytics to give false Unique Visitor Data for Site A to Site B
Hi, We are working as a middle man between our client (website A) and another website (website B) where, website B is going to host a section around websites A products etc. The deal is that Website A (our client) will pay Website B based on the number of unique visitors they send them. As the middle man we are in charge of monitoring the number of Unique visitors sent though and are going to do this by monitoring Website A's analytics account and checking the number of Unique visitors sent. The deal is worth quite a lot of money, and as the middle man we are responsible for making sure that no funny business goes on (IE false visitors etc). So to make sure we have things covered - What I would like to know is 1/. Is it actually possible to fool analytics into reporting falsely high unique visitors from Webpage A to Site B (And if so how could they do it). 2/. What could we do to spot any potential abuse (IE is there an easy way to spot that these are spoofed visitors). Many thanks in advance
Intermediate & Advanced SEO | | James770 -
My site links have gone from a mega site links to several small links under my SERP results in Google. Any ideas why?
A site I have currently had the mega site links on the SERP results. Recently they have updated the mega links to the smaller 4 inline links under my SERP result. Any idea what happened or how do I correct this?
Intermediate & Advanced SEO | | POSSIBLE0 -
7 years old domain sandboxed for 8 months, wait or make a domain change?
Hello folks The questions is, if a domain, 7 years old being sandboxed due to "notice of unnatural links to website" does it make sense to make a domain change (301 permanent redirect and make a "domain change" under google webmaster tools) to another, aged(!) domain name?
Intermediate & Advanced SEO | | Ferray
Website being sandboxed for over 8 months already and there is no chance to do anything with those "unnatural" links to website... Any suggestions?0