Temporary Domain Changes
-
Hi All,
Our development team needs to do a temporary site name change from www.sitename.com to new.sitename.com and then wants to return to www.sitename.com. They need to do this for the whole site due to how it's built with single sign on (SSO) and how certain post login pages utilize pre login pages and need to keep people logged in. This process is changing with a CMS upgrade and website and post login pages will be independent of the pre login pages moving forward.
My question is what is the best way to manage this transition? Right now it seems like the best solution I've been able to work out with development is to reduce the domain shift down to one week and use 302 Redirects, don't index the new.sitename.com site, and for that week and take my lumps as they come from search. Looking for any other suggestion that may help marketing work with dev without casting blame on any teams for drops in organic traffic.
-
Hi everyone
I'm in the same boat too. If either Tim or Dan (or anyone else) have any learnings besides the advice shared here please do.Thanks, Kayley
-
Hi Dan,
I was wondering how this all turned out for you? I'm in a similar boat right now. Any advice you can share?
Thanks,
Tim
-
Thanks Paul,
I'll try to make sure to keep an eye on this site move as it's much different than any other site moves i've implemented and it's incredibly tricky.
Dan
-
I suspect your idea for 302ing to the temp new URL is probably the best you can do given the circumstances, Jeff. The alternative would be to leave the domain the same and have all pages return a 503 header with a Retry After header indicating a time span after the return to the normal site. But this is more invasive and probably more prone to errors. If the 302 redirect stays in place for too long, search indexers may start to consider it permanent despite the 302 status, but keeping it to one week likely shouldn't cause this.
My suggestion from a marketing perspective - I would make the temp site be something like www2.sitename.com instead of "new". This way, most visitors are unlikely to even notice. If they see the "new.sitename.com" site for a week, then are put back on what they now consider the "old" site - they may think they're getting shortchanged or something is wrong that they're no longer getting the "right" version of the site.
The other thing to make sure you've checked on - what other 3rd-party integrations/tools/advertising networks/analytics etc will need to be addressed while the redirect is in place? (For example, Adwords and many ad platforms don't look kindly on ads that redirect from their display URL to a new URL.) So make sure you've checked out and adjusted for any of those. Your SSL certificate and SMTP/site notification email sending functionality are other examples.
And yea, communication and setting expectations will be key here. If the devs truly can't accomplish what they need to any other way than such a major upheaval, everyone needs to be clear that all steps will be taken, there is a plan for the move, for the return, and for monitoring and trying to compensate afterwards (like maybe some extra PPC ready to go if a significant traffic drop will require recovery time?). But there are significant unknowns and while every effort will be made to minimise impact, things beyond your control will have possible negative effects and it's impossible to know in advance how severe they might be. You'll want a clear communication plan for all stakeholders of each of these steps in advance. You don't want to be trying to come up with the communications while in the middle of the process.
Sounds like an opportunity for an interesting case study - be sure to let us know how it goes. Good luck!
Paul
[Edited to add - verifying a new GSC property for the new subdomain(but not submitting any sitemap or fetch) would be a good idea. That would let you monitor whether any of the site was getting indexed. Then as soon as the site goes back to normal and the temp site is 301-redirected back, you could use it to declare a change of address back to the main site to help get any of the temp URLs out of the index faster, (assuming any get indexed) ]
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
-
Domain migration nightmare - what is wrong?
Domain migration nightmare - what is wrong? Domain migration nightmare - what is wrong?
Intermediate & Advanced SEO | | PSOM1010 -
Subdomain replaced domain in Google SERP
Good morning, This is my first post. I found many Q&As here that mostly answer my question, but just to be sure we do this right I'm hoping the community can take a peak at my thinking below: Problem: We are relevant rank #1 for "custom poker chips" for example. We have this development website on a subdomain (http://dev.chiplab.com). On Saturday our live 'chiplab.com' main domain was replaced by 'dev.chiplab.com' in the SERP. Expected Cause: We did not add NOFOLLOW to the header tag. We also did not DISALLOW the subdomain in the robots.txt. We could have also put the 'dev.chiplab.com' subdomain behind a password wall. Solution: Add NOFOLLOW header, update robots.txt on subdomain and disallow crawl/index. Question: If we remove the subdomain from Google using WMT, will this drop us completely from the SERP? In other words, we would ideally like our root chiplab.com domain to replace the subdomain to get us back to where we were before Saturday. If the removal tool in WMT just removes the link completely, then is the only solution to wait until the site is recrawled and reindexed and hope the root chiplab.com domain ranks in place of the subdomain again? Thank you for your time, Chase
Intermediate & Advanced SEO | | chiplab0 -
Community inside the domain or in a separate domain
Hi there, I work for an ecommerce company as an online marketing consultant. They make kitchenware, microware and so on. The are reviewing their overall strategy and as such they want to build up a community. Ideally, they would want to have the community in a separate domain. This domain wouldn't have the logo of the brand. This community wouldn't promote the brand itself. The brand would post content occassionally and link the store domain. The reasoning of this approach is to not interfere in the way of the community users and also the fact that the branded traffic acquired doesn't end up buying at the store I like this approach but I am concerned because the brand is not that big to have two domains separated and lose all the authority associated with one strong domain. I would definitely have everything under the same domain, store and community, otherwise we would have to acquire traffic for two domains. 1. What do you think of both scenarios, one domain versus two? Which one is better? 2. Do you know any examples of ecommerce companies with successful communities within the store domain? Thanks and regards
Intermediate & Advanced SEO | | footd0 -
Which Domain is better
Which domain is better for SEO. vehiclewrapslasvegasnv.com Or vehicle-wraps-lasvegas-nv.com Thanks in advance for your help.
Intermediate & Advanced SEO | | AlexanderWhite0 -
Should I redirect my Google Update Effected Domain to brand new Domain?
Hey Moz experts, I had a domain which was really doing better but after the Humming Bird update my traffic was decreased up to 90%. There are plenty of posts on my existing blog, Now what should I do? I mean should I redirect it to a brand new domain or Copy all the posts to a brand new domain and delete my existing domain? Note that the Old domain has PR1, DA 19 and PA 30.
Intermediate & Advanced SEO | | imran20780 -
Is it safe to redirect our .nl (netherlands) domain that we have just purchased to our .com domain?
Hi all! We've recently developed a German version of our website with German translation and now we have just purchased a .nl domain, but with this one, we want all of the copy to remain in English. Is it ok to redirect our .nl domain to our current .com website or will this give us bad SEO points? Thank you!
Intermediate & Advanced SEO | | donaldsze0 -
Help needed for a domain
I have a small translation agency in Brazil (this website), totally dependent on SEM. We are in business since 2007, and we were on top position for many relevant keywords until the middle of 2011, when the ranking for the most important keywords started dropping. In that time, we believed that we needed to redesign the old static website and replace it by a new modern one, with fresh content and with weekly updates, which we did, and it's now hosted on Squarespace. I took care to keep the old links working with 301 redirections. When we made the transfer from the static site to Squarespace (Mar/2012, see the attachment), the ranking dropping became even more serious. Today, we have less than 50 unique visitors per day, in a total desperate situation! To make things worse, we received an alert from Google on 23/September/2012 talking about unnatural inbound links, but Google said that "As a result, for this specific incident we are taking very targeted action on the unnatural links instead of your site as a whole", so we thought we didn't need to worry about. Google was correct, I worked many hours to register our website in web directories, I thought there would be no problem since I was doing this manually. My conclusions are: Something happened prior to Mar/2012 that was making us losing territory. I just don't know what! The migration to Squarespace was a huge mistake. I lost control over the html, and squarespace doesn't do a good job optimizing the pages for SEO. We also were also blasted by Penguin on September, but I believe this is not the main cause of the drop. We were already running very badly at this time. My actions are: a) I generated a DTOX report and I'm trying to clean up the links marked as toxic. That's a hard work! After that I will submit a reconsideration request. b) I'm working on the site: Improving internal link building for relevant keywords Recently I removed a "tag cloud" which I believe was hurting my SEO. Also, I did some redirections that were missing. c) I trying to generate new content to improve link building to my site. d) I'm also considering to stop putting all my coins on this domain, and maybe start a fresh new one. Yes, I'm desperate! 🙂 I would appreciate a lot to hear from you guys, expert people! Thanks a lot, MWcEdPa.png?1
Intermediate & Advanced SEO | | rodrigofreitas0 -
Consolidate 150 domains to 1
Hi! Just as the questions tell we are looking at a project where we might have to consolidate 150 different domains into 1 (of course with a corresponding page on the new domain). We aim at preserving as much of the linkjuice as possible from each domain. Any advice on doing this propely? I, of course, see a risk of opening the new domain and just redirecting (301) the old domains to the specific page on the new domain but is there any right or wrong way of doing this? I might add that each domain has a more or less unique linkprofiles in terms om linking domains, number of linking domains and such. Our dear friend Cutts has some information on this topic, http://www.youtube.com/watch?v=l7M22teF3Ho but he only talks about 4 domains - which of course seem like a bit more natural occurring phenomenon. But what about 150 of them? Anyone got any advice? Is this as much of a no-go that I feel it is? Thanks! Edit: There domains are all owned by the same entitiy, share the same GWT and such.
Intermediate & Advanced SEO | | bebetteronline0