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
-
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 -
HELP! IE secure page display issue on new live site
For some reason IE 7, 8, & 9 do not display the following page: https://www.jwsuretybonds.com/protools.htm All they show is the Norton seal. It shows properly in all other browsers without issue (including IE 10+), but the earlier versions flash the page for a split second, then hides everything. Can someone shed some light on this? This is a new live site we just launched minutes ago and these browsers account for 12% of our overall traffic. UGH I hate you microsoft!!! Thanks all 🙂
Web Design | | TheDude0 -
HTTPS redirecting to subdomain; do I need to 301 to HTTP first?
Hello there, quick question on HTTPS downgrade to HTTP. Originally, full site was HTTPS. Redesign eliminated need for secure layer. Site currently has https 301'd to sub.domain.com. Ideally, site would live at domain.com, but with the old site having been indexed https, the security warning triggers when you visit, hence the 301 to a subdomain. Thinking possible solutions here are to a) add back in secure layer or b) 301 all old https pages to new http pages. Have I overlooked something? With (a), I will see no SEO impact, correct? With (b), can I expect impact similar to a relaunch? Have seen a lot of chatter that there is some impact in switching http to https, but not much the other way. Any help much appreciated!
Web Design | | alimo0 -
How to redirect special pages to new domain?
Hello. I have 2 websites in diffrent category and i want to move some of my visitor that arrived in specific page of doamin1 (url like this: http://example.com/pages/.........)to root of domain 2.
Web Design | | vahidafshari450 -
Implementing a new Nav Bar: Best practice, SEO benefit, your suggestions?
Hi Mozland, We are going to have a new Nav Bar for our site built from the horror that we currently have to up with. We want to make it a simple affair, similar to The Guardian two-tier Nav Bar - main menu which will drop down to the 2nd tier according to what you clicked on in tier one. Regular stuff, I think. Any suggestions, from your experience, about how best to implement this, what to include, what not to do, what can be included and done to make it as best it can be to get people to peruse our site as easily as possible? Thanks
Web Design | | Martin_S0 -
New URL Strucutre
Hello all! I'm new to SeoMoz and would like to introduce myself and say thanks for all of the great content. This is definitely the premium website I have been looking for. My question is regarding a new URL structure that will be implemented with our website redesign. We are looking to make our URL's more user and SEO friendly. We will be using 301 redirects to reroute our existing structure when the site goes live. Background
Web Design | | kauffmantire
I work in a company that retails automotive tires. I would consider class (performance, off-road, highway, etc.) to be the most important category, but based on our analytics we receive much more traffic from brand terms. This is most likely because our customers are not educated on specific tire classes and generally do head term searches or search by brand / product name. Ultimately the will have to buy from a certain class based on driving habits. Link and URL Structure
(Parameters) The model page includes links to individual tire size specific pages. We are using the model page as our primary SEO page because the only difference from the 5 - 60 tire size specific pages per model will be the tire size itself. This means that all of the remaining content will be duplicated multiple times over. All links to the tire size specific page from the model page will have a rel="nofollow" attribute attached to it. All tire size specific pages will have a rel="canonical" tag pointing back to the model page Out of the following structures, which would you consider to be the best format: 1. http://www.company.com/category/brand/model
or
2. http://www.company.com/brand/category/model
or
3. http://www.company.com/tires/category/model We will append the specific tire-size to the URL on the item specific pages. Any other options or strategies will be greatly appreciated. Thanks in advance for your help!0 -
Can "poor" subdomains drop PR of the root domain?
The page rank of my company's website has dropped from a 6 to a 4 over the past year or so. In that time, we implemented subdomains for development sites to show clients progress on their websites. I noticed that our "dev" sites are being indexed while in development and my question is, will Google drop pagerank of our root domain purely off of these "dev" subdomains? Example - our site is www.oursite.com Dev site - development1.oursite.com I just began investigating the drop and this came to my mind yesterday but am not too sure what type of impact these non-credible subdomains will have on our root domain. Any thoughts?
Web Design | | ckilgore0