When should you turn off redirects to your new domain?
-
Our website moved to a new domain a year ago, and we have our original domain to redirect to our new domain. We're working on contacting people who still link to our old domain to ask them to update, but 7% of our traffic is still coming as a redirect from our old domain.
My question is, when should we just shut the old domain down entirely and stop redirecting people to our new domain? Or should we just keep it up indefinitely? What would be the positive or negative impact on our new domain's SEO if we shut the old domain down?
Thanks!
-
We're working on it!
-
Are there any metrics you can use from the new site to help convince the higher-ups? Maybe your analytics can show that with the site redesign, people stay on the new site longer, that the bounce rate is lower, conversions are higher, or something you can use to show them that it would be better to have the pages on the new site format?
-
Very true!!
-
Yes and no. There are certain pages on the old domain that still exist, but very few, and we're trying to convince the higher-ups that we should move those pages into our new site. The majority of the old website, though, 301 redirects to our new domain.
-
So the old domain with the old content is still displayed, you're not just sending users to the appropriate page of the new domain with a 301?
-
Our old domain was a sprawling behemoth of a website (we completely redid our website when we changed domains), which is a big part of the reason why we're itching to take it down - not so much the cost issue. But you make a good point, thanks!
-
Keep the domain up there and redirected indefinitely, it's not hurting anything and can only help. And don't let the registration lapse, you don't want a competitor to pick up that old domain and do something with it.
-
Or you could just skip 2 latte's at Starbucks, then you don't have to sweat the 9 bucks to maintain it.
-
As the other responses have said, although it will cost you a yearly fee to keep the website up, (minimal), it is in your interest to keep it up to keep that 7% referring traffic. Check out Open Site Explorer to help you identify the websites that have not added your new link, and contact the webmasters to ask them to change it.
Depending on your target audience, if you turn off the redirects, there is a high chance they will be able to find you if they are looking for you. I guess it would depend on the sites content, and whether the traffic was brand related or search driven.
Aaron
-
Your best bet would be to keep it up. That way any link juice coming from websites linking to your old domain will still carry through to your new domain by using the redirect. Also, if you are still receiving visitors to your old domain, it would be a good idea to continue to keep the redirect alive, just to continue receiving those visits and all potential traffic that would come from the old domain.
I would say, if you stop seeing very much, if any, traffic coming from the redirect, you could do without it. However, if it's a concern over spending the money to renew the old domain, depending on how much it costs, it may or may not be worth it to you.
-
NEVER!
The only downside is the $9.95 you pay to keep the registration. The downside to turning it off are many. You lose the PR that is is passing, even if there is no traffic coming from that old domain it still passes PR! Keep it forever!
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
-
Redirecting http to https, do I need to add new url to webaster tools?
Hey all, we just 301 redirected all our http url's to https. I'm getting some funky data in webmaster tools, such as a drastic change in pages indexed and pages submitted over pages indexed. Might be a dumb question, but do I need to update my website in webmaster tools with the new https address, or should I be getting credible data from the old http url that is already in there? Thank you in advance!
Technical SEO | | jaychow0 -
What to do with a 302 redirect after a while
Hi guys, A client of ours has a website with a very bad linkprofile. We adressed this issue and we migrated the website to another domain. We redirected the bad website (cornelisbedding.be) to the new domain (cornelisbedding.com) with a 302 redirect. We didn't want to pass the bad link juice. The problem we are having now is that we can't afford to lose the redirect on cornelisbedding.be. We would lose to much traffic because the old domain still has alot of links that generate good quality traffic. I have read that Google will treat 302 redirects as 301's in the long run. We really want to avoid this.
Technical SEO | | Jacobe
We were thinking of using a meta refresh with a delay on, but in Google's eyes that would be considered spammy. Are their any other suggestions on how to handle this? Thanks you!0 -
Domain redirect
Recently we launched a site under a new domain, the site is doing well under the URL. Client calls me today and would like to have another domain he owns point to the new site. The domain he has has no history and no content. He is under the impression that people are looking for him by typing in www.domainxyz.com. I attempted to explain otherwise to him, but I lost. Question, what are the drawbacks of taking this domin and doing a perm redirect via . Httpaccess file?
Technical SEO | | VanadiumInteractive0 -
Does redirect of domain alias help rankings?
Yes... It iz I again ;o) Here's one for you savy techies out there: So, I've got a primary domain which is live, optimized and running smooooth. And then I've got a couple of misspelled domains as well (17 to be exact). Will it have an effect if I 301 those misspelled domains? What's Best Practice for several domain aliases? Example.
Technical SEO | | nosuchagency
Primary domain: bryghusprojektet.dk
Alias domain 1: bryghusprojekt.dk (301 redirects to primary domain)
Alias domain 2: bryghus-projekt.dk (Hosting company infopage)
Alias domain 3: bryghus-projekter.dk (Not activated) Regards.1 -
Google Webmaster redirect vs 301 redirect
OK assuming a client's website has the right tracking script (hopefully analytics isn't effected by this issue), ... what happens if the htaccess file has a 301 redirect to the www-address, but within Google Webmaster Tools, the address chosen to crawl by Google is the non-www address? How will Google handle and which address takes precedence in this situation? _Cindy
Technical SEO | | CeCeBar0 -
Google , 301 redirects, and multiple domains pointing to the same content.
Google, 301 redirects, and multiple domains pointing to the same content. This is my first post here. I would like to begin by thanking anyone in advance for their help. It is much appreciated. Secondly, I'm posting in the wrong place or something please forgive me simply point me in the right direction I'm a quick learner. I think I'm battling a redirect problem but I want to be sure before I make changes. In order to accurately assess the situation a little background is necessary. I have had a site called tx-laws.com for about 15 years. It was a site that was used primarily by private resource and as such was never SEO'd. The site itself was in fact quite Seo unfriendly. despite a complete lack of marketing or SEO efforts, over time, SEO aside, this domain eventually made it to page one of Google Yahoo and Bing under the keywords Texas laws. About six months ago I decided to revamp the site and create a new resource aimed at a public market. A good deal of effort was made to re-work the SEO. The new site was developed at a different domain name: easylawlook up.com. Within a few months this domain name surpassed tx-laws in Google and was holding its place in position number eight out of 190 million results. Note that at this point no marketing has been done, that is to say there has been no social networking, no e-mail campaigns, no blogs, -- nothing but content. All was well until a few weeks ago I decided to upgrade our network and our servers. During this period there was some downtime unfortunately. When the upgrade was complete everything seemed fine until a week or so later when our primary domain easy law look up vanished off Google. At first I thought it was downtime but now I'm not so sure. The current configuration reroutes traffic from tx-laws to easylawlookup in IIS by pointing both domains to the same root directory. Everything else was handled through scripting. As far as I know this is how it was always set up. At present there is no 301 Redirect in place for tx-laws (as I'm sure there probably should be). Interestingly enough the back links to easylaw also went away. Even more telling however is that now when I visit link: easylawlookup.com there is only one link, and that link is to a domain which references tx-laws not easy law. So it would appear that I have confused Google with regards to my actual intentions. My question is this. Right now my rankings for tx-laws remain unchanged. The last thing I want to have happen is to see those disappear as well. If easy law has somehow been penalized and I redirect tx-laws to easy through a 301 will I screw up my rankings for this domain as well? Any comments or input on the situation are welcome. I just want to think it through before I start making more changes which might make things worse instead of better. Ultimately though, there is no reason that the old domain can't be redirected to the new domain at this point unless it would mean that I run the risk of losing my listings for tx-laws, ending up with nothing instead of transferring any link juice and traffic to easy law. With regards to the down time, it was substantial over a couple of weeks with many hours off-line. However this downtime would have affected both domains the only difference being that the one domain had been in existence for 15 years as opposed to six months for the other. So is my problem downtime, lack of proper 301 redirect, or something else? and if I implement a 301 at this point do I risk damaging the remaining domain which is operational? Thanks again for any help.
Technical SEO | | Steviebone0 -
A client will be translating their entire site into French in addition to English. For SEO purposes, should I host it on the same domain or create its own dedicated domain?
The current site is a long-standing site with good authority and a good number of links. Thanks....
Technical SEO | | JamesBSEO0 -
Is a 302 redirect the correct redirect from a root URL to a detail page?
Hi guys The widely followed SEO best practice is that 301 redirects should be used instead of 302 redirects when it is a permanent redirect that is required. Matt Cutts said last year that 302 redirects should "only" be used for temporary redirects. http://www.seomoz.org/blog/whiteboard-interview-googles-matt-cutts-on-redirects-trust-more For a site that I am looking at the SEO Moz Crawll Diagnostics tool lists as an issue that the URL / redirects to www.abc.com/Pages/default.aspx with a 302 redirect. On further searching I found that on a Google Support forum (http://www.google.com/support/forum/p/Webmasters/thread?tid=276539078ba67f48&hl=en) that a Google Employee had said "For what it's worth, a 302 redirect is the correct redirect from a root URL to a detail page (such as from "/" to "/sites/bursa/"). This is one of the few situations where a 302 redirect is preferred over a 301 redirect." Can anyone confirm if it is the case that "a 302 redirect is the correct redirect from a root URL to a detail page"? And if so why as I haven't found an explanation. If it is the correct best practice then should redirects of this nature be removed from displaying as issues in the SEO Moz Crawll Diagnostics tool Thanks for your help
Technical SEO | | CPU0