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
-
Using a Reverse Proxy and 301 redirect to appear Sub Domain as Sub Directory - what are the SEO Risks?
We’re in process to move WordPress blog URLs from subdomains to sub-directory. We aren’t moving blog physically, but using reverse proxy and 301 redirection to do this. Blog subdomain URL is https://blog.example.com/ and destination sub-directory URL is https://www.example.com/blog/ Our main website is e-commerce marketplace which is YMYL site. This is on Windows server. Due to technical reasons, we can’t physically move our WordPress blog to the main website. Following is our Technical Setup Setup a reverse proxy at https://www.example.com/blog/ pointing to https://blog.example.com/ Use a 301 redirection from https://blog.example.com/ to https://www.example.com/blog/ with an exception if a traffic is coming from main WWW domain then it won’t redirect. Thus, we can eliminate infinite loop. Change all absolute URLs to relative URLs on blog Change the sitemap URL from https://blog.example.com/sitemap.xml to https://www.example.com/blog/sitemap.xml and update all URLs mentioned within the sitemap. SEO Risk Evaluation We have individual GA Tracking ID and individual Google Search Console Properties for main website and blog. We will not merge them. Keep them separate as they are. Keeping this in mind, I am evaluating SEO Risks factors Right now when we receive traffic from main website to blog (or vice versa) then it is considered as referral traffic and new cookies are set for Google Analytics. What’s going to happen when its on the same domain? Which type of settings change should I do in Blog’s Google Search Console? (A). Do I need to request “Change of Address” in the Blog’s search console property? (B). Should I re-submit the sitemap? Do I need to re-submit the blog sitemap from the https://www.example.com/ Google Search Console Property? Main website is e-commerce marketplace which is YMYL website, and blog is all about content. So does that impact SEO? Will this dilute SEO link juice or impact on the main website ranking because following are the key SEO Metrices. (A). Main website’s Avg Session Duration is about 10 minutes and bounce rate is around 30% (B). Blog’s Avg Session Duration is 33 seconds and bounce rate is over 92%
Intermediate & Advanced SEO | | joshibhargav_200 -
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 -
When is Too Many Categories Too Many on a eCommerce site?
We all know that more and more people are increasing the amount of different categories that eCommerce sites have. Say for example, you have over 3,000 different products, all categories contain unique text at the top of each, all of the categories link to each other (so loads on internal linking) and no two categories contain the exact same products. My question is this, is there ever a stage that you could create too many categories? Alternatively, do you think you should just keep creating categories based on what our customers search for?
Intermediate & Advanced SEO | | the-gate-films1 -
Is a 301 Redirect and a Canonical Tag on Uppercase to Lowercase Pages Correct?
We have a medium size site that lost more than 50% of its traffic in July 2013 just before the Panda rollout. After working with a SEO agency, we were advised to clean up various items, one of them being that the 10k+ urls were all mixed case (i.e. www.example.com/Blue-Widget). A 301 redirect was set up thereafter forcing all these urls to go to a lowercase version (i.e. www.example.com/blue-widget). In addition, there was a canonical tag placed on all of these pages in case any parameters or other characters were incorporated into a url. I thought this was a good set up, but when running a SEO audit through a third party tool, it shows me the massive amount of 301 redirects. And, now I wonder if there should only be a canonical without the redirect or if its okay to have tens of thousands 301 redirects on the site. We have not recovered yet from the traffic loss yet and we are wondering if its really more of a technical problem than a Google penalty. Guidance and advise from those experienced in the industry is appreciated.
Intermediate & Advanced SEO | | ABK7170 -
301 redirect subdirectory to new domain
I'm planning on using 301 redirects to spin out a subdirectory of my current website to be its own separate domain. For instance, I currently have a website www.website.com and my writers write tech news at www.website.com/news. Now I want to 301 redirect www.website.com/news to www.technews.com. Will this have any negative impact on SEO? What are some steps that I can take to minimize these impacts?
Intermediate & Advanced SEO | | Chris_Bishop1 -
301 redirection pointing to noindexed pages
I have rather an unusual situation where a recently launched affiliate site does not have any unique content as its all syndicated content. For that reason we are currently using the noindex,nofollow meta tags to keep the pages out of the search engines index until we create unique content for the pages. The problem is that due to a very tight timeframe with rebranding, we are looking at 301 redirecting (on a page to page basis) another high authority legacy domain to this new site before we have had a chance to add unique content to it and remove the noindex,nofollow tags. I would assume that any link authority normally passed through the 301 would be lost in this scenario but Im uncertain of what the broader impact might be. Has anyone dealt with a similar scenario? I know this scenario is not ideal and I would rather wait until the unique content is up and noindex tags are removed before launching the 301 redirect of the legacy domain but there are a number of competing priorities at play outside of SEO.
Intermediate & Advanced SEO | | LosNomads0 -
301 Redirection and apostrophes in URLs
Hi I am experiencing trouble getting any redirects with apostrophes in the URLs to 301 redirect in order to eliminate 404 errors. I have tried replacing the instance of the apostrophe in the source URL field to %27 and variations of this but to no avail. The site is a wordpress site (the old URLS are legacies from the old Business Catalyst site) and I am using the redirection plug in. I have gone into some detail with a helpful soul here http://wordpress.org/support/topic/how-to-deal-with-apostrophes-in-source-url but unfortunately to no result. If anyone has any idea how to solve this puzzle I would be grateful for the help. Example: http://www.tesselaars.com/blog/Inside_Flowers/post/Online_Marketing_for_Florists_Part_1%E2%80%93_A_Website_You_Won%27t_Regret/
Intermediate & Advanced SEO | | Seamoose0