Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Redirect ruined domain to new domain without passing link juice
-
A new client has a domain which has been hammered by bad links, updates etc and it's basically on its arse because of previous SEO guys.
They have various domains for their business (brand.com, brand.co.uk) and want to use a fresh domain and take it from there. Their current domain is brand.com (the ruined one). They're not bothered about the rankings for brand.com but they want to redirect brand.com to brand.co.uk so that previous clients can find them easily.
Would a 302 redirect work for this? I don't want to set up a 301 redirect as I don't want any of the crappy links pointing across.
Thanks!
-
I feel that there should be some form of redirect that can be conducted without passing on link juice value.
From my perspective, it's not gaming the system or trying to game Google. My client doesn't want any link juice passing on, but wants to keep the old domain for people accessing the domain directly.
It's a shame really. Google holds a massive grudge, even though these guys trusted a big name in the SEO industry.
-
Sorry it's taken a bucket load of time to get back to you!
Ideally, they're looking at some form redirection to avoid any form of user interaction.
A meta-refresh might be the best route to go down, I'm going to noindex/nofollow the website and put forward a meta-refresh solution to them.
I don't think a second or two in lag would be a problem, as users hitting the .com version of the website will slowly phase out anyway.
Thanks buddy!
-
I don't think I ever realized that forwarding also can return a 301. That's really good to know. Thanks.
-
I'd just warn that most domain forwarding ends up returning a 301 response code anyway, and some return a 302. You could always test it out to see what happens. I checked (non-masked) domain forwarding on two hosts and found 301s in the header in both cases. I believe this is fairly common.
One controversial solution might be a JavaScript redirect that search engines can't understand instead. It's obviously cloaking if the content is different, but maybe not if the content is similar. See https://support.google.com/webmasters/answer/2721217?hl=en&ref_topic=2371375
Unfortunately, there's not a redirect method that would prevent both versions of the site from being indexed. Even with a penalty, the old site could out-rank the new one for branded and long-tail traffic.
Perhaps the best/safest option is to simply noindex/nofollow the pages, then show a warning with a link to the new version of the page. Yes, it requires a new click from users, but it's simple enough that there's little to worry about.
-
I'm not sure that any redirect is guaranteed that Google won't pass on the links to the .uk domain. The two options I could think of which would probably be the least likely for Google to pass on the links would be,
1. You could setup a meta-refresh redirect on the .com. Make sure it's a few seconds and not instant.
2. Redirect everything from the .com site to a single landing page on the .com site. Put a message on that landing page that tells visitors the site has moved and provide a link to the new site.
Neither of these solutions are great from a user experience standpoint, but their the least likely for Google to pass on all the bad links from the .com site.
-
Why don't you try domain forwarding? That may be your only option as there is growing evidence that Google passes links from 302 redirects as well. You can find the domain forwarding option in the control panel where the domain name is hosted. Instead of doing a redirect, the change will take place with the DNS.
Here's some info: http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Make sure you choose forwarding without masking.
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
-
Does redirecting from a "bad" domain "infect" the new domain?
Hi all, So a complicated question that requires a little background. I bought unseenjapan.com to serve as a legitimate news site about a year ago. Social media and content growth has been good. Unfortunately, one thing I didn't realize when I bought this domain was that it used to be a porn site. I've managed to muck out some of the damage already - primarily, I got major vendors like Macafee and OpenDNS to remove the "porn" categorization, which has unblocked the site at most schools & locations w/ public wifi. The sticky bit, however, is Google. Google has the domain filtered under SafeSearch, which means we're losing - and will continue to lose - a ton of organic traffic. I'm trying to figure out how to deal with this, and appeal the decision. Unfortunately, Google's Reconsideration Request form currently doesn't work unless your site has an existing manual action against it (mine does not). I've also heard such requests, even if I did figure out how to make them, often just get ignored for months on end. Now, I have a back up plan. I've registered unseen-japan.com, and I could just move my domain over to the new domain if I can't get this issue resolved. It would allow me to be on a domain with a clean history while not having to change my brand. But if I do that, and I set up 301 redirects from the former domain, will it simply cause the new domain to be perceived as an "adult" domain by Google? I.e., will the former URL's bad reputation carry over to the new one? I haven't made a decision one way or the other yet, so any insights are appreciated.
Intermediate & Advanced SEO | Apr 3, 2021, 3:22 AM | gaiaslastlaugh0 -
Cleaning up a Spammy Domain VS Starting Fresh with a New Domain
Hi- Can you give me your opinion please... if you look at murrayroofing.com and see the high SPAM score- and the fact that our domain has been put on some spammy sites over the years- Is it better and faster to place higher in google SERP if we create a fresh new domain? My theory is we will spin our wheels trying to get unlisted from alot of those spammy linking sites. And that it would be faster to see results using a fresh new domain rather than trying to clean up the current spammy doamin. Thanks in advance - You guys have been awesome!!
Intermediate & Advanced SEO | May 16, 2019, 3:00 PM | murraycustomhomescom0 -
301 Redirect from query string to new static page
If i want to create a redirect from a page where the slug ends like this "/?i=4839&mid=1000&id=41537" to a static, more SEO friendly slug like "/contact-us/", will a standard 301 redirect suffice? Thanks, Nails
Intermediate & Advanced SEO | Aug 13, 2018, 2:32 PM | matt.nails0 -
Move domain to new domain, for how much time should I keep forwarding?
I'm not sure but my website looks like is not getting it's juice as supposed to be. As we already know, google preferred https sites and this is what happened to mine, it was been crawling as https but when the time came to move my domain to new domain, I used 301 or domain forwarding service, unfortunately they didn't have a way to forward from https to new https, they only had regular http to https, when users clicked to my old domain from google search my site was returned to "site does not exist", I used hreflang at least that google would detect my new domain been forwarding and yes it worked but now I'm wondering, for how much time should I keep the forwarding the old domain to the new one, my site looks like is not going up, I have changed all the external links, any help would be appreciated. Thanks!
Intermediate & Advanced SEO | Mar 13, 2017, 4:00 PM | Fulanito1 -
Getting SEO Juice back after Redirect
Hi, On my website, many product pages were redirected over time to its product category, due to the product being unavailable. I understand with a 301 redirect, the final URL would have lost about 15% of the link juice. However - if after some time (e.g. 2 months, or 1 year) I remove the redirection - is the original page going to have any SEO juice, or did it already lose all of it? Thanks,
Intermediate & Advanced SEO | Sep 30, 2016, 5:01 PM | viatrading10 -
NEw domain extensions, are they worth it seo wise?
Hello I am curious if all of these new extensions for domains are worth it? So say you are a home builder and you bought homebuilder.construction - where as construction is a new extension, does this help seo? Or is it all just a big sales gimmick? Thank you for your thoughts
Intermediate & Advanced SEO | Apr 27, 2014, 10:15 PM | Berner1 -
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 | Mar 16, 2014, 3:18 PM | imran20780 -
Subdomain Blog Sitemap link - Add it to regular domain?
Example of setup:
Intermediate & Advanced SEO | Jun 14, 2013, 3:21 PM | EEE3
www.fancydomain.com
blog.fancydomain.com Because of certain limitations, I'm told we can't put our blogs at the subdirectory level, so we are hosting our blogs at the subdomain level (blog.fancydomain.com). I've been asked to incorporate the blog's sitemap link on the regular domain, or even in the regular domain's sitemap. 1. Putting the a link to blog.fancydomain.com/sitemap_index.xml in the www.fancydomain.com/sitemap.xml -- isn't this against sitemap.org protocol? 2. Is there even a reason to do this? We do have a link to the blog's home page from the www.fancydomain.com navigation, and the blog is set up with its sitemap and link to the sitemap in the footer. 3. What about just including a text link "Blog Sitemap" (linking to blog.fancydomain.com/sitemap_index.html) in the footer of the www.fancydomain.com (adjacent to the text link "Sitemap" which already exists for the www.fancydomain.com's sitemap. Just trying to make sense of this, and figure out why or if it should be done. Thanks!0