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
-
Mobile-First Indexing New Site monetized with Adsense AMP or not?
I am considering developing a new site monetized with Adsense. I am wondering if it's still worth bothering with AMP, it will take some work to get the functionality I have in mind working on these pages due to the inherent limitations. Has anyone got any insights in terms of current and future benefits of AMP in terms of ranking benefits and Adsense earning potential?
Web Design | | GrouchyKids0 -
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 -
Is it cloaking/hiding text if textual content is no longer accessible for mobile visitors on responsive webpages?
My company is implementing a responsive design for our website to better serve our mobile customers. However, when I reviewed the wireframes of the work our development company is doing, it became clear to me that, for many of our pages, large parts of the textual content on the page, and most of our sidebar links, would no longer be accessible to a visitor using a mobile device. The content will still be indexable, but hidden from users using media queries. There would be no access point for a user to view much of the content on the page that's making it rank. This is not my understanding of best practices around responsive design. My interpretation of Google's guidelines on responsive design is that all of the content is served to both users and search engines, but displayed in a more accessible way to a user depending on their mobile device. For example, Wikipedia pages have introductory content, but hide most of the detailed info in tabs. All of the information is still there and accessible to a user...but you don't have to scroll through as much to get to what you want. To me, what our development company is proposing fits the definition of cloaking and/or hiding text and links - we'd be making available different content to search engines than users, and it seems to me that there's considerable risk to their interpretation of responsive design. I'm wondering what other people in the Moz community think about this - and whether anyone out there has any experience to share about inaccessable content on responsive webpages, and the SEO impact of this. Thank you!
Web Design | | mmewdell0 -
How to bounce back after a new url & new site design?
About a month ago, my company changed domains (from the long-established www.imageworksstudio.com to the new www.imageworkscreative.com) and also did a complete overhaul of our site. We tried to do everything necessary to keep Google happy as we went through this change, but we've suffered a drastic loss of both rankings and traffic. I know that can happen as a result of a redesign AND as a result of a new domain, but I'm wondering how long you would expect it to take before we bounced back and also, what can we do in the meantime to improve?
Web Design | | ScottImageWorks0 -
Subdomains For Real Estate Website
I am currently working on a proposal for a clients Wordpress website development which includes ongoing SEO after the website is developed. I have looked into a number of options and the one that seems the most cost effective involves using subdomains for the individual listings pages. What I want: clientsdomain.com/listings/idxnumber/ What I can get for a decent price: listings.clientsdomain.com/idxnumber/ So the majority of the website will actually exist on a subdomain because the IDX API will automatically populate pages for all of the MLS listings in the area (hundreds or thousands). Meanwhile the domain itself will have all the neighborhood pages and other optimized content, blogs and whatnot. My concern is that dividing the website like this will have negative effects on SEO. There wont be duplicate content across subdomain and main domain, but they will share a lot of links back and forth. I haven't found any recent sources on the topic. Almost everything I have found says that dividing a website in this manor is bad for SEO, but these articles are often many years old. Does anyone know of a Wordpress plugin/IDX company that can provide a solution that doesn't use a subdomain and actually just lists each MLS page within a directory? I am open to using another platform, I am just most familiar with Wordpress. Will using a subdomain in the ways mentioned above have a profound negative effect on SEO? Thank you for your time in responding, I greatly appreciate it.
Web Design | | TotalMarketExposure0 -
Is it worth upgrading php to accomodate new WP version?
my client revisitors.com has a blog blog.revisitors.com that we cannot update to a newer WP version 3.5.1 because his php version apparently must be upgraded first. You cannot update because WordPress 3.5.1 requires PHP version 5.2.4 or higher. You are running version 5.1.6. according to client it would be potentially hazarardous for him to upgrade the php but we cant update or add new plugins because we arent running the current version of WP what is worse? i am responsible for his blog but i feel handicapped bigtime - at the same time i dont want him to do something that could wreck his site functionality either any suggestions? or advice here? thanks
Web Design | | Ezpro90 -
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