Site Migration from One Dev. and Server to Another Dev. and Server
-
Hi Mozzers!
I've got a client that is in the early stages of moving the development of their site to another company and therefore, a new server. The site is very large and the migration will take place over 18 months. In the beginning, smaller chunks of the site will be moved, and as that process gets dialed in, larger portions will migrate.
It was brought to our attention today that they (on either side of development) have not yet worked out the logistics of keeping the domain and URL structure consistent throughout the migration. The initial proposal was that they publish newly migrated pages to a subdomain, which we obviously want to steer away from. I'm now on a mission to find a solution that will make everyone happy; client, old dev, new dev, and us (as the SEO partner).
Does anyone have experience in managing SEO through a migration such as this?
-
This is exactly the solution I've been after. Your input and walk-thru is much appreciated!
-
Some load balancing hardware might be able to do this, too - basically, instead of splitting up requests evenly across multiple servers, they'd be configured to send some specific requests to one server and other requests to another server.
Unfortunately, this gets very technical very quickly, and depends completely on your own hardware, OS, configuration, etc. (and, frankly, I'm no expert at all, other than knowing it's possible). There's typically also some added cost involved.
-
Having read through your conversation with Ruth, it looks like there aren't many options open to you.
Your client might be able to use a reverse proxy. I'll walk you through a very simple example with Apache, but the same principles hold for other web servers. I should warn you too that proxies can be fickle, and it may be difficult to persuade the developers to put in the work!
Let's say we host the existing website at example.com, and the new site – or what exists of it so far – at staging.example.com. So there are a couple of different DNS records, with the root domain pointing to the IP address of the old server, and the staging subdomain pointing to the IP address of the new server.
Let's also assume that we're migrating a directory called "/foo" for now. We now want those URLs, and only those URLs, to be served from the new server.
We would then use ProxyPass and ProxyPassReverse directives on example.com, to route those requests to the new server:
ProxyPass /foo http://staging.example.com
ProxyPassReverse /foo http://staging.example.com
The first line says "proxy requests to example.com/foo to staging.example.com/foo instead".
The second line is essential because let's say that one of the URLs in /foo is a redirect. Specifically, let's imagine that staging.example.com/foo/1 is a 301 redirect to staging.example.com/foo/2. Now when the user visits example.com/foo/1, their request is proxied to staging.example.com/foo/1, which is in turn 301-redirected to staging.example.com/foo/2, and this is what will show in the address bar (and to Googlebot). That's what you don't want because then the subdomain is visible to Google. So the point of the second line is to say that when the redirect takes place, it should be adjusted back to the form of the original request before being returned to the client. So now, with that second line in place, the request chain looks like this:
Client requests example.com/foo/1
That's proxied to staging.example.com/foo/1
That's a 301-redirect to staging.example.com/foo/2
And that URL is then adjusted back to example.com/foo/2 before the user sees it!
As you migrate sections of the site, you would add new ProxyPass directives to proxy those directories. Then, when you've migrated the whole site, you change the DNS so that the root A record now points to the IP address of the new server, remove the DNS record for staging.example.com, and ditch the old server.
You'll need to ensure that the developers controlling the old site implement the proxies correctly and that there's a sensible mapping of old directory structures to new ones. Your life will be a lot easier if you can minimise the number of redirects taking place on the new server. Good luck!
-
It's not a matter of keeping them happy, it's simply helping our client accomplish what is best for their SEO during this migration. We have a really good relationship with them, so it's in everyone's best interest if we help find a viable solution.
Unfortunately, launching all at once isn't an option. This migration has been planned for months, there's no going back to the drawing board at this point. There won't be any brand confusion because visitors don't have much reason to be bouncing around to the different sections, they're very localized.
Thank you for your input, but it looks like I'm still on the hunt for a solution.
-
Thanks for the clarification!
From my perspective, your desire to keep both companies happy, while laudable, shouldn't have to be your problem because both companies work for you - they should be the ones figuring out how to work together - although I suppose the company that's on it's way out doesn't have a ton of incentive to play nicely.
Is the new design going to be substantially different from the old design? If so, it might make sense for them to do all of the design and dev work in their own staging environment, and then launch the site all at once when it's ready. I know 18 months is a long time, but I'd be concerned about the brand and user experience implications of having two different designs live on the same site.
I don't know of a way to have one domain hosted on two different servers. Your other best bet would probably be to do as Chris suggested and move the entire existing site over to the new server, then make changes from there.
-
Thanks for your response Ruth.
Luckily, the URLs won't be changing....at least that's the plan anyway!
I'm looking more for info on how to have one domain with different sections spread across 2 different servers. The new development company has a proprietary CMS and are redesigning portions of the site incrementally. They will probably be reluctant to work off of the old development company's server, which is why we're trying to provide a solution that makes both dev companies happy.
-
You're right to be against the subdomain idea - that's not a good call for SEO at all.
What I would do is start out with a full database export of all the URLs on the current site, and figure out what URL each of those resources is ultimately going to live at. This can be daunting with a large site, but it goes faster than you think it's going to - once you figure out that all the pages in example.com/old-folder/pagename are now going to live at example.com/new-folder/pagename you can figure out the URL structure for large chunks of the site at a time. Since it sounds like there won't be any changes to the overall design and structure of the site, just some possible URL changes, that will make it easier, too. I did this for the SEOmoz.org -> Moz.com transition and it took about a month to map out 65,000 pages alongside my other SEO duties (but that was with a lot of major changes in site structure, too).
Once everyone (you, the client, both dev teams) have agreed on the new structure, it's simply a matter of:
- moving the pages in each "chunk" from their old URLs to their new URLs
- 301 redirecting the old URLs to the new URLs on a page-to-page level
- doing a database find+replace on the old site and the new one to update internal links to those pages
Be really really careful with managing expectations for this. It's very common to see pages take a temporary hit in rankings and traffic immediately after they move to a new URL; this drop is usually temporary and reversible. But you don't want the client taking that data as proof that the migration isn't going to work or isn't working, and abandoning ship. To help matters along, take a look at what their best inbound links are and the linking sites with whom you have the best relationship, and as those pages move to their new addresses, reach out to the linking sites to try to get those links updated.
Does that answer your question? Happy to discuss further if not.
-
Thanks for your response!
The new dev company proposed the subdomain idea, which I'm adamantly against. So this is why I'm on the search for an alternative- surely, someone else has had a similar situation.
There is a proprietary CMS involved, I should have mentioned that initially, which is where the real challenge comes in. I don't think either of the developers would be thrilled about a recommendation where they put there info on someone else's box, unless there is some way to lock down access that I'm not familiar with.
-
We've handled plenty of site migrations but certainly not on an 18-month time scale! That said, the same concepts apply.
So if I understand correctly, they want to keep the current site running (old server and dev) and migrate one section of the site at a time to a subdomain so users would end up visiting a seemingly random mix of domain.com and sub.domain.com?
Without knowing more of the details, I suppose the best solution would be to relocate the whole site, database and all, to the new server then the new devs can work on whatever it is they were looking to change. Since you haven't already suggested that, there must be some limitation that makes this impossible - proprietary CMS or something?
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
-
White listing a site
A new clients site is blocked by a lot of Firewalls. And I can't work out why, the content is family friendly they sell nursery equipment. I've run it through the Google checker and there is no malicious software found on the site. Can anyone tell me what I need to do to get this site unblocked? The url is http://knuma.co.uk/
Technical SEO | | Marketing_Optimist0 -
Google Plus One button and https migration
I have a site that has gotten quite a few google +1's. I am currently migrating to https for the site and it seems I will lose all the +1's? Per the documentation it seems I can set the URL to the normal http://, but that would then allow ppl to continue +'ing the old url. Is there a way around this? Thanks!
Technical SEO | | plahpoy0 -
How can I get Google to forget an https version of one page on my site?
Google mysteriously decided to index the broken, https version of one page on my company's site (we have a cert for the site, but this page is not designed to be served over https and the CSS doesn't load). The page already has many incoming links to the http version, and it has a canonical URL with http. I resubmitted it on http with webmaster tools. Is there anything else I could do?
Technical SEO | | BostonWright0 -
Robots.txt | any SEO advantage to having one vs not having one?
Neither of my sites has a robots.txt file. I guess I have never been bothered by any particular bot enough to exclude it. Is there any SEO advantage to having one anyways?
Technical SEO | | GregB1230 -
Specific Domain Migration Question
My company will be taking over an ecommerce site that is built to get local city/state traffic where the competition is slim to none for the given keyword. This site gets 2500+ visits per day, and we're looking to maintain and eventually grow that traffic. We would like to move that site onto our ecommerce platform which will force URL change and of every 'keyword' city/state page on the site. We're undecided whether to keep it on an unfamiliar platform that already gets traffic or to move it and possibly face the 404's or weeks of redirecting a single keyword-city/state page to another. Any advice or insight would be great!
Technical SEO | | BMac540 -
Can we use our existing site content on new site?
We added 1000s of pages unique content on our site and soon after google release penguin and we loose our ranking for major keywords and after months of efforts we decided to start a new site. If we use all the existing site content on new domain does google going to penalized the site for duplicate content or it will be treated as unique? Thanks
Technical SEO | | mozfreak0 -
Way to find how many sites within a given set link to a specific site?
Hi, Does anyone have an idea on how to determine how many sites within a list of 50 sites link to a specific site? Thanks!
Technical SEO | | SparkplugDigital0 -
Index forum sites
Hi Moz Team, somehow the last question i raised a few days ago not only wasnt answered up until now, it was also completely deleted and the credit was not "refunded" - obviously there was some data loss involved with your restructuring. Can you check whether you still find the last question and answer it quickly? I need the answer 🙂 Here is one more question: I bought a website that has a huge forum, loads of pages with user generated content. Overall around 500.000 Threads with 9 Million comments. The complete forum is noindex/nofollow when i bought the site, now i am thinking about what is the best way to unleash the potential. The current system is vBulletin 3.6.10. a) Shall i first do an update of vbulletin to version 4 and use the vSEO tool to make the URLs clean, more user and search engine friendly before i switch to index/follow? b) would you recommend to have the forum in the folder structure or on a subdomain? As far as i know subdomain does take lesser strenght from the TLD, however, it is safer because the subdomain is seen as a separate entity from the regular TLD. Having it in he folder makes it easiert to pass strenght from the TLD to the forum, however, it puts my TLD at risk c) Would you release all forum sites at once or section by section? I think section by section looks rather unnatural not only to search engines but also to users, however, i am afraid of blasting more than a millionpages into the index at once. d) Would you index the first page of a threat or all pages of a threat? I fear duplicate content as the different pages of the threat contain different body content but the same Title and possibly the same h1. Looking forward to hear from you soon! Best Fabian
Technical SEO | | fabiank0