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.
Too many 301 redirects?
-
Hey,
My company currently has one chief website with about 500-600 other domains that all feature the same material as the chief website. These domains have been around for about 5 years and have actually picked up some link traffic.
I have all of these identical web-pages utilizing rel=canonical but I was wondering if I would be better served, from SEO purposes, to 301 redirect all of these sites to their respective pages on our chief website? If I add 500 301 redirects, will the major search engines consider this to be black-hat link-building even though the sites are related and technically already feature the same content?
For an example, the chief website is www.1099pro.com and I would 301 redirect the below sites to the chief site:
-
Michael I don't think you will get anymore benefit from a 301 than you're getting from the cross-domain rel canonical tags that are already in place.
However, I think the fact that you already have these cross-domain rel canonical tags i place, and that the content is identical, will make it much less likely that 301 redirecting those domains would be seen as any type of spam.
If it were me, just so all of my users were on the same domain - and to keep the problem from getting worse over time - I would go ahead and 301 redirect the other domains, but on a page-to-page basis. In other words, each page would link directly to the page it is currently referencing as the rel canonical. This would be much better than redirecting them all to a single landing page, and would send signal that is consistent with the current one you are sending via the cross domain rel canonical.
You might try this one domain at a time. Let the dust settle on that domain and, if all goes well, move on to the next. It may take a year to complete the project, but it might be the safest way to go.
Alternatively, you could just continue to leave the other sites up with the cross domain rel canonical tag - but the problem is likely to just worsen over time as more people link to the other domains, and they develop their own sources of traffic via direct links, social, bookmarks, etc... outside of the SERPs.
-
PS you have a decent thing going with your links already and you are not in a bad spot for page rank.
| Page Authority (PA) | 53 | Domain Authority (DA) | -- | 46 |
| MozRank (mR) | 5.94 | Domain MozRank (DmR) | 4.81 | 4.72 |
| MozTrust (mT) | 5.83 | Domain MozTrust (DmT) | 4.51 | 4.30 |
| Total Links | 1,635 | Total Links | 15,333 | 52,916 |
| External Followed Links | 1,589 | External Followed Links | 10,939 | 12,132 |
| Internal Followed Links | 39 | Linking Root Domains | 566 | 701 |
| Linking Root Domains | 399|
I would not jeopardize you have that's my $.02.
-
301 redirecting is not bad at all in itself.
It is simply a method of redirecting links. However because of the quantity of exact match sites I believe you can only put yourself in danger Google is getting and more aggressive every day I would rather sleep soundly if I were you or myself obviously. And not redirect possibly spamish websites to my main site where I do business.
If this was not regarding 500 duplicate sites I would say go for it
unfortunately I believe that you will open yourself up for a possible penalty from Google.
The immense amount of duplicate or identical content that I don't know if you use Google Webmaster tools am assuming that you do but do have it set up for all 500 websites?
That will tell you if you have a penalty.
My thinking on this is you created a bunch of identical websites 500 of them. Whenever you make large changes to a website Google reevaluates it looks at it.
In my opinion by 301 redirecting 500 sites page 2 page or even to homepage you're just asking for a possible Extremely bad penalty or you might get away with it I don't know but if it were me I would not do it.
The real question is what is the chief site worth?
would you be okay with it being penalized because you 301 redirected all of the sites?
if the answer is this is a valuable website to me I would not risk it.
The problem is you did something that is very far into the black hat arena I'm not judging however you want to show Google you're not going to continue to try to take advantage of any part of the search engine in order to gain rank when the parts that your talking about our exact match duplicate content that you created.
I honestly would kill the content on the sites than 302 redirect them if you want to have the traffic from the links.
What you said about a 301 is pretty much where the money however you're going to open yourself up to a possible penalty or even removal from Google's index which is what happens with most penalties.
It's up to you however I would not do it.
Best of luck to you,
Thomas
-
301 redirecting entire identical sites to different pages sounds extremely dodgy, just to the homepage was bad enough.
-
So if 301 redirecting all of them is seen as negative, what is the best way to consolidate all of these sites? I thought the purpose of a 301 redirect was to permanently transfer traffic from one site to another - which would mean that a 301 redirect would be the ideal method for consolidating multiple versions of an identical site.
In essence, is there a way to gain at least some advantage from the links that these sites of garnered over time?
-
I agree with Alex on a lot of it
however 500 of the same website with identical content is extremely black hat
it would depend on how much traffic is coming from these domains? Which one of them is performing the best? There must surely be a standout hopefully if it's not a lot of traffic I would delete the content on the other domains and pray that Google is not going to penalize you. By 301 redirecting any of those sites to your current chief site used and only to lose quite a bit from Google this is something that will happen if you are using the same hosting providers or not they will consider this less than good
-
Hey,
I would be redirecting each entire site to a specific page on my chief website. Admittedly, this means that there is some precision lost because each site is a copy of the chief site but all the affiliated pages on a copy link to only one landing page on the chief site. For instance:
- www.1099softwarepro.com and all affiliated pages would redirect to www.1099pro.com/software.asp
- www.W2Professionals.com and all affiliated pages would redirect to www.1099pro.com/prodw2pro.asp
-
In 2011 Matt Cutts said there isn't a limit. 500-600 sounds A LOT. If I was in this situation I'd just 301 the domains that have the most traffic and best links.
Are you redirecting each page on the other websites to the matching page on the chief website?
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
-
Do bulk 301 redirects hurt seo value?
We are working with a content based startup that needs to 301 redirect a lot of its pages to other websites. Will give you an example to help you understand. If we assume this is the startups domain and URL structure www.ourcompany.com/brand1/article What they want to do is do a 301 redirect of www.ourcompany.com/brand1/ to www.brand1.com I have never seen 301 as a problem to SEO or link juice. But in this case where all the major URLs are getting redirected to other sites i was wondering if it would have a negative effect. Right now they have just 20-30 brands but they are planning to hit a couple of hundreds this year.
Intermediate & Advanced SEO | | aaronfernandez0 -
Is there any benefit to changing 303 redirects to 301?
A year ago I moved my marketplace website from http to https. I implemented some design changes at the same time, and saw a huge drop in traffic that we have not recovered from. I've been searching for reasons for the organic traffic decline and have noticed that the redirects from http to https URLs are 303 redirects. There's little information available about 303 redirects but most articles say they don't pass link juice. Is it worth changing them to 301 redirects now? Are there risks in making such a change a year later, and is it likely to have any benefits for rankings?
Intermediate & Advanced SEO | | MAdeit0 -
301 Redirect - Rank Recovery Examples?
Hi All, I recently did a 301 redirect. Page to Page and the notified google via its console. Its been 6 days since. The home page and one other high traffic page swopped out with the new domain on google search index with 3-4 drops in ranking for each. The rest of the sites pages have been indexed but still reflect the old domain when searched. Recently today my home page dropped even further to the second page of google index for the specific keyword. Can you share similar experiences and how long it took you to recover rank fully? and how long for all pages to swop out on google search's index? Regards Mike
Intermediate & Advanced SEO | | MikeBlue10 -
302 > 302 > 301 Redirect Chain Issue & Advice
Hi everyone, I recently relaunched our website and everything went well. However, while checking site health, I found a new redirect chain issue (302 > 302 > 301 > 200) when the user requests the HTTP and non-www version of our URL. Here's what's happening: • 302 #1 -- http://domain.com/example/ 302 redirects to http://domain.com/PnVKV/example/ (the 5 characters in the appended "subfolder" are dynamic and change each time)
Intermediate & Advanced SEO | | Andrew_In_Search_of_Answers
• 302 #2 -- http://domain.com/PnVKV/example/ 302 redirects BACK to http://domain.com/example/
• 301 #1 -- http://domain.com/example/ 301 redirects to https://www.domain.com/example/ (as it should have done originally)
• 200 -- https://www.domain.com/example/ resolves properly We're hosted on AWS, and one of my cloud architects investigated and reported GoDaddy was causing the two 302s. That's backed up online by posts like https://stackoverflow.com/questions/46307518/random-5-alpha-character-path-appended-to-requests and https://www.godaddy.com/community/Managing-Domains/My-domain-name-not-resolving-correctly-6-random-characters-are/td-p/60782. I reached out to GoDaddy today, expecting them to say it wasn't a problem on their end, but they actually confirmed this was a known bug (as of September 2017) but there is no timeline for a fix. I asked the first rep I spoke with on the phone to send a summary, and here's what he provided in his own words: From the information gathered on my end and I was able to get from our advanced tech support team, the redirect issue is in a bug report and many examples have been logged with the help of customers, but no log will be made in this case due to the destination URL being met. Most issues being logged are site not resolving properly or resolving errors. I realize the redirect can cause SEO issues with the additional redirects occurring. Also no ETA has been logged for the issue being reported. I do feel for you since I now understand more the SEO issues it can cause. I myself will keep an eye out for the bug report and see if any progress is being made any info outside of this I will email you directly. Thanks. Issue being Experienced: Domains that are set to Go Daddy forwarding IPs may sometimes resolve to a url that has extra characters appended to the end of them. Example: domain1.com forwards to http://www.domain2.com/TLYEZ. However it should just forward to http://www.domain2.com. I think this answers what some Moz users may have been experiencing sporadically, especially this previous thread: https://moz.com/community/q/forwarded-vanity-domains-suddenly-resolving-to-404-with-appended-url-s-ending-in-random-5-characters. My question: Given everything stated above and what we know about the impact of redirect chains on SEO, how severe should I rate this? I told my Director that I would recommend we move away from GoDaddy (something I don't want to do, but feel we _**have **_to do), but she viewed it as just another technical SEO issue and one that didn't necessarily need to be prioritized over others related to the relaunch. How would you respond in my shoes? On a scale of 1 to 10 (10 being the biggest), how big of a technical SEO is this? Would you make it a priority? At the very least, I thought the Moz community would benefit from the GoDaddy confirmation of this issue and knowing about the lack of an ETA on a fix. Thanks!0 -
301 redirect hops from non-https and www
It's best practice to minimize the amount of 301 redirect hops. Ideally only one redirect hop. It's also best practice to 301 redirect (or at least canonical) your non-https and/or your non-www (or www) to the canonical protocol/subdomain. The simplest (and possibly the most common) way to implement canonical protocol/subdomain redirects is through a load balancer or before your app processes the request. Both of which will just blanket 301 to the canonical domain/protocol regardless if the path exists or not In which case, you could have: Two hops. i.e. hop #1 http://example.com/foo to https://example.com/foo, hop #2 https://example.com/foo to https://example.com/bar 301 to a 404. Let's say https://example.com/dog never existed, but somebody for whatever reason linked to it (maybe a typo). If I request https://www.example.com/dog, the load balancer would 301 to a 404 page. Either scenario above should be fairly rare. However, you can't control how people link to you. Should I care about either above scenario? I could have my app attempt to check if the page exists before forwarding, but that code could be complicated.
Intermediate & Advanced SEO | | dsbud0 -
Images Returning 404 Error Codes. 301 Redirects?
We're working with a site that has gone through a lot of changes over the years - ownership, complete site redesigns, different platforms, etc. - and we are finding that there are both a lot of pages and individual images that are returning 404 error codes in the Moz crawls. We're doing 301 redirects for the pages, but what would the best course of action be for the images? The images obviously don't exist on the site anymore and are therefore returning the 404 error codes. Should we do a 301 redirect to another similar image that is on the site now or redirect the images to an actual page? Or is there another solution that I'm not considering (besides doing nothing)? We'll go through the site to make sure that there aren't any pages within the site that are still linking to those images, which is probably where the 404 errors are coming from. Based on feedback below it sounds like once we do that, leaving them alone is a good option.
Intermediate & Advanced SEO | | garrettkite0 -
When should you redirect a domain completely?
We moved a website over to a new domain name. We used 301 redirects to redirect all the pages individually (around 150 redirects). So my question is, when should we just kill the old site completely and just redirect (forward/point) the old domain over to the new one?
Intermediate & Advanced SEO | | co.mc0 -
301 Redirect With A Message And Delay
Hello, I'd like to sell a site I own. I'd like the site to be redirected to the buyers site with a 301 redirect. But I'd like the viewer to be informed that the site was purchased by this company and they will be redirect in 5 seconds.I'd like for the redirect to be a complete 301 and pass as much linklove as possible. Are you familiar with how to do this? Thanks, Tyler
Intermediate & Advanced SEO | | tylerfraser0