Redirect Chains - Accept the 301 chain or link from the original page??
-
Hi everyone,
I have a client that re-launched his site and it's gone from 100 pages to 1000 (new languages/increased product pages etc)
We've used 301's to map the old site to the new database driven site. BUT the new site is creating extremely long URL's:
e.g. www.example.com/example_example_example/example_example_example_example
Obviously I want to change these URL's:
THE PROBLEM.....
I am worried about the Chain Redirects. I know two 301 redirects is okay (although it's not great), but I wonder if there is an alternative:
When I've implemented the new URL structure the chain will look like this:
www.oldsite.com 301 redirects to www.newsitewithdodgyurls.com which then 301 redirects to www.mynewsitewithgreaturls.com
Seeing as the new site has only been live for a month, and hasn't really gained many external links, should I:
301 from the original site (www.oldsite.com) straight to the new site (www.mynewsitewithgreaturls.com)? If so, what would I do with the pages that I have not redirected? Let them 404?
OR
Leave the 301 chain in place?
Your advice, and any other suggestions would be much appreciated
Thanks
-
Thought in general you could use canonical tag cross domain too http://moz.com/blog/cross-domain-canonical-the-new-301-whiteboard-friday
-
Hi Ryan,
Thanks. I've confused the issue slightly. All these changes have been made on the same domain. It's only the URL structure that is changing. (sorry the examples I've used say something very different to that).
Your logic of finding mapping methods of redirecting is a solid plan though. I will work with the developer to implement it. And for anything I cant find logic for I will either 301 redirect or rel=canonical it.
Thanks again. That's hugely helpful.
-
Solution could therefore be to implement the rel=canonical tag on the intermediary site URL's pointing to the new site URL's
No.
The canonical tag can only be used within a domain.
Since you have determined the URL structure will change, I would recommend finding a logic that would apply to all URLs so you can map from the old site to the new one. Even if each logic piece only applied to 10% of the site, then you can map everything over in a total of 10 redirects.
If your current sites URL is www.oldsite.com/product1 and the new site URL is www.newsite.com/retail/us/stores/items/products/1 you can still use logic to make the conversion IF this same logic can be applied to all, or a worthwhile percentage, of the site.
-
Hi Ryan,
Thanks very much for responding in such detail, that's awesome.
Yeah, I think I'm abusing the 404 page a little. The vast majority of the thousand pages on the site will still exist but will be on different URL's (duplicate content ALERT!)
That as you rightly say could cause a problem for people landing on the site, and for duplicate content.
SO...
I don't want to do the thousands of individual redirects due to server load and potential penalties
Solution could therefore be to implement the rel=canonical tag on the intermediary site URL's pointing to the new site URL's, so although the pages aren't de-indexed, the new site URL's will soon be in a dominant position over the intermediary URL's in the serp's.
What do you reckon?
-
Hi James. Please allow me to offer some clarifications:
A. server speed- too many 301 redirects is going to put an unnecessary load on the server and reduce speed =BAD
The concern is HOW the redirects are made. If your client has a URL www.oldsite.com, and he moves his entire 10k page site to a new URL, www.newsite.com, and he keeps his URL structure the same at the new site, then the entire re-direct can be done in a single line. In this case there is absolutely no additional load on the server.
Alternatively, if the new site structure is such that hundreds of rules need to be written to properly complete the re-directs, then yes, your speed can be impacted as each request requires the server to iterate through hundreds of lines of code to seek a match.
You shared there would be a change to the URL structure. Your 301 logic would depend on if the change follows a logical pattern to where a regex mapping can be created in a few rules.
B. being penalised- too many 301 redirects can be viewed as aggressive PR sculpting and your 301's can be devalued
C. Avoiding 301 redirect chains- Matt Cutt's interview with Rand in 2010 said 301 chains are not a good thing as a general rule
This refers to chain 301s, a practice that I do not use and would never advise. Go to the original site and ensure each page is properly directed to it's final location.
You can redirect all 100k pages of site A to site B and that would not be considered "too many redirects" nor page sculpting. When you re-direct from site A to site X to site Y to site Z then to site B (the final destination), that would be considered too many re-directs. This could happen even if the re-directs were within the same couple of sites. Even if the re-directs all worked, each hop is a leak in the link juice pipeline.
404's are not necessarily a bad thing
I agree, but a 301 is far superior IF you are keeping the content.
Let's say someone is looking for an article on the 1982 Corvette Stingray. He locates a search result, clicks on it and is taken to the article on your site. He is a happy search engine user, and now a happy visitor on your site. Everyone wins.
Using the same example, the person gets a 404 page on your site. There is an extremely high chance the user will simply return to Google and move on to the next result. Everyone looses.
404s should be used for content when it is highly unlikely a user will ever look for it in a search result OR if you no longer have the content. You would never want to 404 a link when you still have the content and know where it is located.
With all of the above noted, I agree with your plan. The pages with no value, meaning the pages are not searched for or you no longer have the content, can 404.
-
Hi guys, thank you both for your responses.
I don't think I framed my question correctly though. The 301 redirect issues I am worried about are:
A. server speed- too many 301 redirects is going to put an unnecessary load on the server and reduce speed =BAD
B. being penalised- too many 301 redirects can be viewed as aggressive PR sculpting and your 301's can be devalued )(see here) =BAD
C. Avoiding 301 redirect chains- Matt Cutt's interview with Rand in 2010 said 301 chains are not a good thing as a general rule (no need to watch video, it's in the text below) = BAD
SO....
Ryan K, I agree with you in your decision to direct from old site direct to new site. However, 404's are not necessarily a bad thing (see google's stance)
Ryan P, I agree with your suggestion of a sitemap
** So my plan as far as I see it is this:**
1. 301 redirect all the original site (www.oldsite.com) pages to the new URL's at (www.mynewsitewithgreaturls.com)
2. Any pages on the intermediary site (www.newsitewithdodgyurls.com) that have gained backlinks 301 them to the new site aswell
3. Let pages on the intermediary site with no SEO value 404
4. Create a prioritised sitemap (as per Ryan P's suggestion)
This solves the problem on chaining 301 redirects, it reduces the load on the server, and it avoids penalisation due to too many 301's
That's how I see it going down anyway. Would love to hear if you think that's the right plan of action.
Anyone else feel free to chip in aswell!!
-
With the addition of a sitemap specifying only the great URLs and rel=canonical on those pages you should have the situation cleaned up in a tidy way. It's not uncommon to have to redirect from a few older sources as a website ages.
-
I think the correct thing to do is pretty clear.
301 the pages from the original site to their new URLs directly just as you suggested.
what would I do with the pages that I have not redirected? Let them 404?
The right thing to do is redirect them properly. Why would you leave any pages as a dead end 404?
How much time and resources do you have available for this project. That answer should be balanced with other factors:
Are the existing links worth the effort? Is this an older site with high quality links?
What is your SEO rank worth? Is the site's sales dependent on SERP? Since you are posting here, I would assume the answer is yes.
With only 100 pages involved, I would do whatever it takes to ensure each page is properly redirected to the appropriate page on the new site.
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 redirecting a site that currently links to the target site
I have a personal blog that has a good amount of back links pointing at it from high quality relevant authoritative sites in my niche. I also run a company in the same niche. I link to a page on the company site from the personal blog article that has bunch of relevant links pointing at it (as it's highly relevant to the content on the personal blog). Overview: Relevant personal blog post has a bunch of relevant external links pointing at it (completely organic). Relevant personal blog post then links (externally) to relevant company site page and is helping that page rank. Question: If I do the work to 301 the personal blog to the company site, and then link internally from the blog page to the other relevant company page, will this kill that back link or will the internal link help as much as the current external link does currently? **For clarity: ** External sites => External blog => External link to company page VS External sites => External blog 301 => Blog page (now on company blog) => Internal link to target page I would love to hear from anyone that has performed this in the past 🙂
Intermediate & Advanced SEO | | Keyword_NotProvided0 -
Going from 302 redirect to 301 redirect weeks after changing URL structure
I made a small change on an ecommerce site that had big impacts I didn't consider... About six weeks ago in an effort to clean up one of many SEO-related problems on an ecommerce site, I had a developer rewrite the URLs to replace underscores with hyphens and redirect all pages throughout the site to that page with the new URL structure. We didn't immediately update our sitemap to reflect the changes (bad!) and I just discovered all the redirects are 302s... Since these changes, most of the pages have a page authority of 1 and we have dropped several spots in organic search. If we were to setup 301 redirects for the pages that we changed the URL structure would there be any changes in organic search placement and page authority or is it too late?
Intermediate & Advanced SEO | | Nobody16116990439410 -
Domain forward or 301 redirect
My company recently acquired another company including their web presence. We are soon ending their website and will be either 301 redirecting their domain to our domain or pointing their domain to our nameservers. Their domain authority is only 25 while our domain authority is 32. Their domain was created in 1998 while ours was created in 1999. So to keep our domain authority up or enhance it, should we do a 301 redirect or a domain forward. And that is if there is any difference? Thanks Chris
Intermediate & Advanced SEO | | topsailislander0 -
How to do a site migration followed by a domain migration and avoid 301 redirect chains?
Hi all, The current roadmap for our Eng team has us performing a site migration (redirecting one subfolder to another subfolder) and then a domain migration shortly after. The way I see it, I have 2 scenarios (the 1st involves the site migration THEN the domain migration and the 2nd is the site migration and domain migration being done simultaneously): olddomain.com/subfolder-old to olddomain.com/subfolder-new THEN olddomain.com/subfolder-new to newdomain.com/subfolder-new AND olddomain.com/subfolder-old to newdomain.com/subfolder-new olddomain.com/subfolder-old to newdomain.com/subfolder-new I also understand that there are two best practices for a domain migration and they are 1) keep everything the same that you can to help Google understand it is the same page, just on a different domain and 2) avoid chain redirects. As you can imagine, scenario 1 requires more Eng costs than scenario 2. So, my question is, is scenario 2 a perfectly viable option or should I make the push to go for scenario 1? Any advice is greatly appreciated!
Intermediate & Advanced SEO | | brad-causes1 -
How to build links to landing pages?
I have been using link baits like infographics to get quality links to my site and I have observed that these tactics are great to get links to the home page or that particular post page where infographic was originally posted. But we have various other important landing pages and we want to transfer some link equity to those pages. Whenever we publish an infographic we post it on out blog with an embed code carrying anchor text pointed to our site’s home page. People who share our infographic, normally links to the home page or to the post page where they find that particular item. So, what are the possible ways to get links to any other landing page? Can we post some bait on other landing pages as well. I need to know some more techniques to attract deep links. Thanks
Intermediate & Advanced SEO | | shaz_lhr1 -
Two links from one page with different Anchor text
Example Business Name - UberPuter UberPuter targets the keywords "Computer Repairs" right from their home page. UberPuter has the option to place links on 150 of their customers pages that are happy with the service. Would it be best to place two anchor text links one with the brand name and one with the keyword anchor text in "computer repairs" pointing both at the home page or should UberPuter only place one link back to the home page for the Keyword Anchor text? To the best of my knowledge G only counts the first link on a page as a "Vote" so my thought is to only include the single link with the keyword anchor text. Thanks,
Intermediate & Advanced SEO | | SEOKeith0 -
301 Redirect To Corresponding Link No Matter The URL?
Hey guys I have hosting on Host Gator with I believe an apache web server. I need a code to put in the HT ACCESS to redirect all WWW URL's to their corresponding http URL. I haven't been able to get a code to work. For example, http://www.mysite.org/page1.html -> http://mysite.org/page1.html , without having to redirect hundreds of pages individually Here is the format my server uses in the HT ACCESS file for 301 redirects. RewriteCond %{HTTP_HOST} ^mysite.org$ [OR] RewriteCond %{HTTP_HOST} ^www.mysite.org
Intermediate & Advanced SEO | | DustinX
$RewriteRule ^Electric-Pressure-Cookers.html$ "http://mysite.org/Pressure-Cookers.html" [R=301,L] Thanks0