Phasing in new website on www2 domain - 301 plan
-
Hi,
I work for a large company and we're planning to phase in a new website. The idea is to develop key journeys on the new site and serve them on a www2 domain, removing them from the old website which is served on the www domain.
The reason for this is because the old website is over 2,000 pages, and the management want to see new, improved journeys sooner rather than later. So, rather than launching all new pages and journeys at the same time, which will take a long time to design and develop, key journeys will move across to the new site / design sooner and made available to visitors.
Whilst the overall journey might be a bit disjointed in parts (i.e. sending people from old to new site, and vice versa) I can't see a better way of doing it...
Once all new content is complete, 301s will be implemented from old content on www. to new content www2.
Once the phasing is complete, and all new content is in place on www2, 301s will be implemented to point everything back to www.
Does anybody see any problems with this approach? Or any ideas on how to better handle this situation?
Thanks Mozzers!
-
Excellent, thank you Chris.
I would prefer to keep the URL path the same, but to be honest the original URL path is a bit of a mess, so I'm taking this opportunity to clean it up.
Really appreciate your help on this!
-
Your proposed redirect strategy looks good. If possible, I would keep the same URL path on the www subdomain. That way, when you're finished, you could simply remove the 302 redirects.
1. I would keep the redirects in place until the new content on the www subdomain is live.
2. Personally, I would avoid using the canonical tag in this situation. Google treats this as a hint and not a directive. If your content is too different, Google might just ignore the canonical tag and index both versions. As well, if you use the canonical tag from the ww2 domain to www subdomain, Google will only view the www subdomain content quality. If your content/UX is better on the ww2 subdomain, you won't receive any of that SEO benefit during that time.
-
Hi Chris,
Thanks for getting back to me. That's sound advice, and it makes perfect sense. So, I will do the following:
302 redirect
from www.mydomain.com/old-version-of-page
to www2.mydomain.com/new-version-of-pageThen, once we are ready to publish the new content on to the main www domain, I will do the following because the new URL string will be slightly different from the original:
301 redirect
from www.mydomain.com/old-version-of-page to www.mydomain.com/new-version-of-pageDoes that make sense?
Just a couple of other questions, if that's okay:
- How long do you think the 302 redirects can stay in place? It may have to be there for 12 - 18 months, while we're developing the rest of the new site.
- I came across this article at the weekend, which suggests the following for the www2 temporary version of pages: (1) pointing a rel=canonical tag from the temporary pages to the main pages, and (2) using the meta robots content="noindex" tag to tell search engines not to index the temporary pages. Would you agree with this approach?
Thanks again!
-
Got it!
While I've been a pretty heavy advocate against them, this might be a situation where using 302 (temporary) redirects is the best option. The current plan will tell Google:
- The site is permanently moving the content to the ww2 subdomain
- The site is now permanently moving the content back to the www subdomain.
Instead by implementing 302 redirects gradually as the content goes live, you would send stronger signals that this is only a temporary move.
Let me know if you have any questions on this, would be happy to chat more: chris.long@gofishdigital.com
-
Hi Chris,
Thanks for replying, I really appreciate it.
In answer to your first question... we will be incrementally adding new content on the www2 subdomain, 301 redirecting from existing content on the www subdomain. This will be done gradually, over around 24 months, until all of the www content can be 301 redirected to www2 - and a full site is in place on the www2 subdomain. At this point, once everything is on the www2 subdomain, we will then do one final migration to move all new content on www2 back to the www domain, as we don't want our primary domain to be the www2 subdomain long-term.
The content will be similar, but more engaging and richer on the www2 subdomain. But, because 301s will be implemented incrementaly when the new content is launched on www2, there will no duplicate content across the subdomains.
The TLD will remain the same throughout this process.
I hope that answers your questions - let me know if you need any more clarity.
Thanks again!
-
So if I understand it correctly, you're going to be incrementally adding new pages on the ww2 subdomain while content still exists on the www subdomain. This will be done slowly until all of the www content can be 301 redirected to ww2?
If that's the case, there's a few other things that could be helpful to know:
- What's the expected timeline to get all of the new ww2 pages live?
- How similar will the ww2 content be to the www content?
- Is the TLD staying the same and only the subdomain changing?
Ideally, everything would be added to the production site and redirected all at once.
However, if that isn't an option I'd probably try to implement the redirects from www to ww2 incrementally as well. Otherwise, Google will be able to crawl/index content from both the www and ww2 subdomains, leading to duplicate content issues. I'd try to keep the website architecture fairly consistent between the two so preserve the UX/equity signals between the two subdomains.
It's tough to give insights without more information, so I'd be happy to chat more about this!
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
-
Phasing in new website - new content on www2
Hi Mozzers, I'm working on a large website redesign / redevelopment project. New sections of the website will be phased in over the next 12 months. The plan is to launch all new content on a subdomain (www2.domain.com) while the old site remains on www.domain.com. There will be no duplicate content across the www and www2 sites, as old content will be removed on www as it is replaced with new content on www2. 301 redirects will also be setup from old content on www to new content on www2. Once the new site on www2 is complete, everything will be moved to www, with a robust 301 redirect setup in place. Is this approach logical, and can you see any SEO implication for managing the migration in this way? Thanks!
Intermediate & Advanced SEO | | RWesley0 -
We are redesigning our existing website. The domain is staying the same, but the sub-structure and page names are changing. Do I still need to do 301s?
We are redesigning our existing website. The domain is staying the same, but the sub-structure and page names are changing. Do I still need to do 301 redirects or will search engines know to remove the old 404 pages from the SERPs? We are redesigning our existing website. The domain is staying the same, but the sub-structure and page names are changing. Do I still need to do 301s?
Intermediate & Advanced SEO | | GrandOptimizations0 -
Moving to a new domain name - 301 redirect NOT an option
Hi everyone My question concerns moving from an old to a new domain name without losing all previous SEO efforts. I am aware that a properly executed 301 redirect is the answer and way to go as well as telling Google about it in Webmaster Tools. However, what is the situation, if you do not own the old domain name anymore? If you have no means of getting back the old domain name and wanting to basically mask/switch the already existing website to the new domain name, will search engines penalise the "new site" as a duplicate, since the "old site" is still in the search engine rankings? I know that not being able to execute a proper 301 redirect and starting out with a new domain means a fresh start, but what is the best way to minimise the negative impact (if any)? Basically dropping the sites' current content and starting out new in favour of the new domain name is not really an option. Even if you were to take the content from the old site and place it on another site, this would surely be seen as duplicate too. Anyone thinks that Webmaster Tools/Google is savvy enough to spot the difference when the "old site" gets removed and the "new one" added instead (in Webmaster Tools). I read something along the lines about having your host point the DNS from the old site to the new one. Could something like be helpful? Thanks all in advance for your help and input!
Intermediate & Advanced SEO | | Hermski0 -
Do you get links from new websites?
There's a new industry specific website that looks decent. It's clean and nothing spammy. However, it's so new it's DA is under 10. Is it worth pursuing a link from a site like this? On one hand, there's nothing spammy and it is industry specific. On the other...it's just DA is so terrible (worse than any of our other links), I don't want it to hurt us. Any thoughts? Ruben
Intermediate & Advanced SEO | | KempRugeLawGroup1 -
Merging Domains
Up until last week, we had separate domains for each of our 3 products. We've now merged two products to sit under one URL. The merge coincided with a CMS upgrade which effectively killed all of our old URLs save for the homepage. Is it best for me to 301 the old homepage to it's new place, as well as the rest of the old site's top pages to according pages on the new site? Or is there a better solution?
Intermediate & Advanced SEO | | taylor.craig0 -
Does Google make continued attempts to crawl an old page one it has followed a 301 to the new page?
I am curious about this for a couple of reasons. We have all dealt with a site who switched platforms and didn't plan properly and now have 1,000's of crawl errors. Many of the developers I have talked to have stated very clearly that the HTacccess file should not be used for 1,000's of singe redirects. I figured If I only needed them in their temporarily it wouldn't be an issue. I am curious if once Google follows a 301 from an old page to a new page, will they stop crawling the old page?
Intermediate & Advanced SEO | | RossFruin0 -
301 redirects within same domain
If I 301 redirects all urls from http://domain.com/folder/keyword to http://domain.com/folder/keyword.htm Are new urls likely to keep most of link juicy from source url and maintain the rankings in SERP?
Intermediate & Advanced SEO | | Bull1350 -
Sub domain will not index - Next plan of action?
I'm not sure exactly what option i should take next. but i'll run you through a few points: The page is optimized to a rank "A" The page has 350 backlinks* a strong social presence Interlinking pages. High domain authority an OK page authority The domain ranks highly Every other sub domain rank highly. I make a search and the first page that ranks for this domain is a product page within the exact sub domain i'm trying to rank for, followed by some external blogs I've written and then the rest of the product pages. I've submitted the URL to web master tools twice and yet it still will not rank for that keyword. The only time i see the page index is if i copy the exact URL into Google. Any help on this would be greatly appreciated. Thanks
Intermediate & Advanced SEO | | Martin_Harris0