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
-
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version?
We are redirecting http and non www versions of our website. Should all versions http (non www version and www version) and https (non www version) should just have 1 redirect to the https www version? Thant way all forms of the website are pointing to one version?
Intermediate & Advanced SEO | | Caffeine_Marketing0 -
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 -
Is it a problem to use a 301 redirect to a 404 error page, instead of serving directly a 404 page?
We are building URLs dynamically with apache rewrite.
Intermediate & Advanced SEO | | lcourse
When we detect that an URL is matching some valid patterns, we serve a script which then may detect that the combination of parameters in the URL does not exist. If this happens we produce a 301 redirect to another URL which serves a 404 error page, So my doubt is the following: Do I have to worry about not serving directly an 404, but redirecting (301) to a 404 page? Will this lead to the erroneous original URL staying longer in the google index than if I would serve directly a 404? Some context. It is a site with about 200.000 web pages and we have currently 90.000 404 errors reported in webmaster tools (even though only 600 detected last month).0 -
Multiple 301 redirects for a HTTPS URL. Good or bad?
I'm working on an ecommerce website that has a few snags and issues with it's coding. They're using https, and when you access the website through domain.com, theres a 301 redirect to http://www.domain.com and then this, in turn, redirected to https://www.domain.com. Would this have a deterimental effect or is that considered the best way to do it. Have the website redirect to http and then all http access is redirected to the https URL? Thanks
Intermediate & Advanced SEO | | jasondexter0 -
Remove URLs that 301 Redirect from Google's Index
I'm working with a client who has 301 redirected thousands of URLs from their primary subdomain to a new subdomain (these are unimportant pages with regards to link equity). These URLs are still appearing in Google's results under the primary domain, rather than the new subdomain. This is problematic because it's creating an artificial index bloat issue. These URLs make up over 90% of the URLs indexed. My experience has been that URLs that have been 301 redirected are removed from the index over time and replaced by the new destination URL. But it has been several months, close to a year even, and they're still in the index. Any recommendations on how to speed up the process of removing the 301 redirected URLs from Google's index? Will Google, or any search engine for that matter, process a noindex meta tag if the URL's been redirected?
Intermediate & Advanced SEO | | trung.ngo0 -
302 redirects in the sitemap?
My website uses a prefix at the end to instruct the back-end about visitor details. The setup is similar to this site - http://sanfrancisco.giants.mlb.com/index.jsp?c_id=sf with a 302 redirect from the normal link to the one with additional info and a canonical tag on the actual URL without the extra info ((the normal one here being http://sanfrancisco.giants.mlb.com,) However, when I used www.xml-sitemaps.com to create a sitemap they did so using the URLs with the extra info on the links... what should I do to create a sitemap using the normal URLs (which are the ones I want to be promoting)
Intermediate & Advanced SEO | | theLotter0 -
301 doesn't redirect a page that ends in %20, and others being appended with ?q=
I have a product page that ends /product-name**%20** that I'm trying to redirect in this way: Redirect 301 /products/product-name%20 http://www.site.com/products/product-name And it doesn't redirect at all. The others, those with %20, are being redirected to a url hybrid of old and new: http://www.site.com/products/product-name**?q=old-url** I'm using Drupal CMS, and it may be creating rules that counter my entries.
Intermediate & Advanced SEO | | Brocberry0 -
How to stop Google crawling after 301 redirect?
I have removed all pages from my old website and set 301 redirect to new website. But, I have verified old website with Google webmaster tools' HTML verification file which enable me to track all data and existence of pages in Google search for my old website. I was assumed that, Google will stop crawling and DE-indexed all pages after 301 redirect. Because, I have set 301 redirect before 3 months. Now, I'm able to see Google bot activity on my website with help of Google webmaster tools. You can find out attachment to know more about it. How can it possible & How Google can crawl removed pages? You can see following image to know more about it. First & Second
Intermediate & Advanced SEO | | CommercePundit0