Gradual roll out of new webpages on temporary subdomain
-
I’m working for a company who is looking to gradually replace an existing website with a new website.
They will replace the homepage, then a section, then another section, and so on, until the new site is complete.
All new pages will sit on a temporary subdomain.
So, for example, the URL for the homepage at the moment is www.domain.com, but as soon as the new homepage is ready, that will be launched on a temporary URL / subdomain - www2.domain.com - replacing the old homepage.
The new pages will then gradually increase on www2.domain.com (so journeys will inevitably move across domains) until the whole of the new website is ready on www2.domain.com - at which point it will move on to www.domain.com.
I know this isn’t a good way of doing things - I would much prefer the new site is completely built and then it just replaces the old site with the necessary 301 redirects in place - but the company wants to see the gradual roll out of new page designs.
So, my question is, what’s the best way to manage this without negatively impacting rankings for the existing domain (www.domain.com)?
-
The most important is to redirect all your backlinks via 301 to the new URLs. As you've been told, why not develop the entire site in the subdomain and then move it to the new one, so you don't play with redirects and traffic from one subdomain to another.
-
I'm not sure how the search engines look at 302 redirects which are in place for a prolonged time. I'll be interested to see if anyone else on this thread has additional insights about that. What I can say is that I've used 302 redirects in some cases for prolonged period of time (although not as long as 12-18 months, perhaps more like 4-6 months) and have not experienced issues from that approach. But others on this forum may have more experience with 302 redirects over that period of time.
The other thing I'll mention is that some tools like Moz Pro will report 302 Redirects as "issues". My perspective is to look through these because some might be unintentional, and then to ignore when they are inentional/strategic.
-
Hi seoelevated,
Thanks for your response. I have been considering a 302 approach, but I am concerned about how long I can leave 302s in place. If from start to finish, the roll out takes 12 - 18 months, will that cause any problems?
Thanks!
-
Unless I'm missing something in the thread here, it seems to me this would be better served by 302. My rationale is that you will be eventually going back to the www URL and you want that to retain the full equity of all its links. So, during the interim period, you would have 302 redirects, and then when you switch back to www, you would simply remove all the redirects.
The only downside I see to that is that during the interim period, one thing you won't be able to measure as the site is gradually updated, is the incremental impact of the new page designs on SEO. You will still be able to measure the new page design in terms of conversion rate and other UX factors, but measuring impact on SEO wouldn't really be feasible.
-
Yes, I got it. That's the only option to do this if you want to pass link juice to www2.domain.com while you are working on the new site. There is no way to not lose traffic if you want to redirect everything on the page by page basis. Traffic will bounce back after you move back to www.domain.com, but it can takes time.
Ross
-
Hi Ross.
Everything will have a 301.
For example:
- When I launch the new homepage on the temporary subdomain, I will add a 301 redirect from www.domain.com to www2.domain.com.
- When I launch a new section page, I will add a new 301 redirect from www.domain.com/section1 to www2.domain.com/section1.
- When I launch a new product page, I will add a new 301 redirect from www.domain.com/product1 to www2.domain.com/product1.
And then, eventually, when everything is moved back to the www domain, I will setup the following 301 redirects:
- Homepage - From www2.domain.com to www.domain.com
- Section page - From www2.domain.com/section1 to www.domain.com/section1
- Product page - From www2.domain.com/product1 to www.domain.com/product1
Does this make sense? So, everything will have a 301 redirect.
I'm just concerned about the fact I'm basically having to 301 redirect a whole site away from it's original domain to a temporary subdomain, and then back again. Should I be concerned about this?
-
The only problem I see here that you will lose traffic by setting 301s to www2 and then removing those 301s.
Ross
-
Hi Ross.
Thanks again for the response.
There will only ever be one version of a page, and each time an old page is replaced with a new version, I will 301 redirect from the www version to the www2 version.
My concern is, at the end of the web build all pages on www will have been 301 redirected to www2, and then I’ll need to 301 redirect them all back again to www when the new site is moved off the temporary subdomain. Do you see any problems with this approach?
-
If not then I would deindex completely the www2.domain.com and do not set up any redirects at all. Just have your www.domain.com working in a normal way until you migrate your www2.domain.com to www.domain.com. Also, If you planning to change the URLs on the new version of the website then you need to set up 301 redirects from old URLs to new URLs on your server ( apache or ngnix) so you do not get any broken links.
Ross
-
Are you planning to have both versions of the site working at the same time?
Ross
-
Thanks for the response.
But is it okay to 301 redirect, for example, the homepage to a temporary www2 subdomain, and then back again once the whole site is ready to move back to the www domain?
-
Hi there,
The most important is to redirect all your backlinks via 301 to the new URLs. Also, you can take a look at this guide.
Ross
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
-
Will There Be Much Impact When Moving Site To New Root Folder?
Hi, ok so I have a pretty big site that is located on my sever /root/current-folder/. I want to rebuild the site completely as it's using software that is out of date and not our main focus anymore (OpenCart). We want to move to a Wordpress platform, but want to have as little impact on the SEO as possible. Our current strategy is: List all URLs/Titles/Meta indexed with Google on current site Create new folder on the server /root/new-folder/ My question is... if I move to a new folder on the server (same TLD) and then re-route the TLD to go to this new folder, will there be more of an impact on SEO that if I start a fresh in the current folder? Thanks
Web Design | | Easigrass0 -
Manufacturer, New Direct-to-Consumer Site (Separate Site, or Sub-Domain?)
Hi All! Working with an established manufacturer, been around for many years, it's an internationally known brand, and their products are sold by thousands on distributors. They recently started a new website (separate from their old established B2B manufacturer site) which will be used to sell direct to customer. The new site is great, with a nice responsive design, clean look, flexible, etc. The problem is, it's a new site with low Domain Authority. The manufacturer's B2B site has been around a while, very high Domain Authority. So, I'd like to be able to harness all the link equity they've build instead of trying to optimize a brand new site. The problem with this old established site is that it IS in fact old. The design is terrible, it's not responsive, old code, bad look and feel, etc. We could incorporate the new B2C site (which has its own CMS) into a sub-domain, like store.site.com. But, I'd worry that site.com's crapiness will limit growth potential for the new pages at store.site.com. Same issue were we to add the new site into a sub-folder, like site.com/store/. On the other side, we could just keep the new site, with it's own domain, sitestore.com, and have product pages and/or category pages from the manufacturer's B2B site link to the relevant pages on the new B2C site. Thanks!
Web Design | | fiberglass0 -
Show new mobile site to 60% users & old mobile site to 40% users
Hi, We are planning to show new mobile site to 60% users & old mobile site to 40% users. We will show the old site to google crawler. Our old site has some interlinking through footer & content whereas the new site does not has it. We wanted to do this since our new site does not supports some browsers. Will there be an issue with Google on showing the site like this. The mobile site & desktop site will have same url across devices & browsers. Regards
Web Design | | vivekrathore0 -
New Google SERPS design - What's Changed?
Has anyone noticed any fall out from the recent redesign of SERP pages by Google? I noticed that there appears to be one less organic result "above the fold" now, so if you were possibly in third or fourth position maybe slight dip in traffic? Any noticeable shift in click through rate with the new bigger font? Also, has anyone noticed if the new design has caused any shift in best practices for on-page meta data like Title tag and description tag counts? I know the Title tag was previously driven by the pixel width of the title in Google SERPS, just curious if that has changed with this redesign.
Web Design | | IrvCo_Interactive0 -
Comparing the site structure/design of my live site to my new design
Hi SEOmoz team, for the last few months I've been working on a new design for my website, the old, live design can be viewed at http://www.concerthotels.com - it is primarily focused on helping users find hotels close to concert venues throughout North America. The old structure was built in such a way that each concert venue had a number of different pages associated with it (all connected via tabs) - a page with information about the venue, a page with nearby hotels to the venue, a page of upcoming events, a page of venue reviews. An example of these pages can be seen at: http://www.concerthotels.com/venue/madison-square-garden/304484 http://www.concerthotels.com/venue-hotels/madison-square-garden-hotels/304484 http://www.concerthotels.com/venue-events/madison-square-garden-events/304484 http://www.concerthotels.com/venue-reviews/madison-square-garden-reviews/304484 The /venue-hotels/ pages are the most important pages on my website - and there is one of these pages for each concert venue - they are the landing pages for about 90% of the traffic on the website. I decided that having four pages for each venue was probably a poor design, since many of the pages ended up having little or no useful, unique content. So my new design attempts to bring a lot of the venue information together into fewer pages. My new website redesign is temporarily situated at: (not currently launched to the public) http://www.concerthotels.com/frontend The equivalent pages for Madison Square Garden are now: http://www.concerthotels.com/frontend/venue/madison-square-garden/304484 (the page above contains venue information, events and reviews) and http://www.concerthotels.com/frontend/venue-hotels/madison-square-garden-hotels/304484 I would really appreciate any feedback from you guys, based on what you think of the new site design compared to the old design from an SEO point of view. Of course, any feedback on site speed, easy of use etc compared to the old design would also be greatly appreciated. 🙂 My main fear is that when I launch the new design (the new URLs will be identical to the old ones), Google will take a dislike to it - I currently receive a large percentage of my traffic through Google organic search, so I don't want to launch a design that might damage that traffic. My gut instinct tells me that Google should prefer the new design - vastly reduced number of pages, each page now contains more unique content, and it's very much designed for users, so I'm hoping bounce rate, conversion etc will improve too. But my gut has been wrong in the past! 🙂 But I'd love to hear your thoughts, and thanks in advance for any feedback, Cheers Mike
Web Design | | mjk260 -
Best Way to Remove Mutltiple XML Sitemaps From Multiple Subdomains
Just found a series of of XML sitemaps hosted like so: http://www.thesite.anothersite.com/sitemap.xml and defaulted to remove and 301 redirect but as this is the first time I've encountered an issue like this, an outside opinion or two would be much appreciated. Is the 301 the best option, should I 404 them or what?
Web Design | | ePageCity0 -
New site - same host domain?
Building a new site for my business (different URL) For SEO purposes...Is it ok to host the site on the same account as my existing site (GoDaddy) or should I purchase a seperate hosting account? Thanks
Web Design | | Tustep0 -
Preserve Rankings When Switching to a New Site
Hello community! I have a quick question for you regarding preserving my SERPs once I switch a development site to replace the current production site. Basically, we are switching to a new CMS and will be featuring the same content, architectural layout, URL structure, etc. Again, the only difference is that it's going to be on a new CMS. Upon switching to the new version of the site, what would be the best strategy for making sure we preserve our rankings for content already ranking highly within the search engines? Likewise, is there anything additional we may be able to do right-off-the-bat in order to assist content that may not be ranking highly in the SERPs, rank more highly?
Web Design | | NiallSmith0