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
-
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 -
How to handle potentially thousands (50k+) of 301 redirects following a major site replacement
We are looking for the very best way of handling potentially thousands (50k+) of 301 redirects following
Intermediate & Advanced SEO | | GeezerG
a major site replacement and I mean total replacement. Things you should know
Existing domain has 17 years history with Google but rankings have suffered over the past year and yes we know why. (and the bitch is we paid a good sized SEO company for that ineffective and destructive work)
The URL structure of the new site is completely different and SEO friendly URL's rule. This means that there will be many thousands of historical URL's (mainly dynamic ones) that will attract 404 errors as they will not exist anymore. Most are product profile pages and the God Google has indexed them all. There are also many links to them out there.
The new site is fully SEO optimised and is passing all tests so far - however there is a way to go yet. So here are my thoughts on the possible ways of meeting our need,
1: Create 301 redirects for each an every page in the .htaccess file that would be one huge .htaccess file 50,000 lines plus - I am worried about effect on site speed.
2: Create 301 redirects for each and every unused folder, and wildcard the file names, this would be a single redirect for each file in each folder to a single redirect page
so the 404 issue is overcome but the user doesn't open the precise page they are after.
3: Write some code to create a hard copy 301 index.php file for each and every folder that is to be replaced.
4: Write code to create a hard copy 301 .php file for each and every page that is to be replaced.
5: We could just let the pages all die and list them with Google to advise of their death.
6: We could have the redirect managed by a database rather than .htaccess or single redirect files. Probably the most challenging thing will be to load the data in the first place, but I assume this could be done programatically - especially if the new URL can be inferred from the old. Many be I am missing another, simpler approach - please discuss0 -
Hacked website - Dealing with 301 redirects and a large .htaccess file
One of my client's websites was recently hacked and I've been dealing with the after effects of it. The website is now clean of malware and I already appealed to Google about the malware issue. The current issue I have is dealing with the 20, 000+ crawl errors which are garbage links that were created from the hacking. How does one go about dealing with all the 301 redirects I need to create for all the 404 crawl errors? I'm already noticing an increased load time on the website due to having a rather large .htaccess file with a couple thousand 301 redirects done already which I fear will result in my client's website performance and SEO performance taking a hit as well.
Intermediate & Advanced SEO | | FPK0 -
Website Redesign, 301 Redirects, and Link Juice
I want to change my client’s ecommerce site to Shopify. The only problem is that Shopify doesn’t let you customize domains. I plan to: keep each page’s content exactly the same keep the same domain name 301 redirect all of the pages to their new url The ONLY thing that will change is each page’s url. Again, each page will have the exact same content. The only source of traffic to this site is via Google organic search and sales depend on the traffic. There are about 10 pages that have excellent link juice, 20 pages that have medium link juice, and the rest is small link juice. Many of our links that have significant link juice are on message boards written by people that like our product. I plan to change these urls and 301 redirect them to their new urls. I’ve read tons of pages online about this topic. Some people that say it won’t effect link juice at all, some say it will might effect link juice temporarily, and others are uncertain. Most answers tend to be “You should be good. You might lose some traffic temporarily. You might want to switch some of your urls to the new structure to see how it affects it first.” Here’s my question: 1) Has anyone ever done changed a url structure for an existing website with link juice? What were your results and do you have a definitive answer on the topic? 2) How much link juice (if any) will be lost if I keep all of the exact content the same but only change each page’s url? 3) If link juice is temporarily lost and then regained, how long will it be temporarily lost? 1 week? 1 month? 6 months? Thanks.
Intermediate & Advanced SEO | | kirbyf0 -
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 -
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 -
301 Redirect from ASP.NET to PHP...Is it possible?
Hi all, I'm trying to migrate my current website over to wordpress however my current website is ASP.NET and obviously Wordpress uses PHP. Is it possible to perform a 301 redirect from a asp.net to a php? Or do you need to convert the asp.net language into php? Or something different? I welcome your thoughts? Regards, Thomas Rochford
Intermediate & Advanced SEO | | CoGri0 -
How to set up 301 redirect for URL with question mark
I have encountered some issue with 301 redirect and htaccess file. I need to redirect the following url: http://www.domain.com/?specifications=colours/page/3 to: http://www.domain.com/colours The 301 redirect command I wrote in htaccess file is as follow: Redirect 301 /?specifications=colours/page/3 http://www.domain.com/colours And it doesn't work at the moment. What is the correct way to set up 301 redirect here? Your help will be sincerely appreciated!
Intermediate & Advanced SEO | | robotseo0