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
-
Internally linked pages from different subdomain must be well optimised?
Hi all, We have guide/help pages from different subdomain (help.website.com). And we have linked these from 3rd hierarchy level pages of our website (website.com/folder1/topic2). But help.website sumdomain & pages are not well optimised. So, I am not sure linking these subdomain pages from our website pages hurts our rankings? Thanks,
Web Design | | vtmoz0 -
App indexing with several subdomains
Hi, We are currently in the process of getting our app developed. From an SEO point of view I want the app to get indexed and am currently trying to get a step by step guide for it. I've come across this helpful guide: https://moz.com/blog/how-to-get-your-app-content-indexed-by-google but need to go a bit deeper now. Questions I have is related to the "apple-app-site-association" file As far as I could find out the JSON code of that file has the following syntax: {_ “applinks”: {__ “apps”: [],__ “details”: [__ {__ “appID”: “9JA89QQLNQ.com.my.bundle.id“,__ “paths”: [ “/myPath1”, “/myPath2/*” ]__ },__ ]__ }_ } My question is related to the key "appID" I'm wondering how the entry would look like if I have 10 country subdomains and would like to make sure that the deep link clicked in the browser is going to the right subdomain page within the app. Current website structure:
Web Design | | FashionLux
uk.example.com/english-path/
de.example.com/german-path/ Many Thanks in advance0 -
New Mobile Site Traffic Drop
With all the talk about how much mobile is important and how it is going to return its own search results, we finally decided to make a mobile site for one of our smaller websites to test the water. We put it up about two weeks ago and did Vary HTTP header method to serve the site. Before the change, on the average week we would get 270-300 mobile visitors from organic search results and we converted 0.78% to sales. Since the change, we are now getting about 70 mobile organic visitors per week but converting 2.47% So what can I say but WOW. We are converting way way better but our organic mobile search traffic has dropped off a ton. Luckily our desktop and tablet traffic(we serve the desktop version of the site to tablets) has stayed the same and has not dipped. Do any of you guys have experience or gone through launching a mobile site before? Did you see the immediate drop in organic mobile traffic and did you recover your traffic back to previous levels? If so, do you know how long it takes to recover? I am thinking it is a big change and will take time for Google to adjust but I am not sure since the mobile version has so much less text now on the home page and on category or product list pages or whatever you guys want to call them.
Web Design | | KurtL0 -
New website and new domain
Hi, We have a domain with current e-commerce site on, about 5 years old. We have a new website being built with a different company and a new domain name. We are transferring our old domain over to new provider and 301'ing the domain to new domain. However, we can not take the current website with us, so we lose all our links/pages etc.. How important would it be to take a wrap of our current website to keep all the pages alive? Is there anything we can do so oldurl.com/brand/tshirt/ doesnt lose its rank? Can we 301 individual pages if we dont have the actual website? Just the domain name. Any help be great. Thanks
Web Design | | YNWA0 -
301 Redirect from Old Domain to New Domain
I am building a new website and I plan to 301 Redirect my Old Domain (olddomain.com) to a brand new Domain (newdomain.com) in the upcoming months. To do this I was planning to update the htaccess file on both the old and new domains. The htaccess file on the old domain would look to 301 redirect all pages on the old domain to the new domain. The htaccess file on the new domain would detail any specific URL redirects I want to implement (ie. olddomain.com/EXAMPLE/TEST will redirect to newdomain/TEST) - this will ensure link equity is retained and bounce rates are kept at a lower level. Does this sound like the right approach? Also, what do I need to do with the old domain going forward? Do I need to keep this forever in order for the 301 redirect to work or can I eventually just forward the domain to the new one permanently?
Web Design | | DHS_SH0 -
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 -
Having a new website build, what happens to my SEO work?
Hi, We are in the process of having a new website developed by a web agency. New domain, new business name etc... What is the best process to transfer from old domain to the new one? What happens to all my ranked URLs? What can re-directs do to help me? Will I loose all my link juice on highly ranked keyword domains? I ranked 1st for a brand now, wil lthis go? Any advice, help or hints would be great. Thanks Will
Web Design | | YNWA0 -
Subdomain vs Sub Folder
Hi. This is my first question here guys and gals so please be gentle. We are creating a town based website that will hold news, events, articles and relevant local content. We are also creating a business directory that will be part of this. My question relates to an issue we have regarding how the directory will be treated as part of the "network". Although we aren't 100% sure on the domain name yet, we want the directory to be found as easily as the domain itself. Even better, if the two could be treated seperately but strengthen the overall theme for the domain we'd be in keyword heaven. Therefore in your opinion (hopefully with pro's and con's) which do you think will rank better in Google, Yahoo and Bing (or all three);
Web Design | | rufo
The directory seperate as a subdomain or as a folder within the main domain? So for example - providing we are including links between the two sections and the site is www.sitetown.com Which is better for the directory itself? http://www.sitetown.com/directory http://directory.sitetown.com or you're mad Steve, use a seperate domain altogether www.sitetowndirectory.com I hope you can help, obi-wan, you're my only hope..... PS - seomoz still rocks. Thanks
Steve0