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: [email protected]
-
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
-
Planning to transition to a new website domain - should I press pause on SEO initiatives?
Hello - my company is planning to transition to a new website domain sometime this year, probably about six months from now. Our current website does not currently get much organic traffic from unbranded search terms. I would really like to fix that by publishing lots of new blog posts and trying to get more backlinks. But with the website transition on the horizon, I'm wondering if I should hold off on posting new pages and getting backlinks for the time being. Then once the new website is live, I can start to ramp things up. What would you do in this situation? Also, does anyone know of any thorough guides or walk-throughs that cover all of the best practices (re: SEO) when migrating to a new website domain?
Intermediate & Advanced SEO | | collinburkewg0 -
Why does my old brand name still show up on organic search but as my new brand name and domain?
Hello mozers! I have quite the conundrum. My client used to have the unfortunate brand name "Meetoo" - which by the way they had before the movement happened! So naturally, they rebranded to the name Vevox in March 2019 to avoid confusion to users. However, when you search for their old brand name "Meetoo" the first organic link that pops up is their domain www.vevox.com. Now, this wouldn't normally be a problem, however it is when any #MeToo news appears in the media and we get a sudden influx or wrong traffic. I've searched the HTML and content for the term "Meetoo" but can only find one trace of this name through a widget. Not enough to hold an organic spot. My only other thinking is that www.vevox.com is redirected from www.meetoo.com. So I'm assuming this is why Vevox appear under the search term "Meetoo". How can I remove the homepage www.vevox.com from appearing for the search term "meetoo"? Can anyone help? AvGGYBc
Intermediate & Advanced SEO | | Virginia-Girtz3 -
Website structure - best tools to analyse and plan, visually
Hi - I am about to analyse and then re-plan the structure of a website and think it would be best to do it graphically - in the form of a chart. Are there any tools you would recommend to visualise the structure of an existing website (perhaps something that can scan and then represent a websites) - or plan out a new/revised website? Thanks in advance, Luke
Intermediate & Advanced SEO | | McTaggart0 -
Domain dominance
I've just started to work for a company who've purchased masses of domains with every conceivable permutation based on all their products with every extension possible e.g .biz . eu. .net (including .co.uk and .com of course). I have two questions: 1. Is it worth keeping all these (they want to add more) domains or let them expire? 2. All the purchased domains are online - is there any point (they redirect with a 301)?
Intermediate & Advanced SEO | | LJHopkins0 -
Urgent Site Migration Help: 301 redirect from legacy to new if legacy pages are NOT indexed but have links and domain/page authority of 50+?
Sorry for the long title, but that's the whole question. Notes: New site is on same domain but URLs will change because URL structure was horrible Old site has awful SEO. Like real bad. Canonical tags point to dev. subdomain (which is still accessible and has robots.txt, so the end result is old site IS NOT INDEXED by Google) Old site has links and domain/page authority north of 50. I suspect some shady links but there have to be good links as well My guess is that since that are likely incoming links that are legitimate, I should still attempt to use 301s to the versions of the pages on the new site (note: the content on the new site will be different, but in general it'll be about the same thing as the old page, just much improved and more relevant). So yeah, I guess that's it. Even thought the old site's pages are not indexed, if the new site is set up properly, the 301s won't pass along the 'non-indexed' status, correct? Thanks in advance for any quick answers!
Intermediate & Advanced SEO | | JDMcNamara0 -
301 many smaller domains to a new, large domain
Hi all, I have a question regarding permanently redirecting many small websites into one, large new one. During the past 9 years I have created many small websites, all focusing on hotel reservations in one specific city. This has served me beautifully in the past, but I have come to the conclusion that it is no longer a sustainable model and therefore I am in the process of creating one large, worldwide hotel reservations website. To not loose any benefit of my hard work the past 9 years, I want to permanently redirect the smaller websites to the correct section of my new website. I know that if it is only a few websites, that this strategy is perfectly acceptable, but since I am talking about 50 to 100 websites, I am not so sure and would like to have your input. Here is what I would like to do: (the domain names are not mine, just an example) Old website: londonhotels.com 301 to newdomain.com/london/ Old website: berlinhotels.com 301 to newdomain.com/berlin/ Old website: amsterdamhotels.com 301 to newdomain.com/amsterdam/ Etc., etc. My plan is to do this for 50 to 100 websites and would like to have your thoughts on if this is an acceptable strategy or not. Just to be clear, I am talking about redirecting only my websites that are in good standing, i.e. none of the websites I am thinking about 301'ing have been penalized. Thanks for your thoughts on this.
Intermediate & Advanced SEO | | tfbpa0 -
Redirect 301
Hi, I `m redirecting some pages in htaccess The first 15 pages that i redirected it worked. But the last 3 dont work, and i cant figure it out why it is not working. Redirect 301 /analyseverktoy/ /webanalyse
Intermediate & Advanced SEO | | SGacic
Redirect 301 /index.php/ledige-stillinger/ /
Redirect 301 /?page_id=352/ / Anu suggestions?0 -
Redirect non www. domain to WWW. domain for established website?
Hey guys, The website in question has been online for more than 5 years but there are still 2 versions of the website. Both versions are indexed by Google and of course, this will result in duplicate content. Is it necessary to redirect the non-www domain to the www. domain. What are the cons and advantages? Will a lot of organic traffic be lost at first (if non-www are getting a good amount of traffic)? Thanks.
Intermediate & Advanced SEO | | BruLee0