Multiple 301 redirects considered a redirection chain?
-
I need to redirect a ton of duplicate content, so I want to try
redirect 301 /store/index.php /store
redirect 301 /store/product-old /store/product-new
redirect 301 /store/product-old1 /store/product-new1
redirect 301 /store/product-old2 /store/product-new2
redirect 301 /store/product-old3 /store/product-new3
redirect 301 /store/product-old4/file.html /store/product-old4/new4/file.html
and then a whole bunch of old dead links to homepage.
So we've had /index.php redirected to / on other parts of the site for awhile, and for the most part /store is a friendly URL, but then we have tons of dup content and work arounds that preceded my job here. I'm wondering if those redirects above would be considered a redirection chain? Since the all the redirects below the /index.php -> /store count on that one redirect.
Thanks for any insight you may be able to give!
-
301 redirecting an old, no longer existing page to the homepage or any other page (I'd suggest using the closest matching existing page) is certainly not a violation of google's guidelines.
-
As far as 'header redirect' are you talking about a meta refresh redirect rather than a 301 htaccess redirect? I thought meta refresh redirects were not necessarily a good thing to do in the eyes of search engines?
Also, isn't redirecting a URL of a page that no longer exists to the home page actually a violation of Google's guidelines?
I'm currently doing a project to resolve many 404s being reported in Google Webmaster account.
Many of them are simply malformed URLs (live URLs with a period at the end or a comma or an equal sign, etc.) from the referrer's side - yet some carry a vaulable backlink authority, so they should be 301'd, in my opinion to the intended URL, when that is obvious.
However, if there is no longer a close match page - say for an old but valued backlink - to ideally redirect to, is it OK to - in attempt to retain the backlink value - redirect what are really 404 pages to the homepage or a top landing page? If so, is there a limit to the number of redirects to resolve a 404?
Thanks for any clarification of the issue raised above.
-
Ask if you can do header code injection where you can dump code blocks in the header.
-
Yeah I might have to seek help on the magento boards.
-
WP has to have a 404 handler someplace in their admin section. At least the dead pages you can redirect, but I do not know if WP will 301 those.
Then yes, you have to use your .htaccess file to shift those pages. What a mess! Write them all down and carefully map them out. I would still test the page to see if it has any inbound links, if not, I might let the 404 handler handle that link to save editing.
I would also as WP or Magento or their message boards if any of them have this same problem and see if there are any plug-in fixes.
-
There are both indexed and internally linked urls that need to be redirected properly. Using two CMS's WP and Magento and I'm not too much of a php wiz so I really am not following. besides the product pages still being linked there are like 1000 more 404 pages that need to be redirected to the homepage. Would mod rewrite be better here?
And Barry, yes I guess so, just found out about it, trying to understnad wth is goin on here. Looks like mage redirects a couple times on its own as well? Who knows, it's puttin me to sleep lol. Hopefully I can find out more tomorrow. Thanks for the answers guys +1
-
Are you using Magento's funny built in redirect tool? I've never really understood how that worked
-
Wow, this is not fun
Yes, you can get down the chain too many times and your browser just pukes. And likely Google will give up.
- Test the OLD page(2) to see if it has any inbound links or page authority. If not, then a redirect is not necessary. Yes, the page still might be indexed, but I would do a header redirect with a 301 instead of using the .htaccess file. It is on the fly and much cleaner.
Depending on how your site is coded, you can test the page in PHP.
- Find incoming URL
- Test against database
- Send to new location
Simply take the incoming URL and pull the location in the _HEADER. Then look at your database that you set up with all these redirects. Then redirect the user to the new page and 301 the redirect in the header.
All the work you do is then in the database. Look at Google Webmaster for 404 pages and adjust the database. I would also then state that if I found no URL within the database (good or old) then I would redirect to the home page and 301 that. This way you do not lose any link juice and keep your 301 chain down to one dynamic hop.
I hope that helps
-
No trouble I'm quick with the mouse. That's why I like doin this stuff around 4am haha. Thanks anyway Barry.
You might be onto something, it's magento which I have limited to no knowledge of how it redirects, I'm sure that's the deal I'll look into it but after I need sleep soooo tired
-
I might bow out gracefully before I get you in any more trouble But I'll see what I can replicate and test What would be the raw URL of the electronics pages?
Is it actually rewriting from something like /store/index.php?id=electronics or is it /store/electronics.php (or even /store/electronics/index.php)? Or are you on a CMS that make it hard to tell?
-
redirect 301 /store/index.php /store
redirect 301 /store/electronics1 /store/electronics
that's pretty much it
-
Talk me through it again then, please.
You're trying to get to /store/product-new1 and you're getting a 310?
Did I get the redirect thing mixed up and actually there's another redirect because the real URL would be /store/product-new1/index.php?
-
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
-
Yeah there's certain cases, sometimes all, where /old will go through the first /index.php redirect to be able to get to /new
Yeah I guess you have a point, but for some reason it feels wrong. Google hasn't crawled this site for almost a month lol. So when it finally does, everything's gonna be so different it might just be like AHHH.
Thanks for the help.
-
If I understand correctly I'm going to say no (with a low degree of certainty :D).
So /store/product-old1 you are assuming already goes through /store/index.php?id=product-old1 (or similar) to produce that first url?
So to get to /store/product-new1 from a link to /store/product-old1 you're wondering how many steps your .htaccess puts it through?
I'll have to let somebody with better .htaccess skills than mine confirm, but I think it's all resolved as one, in sequence, if it's on the same server (and set up correctly). I'm maybe talking nonsense though.
However if it was a chain then, for example, somebody going to my WordPress site using mysite.com/page1 would end up at www.mysite.com/redirected-page1/ and after hitting about 4 redirects (www, permalinks, redirect and trailing slash) and I've not seen anything to suggest that it's a problem.
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
-
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 redirects broken - problems - please help!
Hi, I have a bit of an issue... Around a year ago we launched a new company. This company was launched out of a trading style of another company owned by our parent group (the trading style no longer exists). We used a lot of the content from the old trading style website, carefully mapping page-to-page 301 redirects, using the change of address tool in webmaster tools and generally did a good job of it. The reason I know we did a good job is that although we lost some traffic in the month we rebranded, we didn't lose rankings. We have since gained traffic exponentially and have managed to increase our organic traffic by over 200% over the last year. All well and good. However, a mistake has recently occurred whereby the old trading style website domain was deleted from the server for a period of around 2-3 weeks. It has since been reinstated. Since then, although we haven't lost rankings for the keywords we track I can see in webmaster tools that a number of our pages have been deindexed (around 100+). It has been suggested that we put the old homepage back up, and include a link to the XML sitemap to get Google to recrawl the old URLs and reinstate our 301 redirects. I'm OK with this (up to a point - personally I don't think it's an elegant solution) however I always thought you didn't need a link to the xml sitemap from the website and that the crawlers should just find it? Our current plan is not to put the homepage up exactly as it was (I don't believe this would make good business sense given that the company no longer exists), but to make it live with an explanation that the website has moved to a different domain with a big old button pointing to the new site. I'm wondering if we also need a button to the xml sitemap or not? I know I can put a sitemap link in the robots file, but I wonder if that would be enough for Google to find it? Any insights would be greatly appreciated. Thank you, Amelia
Intermediate & Advanced SEO | | CommT0 -
For URLs that require login, should our redirect be 301 or 302?
We have a login required section of our website that is being crawled and reporting as potential issues in Webmaster Tools. I'm not sure what the best solution to this is - is it to make URLs requiring a login noindex/nocrawl? Right now, we have them 302 redirecting to the login page, since it's a temporary redirect, it seems like it isn't the right solution. Is a 301 better?
Intermediate & Advanced SEO | | alecfwilson0 -
Removing 301 redirect from 2.5 yr old domain
Hello, Need Advise. We are in Automobiles We have an Automotive site - build 3 yrs back - which is our main site (Site A) We built a separate niche site on Used cars 2.5 yrs back (Site B - url http://www.usedcarindelhi.com) - did seo - promote it for a year and later on in feb 2013 - did 301 domain redirection to Site A Now - we thinking to rebuild Site Site B again and remove redirection Will there be any harm on Site A, as we have now removed the redirection or shall we pass on link from home page of Site B to Site A i.e say Powered by Site A (on Top) or at all no direct linking is actually needed. PS :- Also - can anyone let know the backlink quality of www.usedcarindelhi.com. Its PR 3, DA - 18, Majestic Citation Flow - 18, Trust Flow - 11 . Pl advise
Intermediate & Advanced SEO | | Modi0 -
301 Redirect and Webmaster Central
I've been working on removing canonical issues. My host is Apache. Is this the correct code for my htaccess? RewriteEngine On
Intermediate & Advanced SEO | | spkcp111
RewriteCond %{HTTP_HOST} ^luckygemstones.com$ [NC]
RewriteRule ^(.*)$ http://www.luckygemstones.com/$1 [R=301,L] SECOND!!! I have two websites under Google's Webmaster Central; http://luckygemstones.com which gets NO 404 soft errors... AND http://www.luckygemstones.com which has 247 soft 404 errors... I think I should DELETE the http://luckygemstones.com site from Webmaster Central--the 301 redirect handles the"www" thing. Is this correct? I hate to hose things (even worse?) Help! Kathleen0 -
Restructuring/Removing 301 Redirects Due To Newly Optimized Keywords
Just to be clear, this is for one unique page on a website. Also, please see my diagram attached. Let's say that a page's URL was originally /original. So, you optimize the page for a new keyword (keyword 1), and therefore change the URL to /keyword-1. A 301 redirect would then be placed... /original > /keyword-1 However, let's say 6 months down the road you realize that the keyword you optimized the page for (keyword 1) just isn't working. You research for a new keyword, and come up with (keyword 2). So, you'd like to rename the page's URL to /keyword-2. After placing a redirect from the current page (keyword 1) to the 'now' new page (keyword 2), it would look like this... /original > /keyword-1 > /keyword-2 We know that making a server go through more than one redirect slows the server load time, and even more 'link-juice' is lost in translation. Because of this, would it make sense to remove the original redirect and instead place redirects like this? /original > /keyword-2 /keyword-1 > /keyword-2 To me, this would make the most sense for preserving SEO. However, I've read that removing 301 redirects can cause user issues due to browsers caching the now 'removed' redirect. Even if this is ideal for SEO, could it be more work than it's worth? Does anyone have any experience/input on this? If so, I greatly appreciate your time! oDvLl.jpg
Intermediate & Advanced SEO | | LogicalMediaGroup1 -
Help with setting up 301 redirects from /default.aspx to the "/" in ASP.NET using MasterPages?
Hi SEOMoz Moderators and Staff, My web developer and I are having a world of trouble setting up the best way to 301 redirect from www.tisbest.org/default.aspx to the www.tisbest.org since we're using session very heavily for our ASP.NET using MasterPages. We're hoping for some help since our homepage has dropped 50+ positions for all of our search terms since our first attempt at setting this up 10 days ago. = ( A very bad result. We've rolled back the redirects after realizing that our session system was redirecting www.tisbest.org back to www.tisbest.org/default.aspx?AutoDetectCookieSupport=1 which would redirect to a URL with the session ID like this one: http://www.tisbest.org/(S(whukyd45tf5atk55dmcqae45))/Default.aspx which would then redirect again and throw the spider into an unending redirect loop. The Google gods got angry, stopped indexing the page, and we are now missing from our previous rankings though, thankfully, several of our other pages do still exist on Google. So, has anyone dealt with this issue? Could this be solved by simply resetting up the 301 redirects and also configuring ASP.NET to recognize Google's spider as supporting cookies and thus not serving it the Session ID that has caused issue for us in the past? Any help (even just commiserating!) would be great. Thanks! Chad
Intermediate & Advanced SEO | | TisBest0 -
Effect of 301 redirect to a relative url to homepage?
One of our new clients recently encountered a site-wide ranking drop for many keywords and I'm pretty confident regarding their link profile as to being 98% legit. Background: 1. Client full site is https, and all http pages are 301 redirected to their https counterpart 2. Client has ~50 links partners (all legitimate sites + schools etc) links to client with urls such as www.example.com/portal/123.aspx that redirects to www.example.com. 3. Client homepage 301 redirects from www.example.com to www.example.com/default.aspx and then 301 redirects to the relative url "/Home.aspx". 4. Client launched some testing with Google website optimizer tool. ~1-2 months ago. Symptoms: 1. Rankings dropped for basically many/all 30-40+ keywords by ~15 positions 2. Seomoz reports close to a double of existing pages + (600+) duplicate content in the same date range. Webmasters only report 80 duplicate titles though. 3. Domain authority by seomoz reduced a bit + backlinks recorded by seomoz to the website nearly halved in the past 2 months. I'm not sure if I narrowed this towards the right direction, and it isn't clear when the relative url 301 redirect was implemented: 1. The 301 redirect to the relative page (www.example.com/default.aspx to "/home.aspx") is accounting for the loss of links recorded by seomoz. 2. The ~50 links the client currently use (www.example.com/portal.123.aspx 301 redirecting to www.example.com, also relative) as a tracking tool is being considered 301 redirect abuse. 3. Maybe something went wrong with the usage of google optimizer tool for SEO purposes? Visitor traffic to each of the tested pages looked fine. I would greatly appreciate any advice/insights on what I might be missing in terms of direction / factors. Thanks! Alex
Intermediate & Advanced SEO | | sixspokemedia0