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
-
Ugly Redirect Chain
Hey everyone, Hoping to get your take on this: We have some very high demand products, they usually sell out in minutes (lucky us, eh?!) We are implementing a queue function on a product page - basically if too many people try to check out at the same time, we dump them in a queue The queue could kick in before or after search engines have indexed the product page The product page has markup and on-page content relating to the product. The queue page exists on an external (yes, external) site The queue page will not have any of the product info, markup, or optimised page title Product page will 302 to queue page and starts a series of 302 redirects! Here's the sequence when queue is active: CANONICAL product page (with markup, on-page product info, optimised page title, etc.)
Intermediate & Advanced SEO | | TSEOTEAM
>> 302 >> queue page on external domain (ZERO markup, product info or page title)
>>302>> same queue page, but throwing a hashed queue ID into the URL (basically giving you your place in the queue)
HELD IN QUEUE FOR A FEW MINUTES
**>> 302> ** NON-CANONICAL product page (with markup, on-page product info, optimised page title, etc.) I can foresee two scenarios search engine has indexed product page prior to queue kicking in. Then queue kicks in 302ing search engine to queue page. because it's a 302 the crappy queue page content is indexed back to the originating product page. This causes search engines to drop the product page cos all the product-specific markup/content has been overwritten with crappy queue page content search engines don't manage to index product page before queue kicks in. They crawl product page URL, get 302 to queue page, index crappy queue page content and think the product page is crappy, so don't traffic it. They will recrawl the product page once the queue's turned off, only to discover the product has sold out - boo. I very much doubt the search engines will 'wait for a few minutes' so may never end up reaching the product page again. I'm trying to get the markup/product info and optimised meta data injected into the queue page, so that remains present at all points on the journey in the hope that this enables search engines to continue to rank and traffic the product page. What's your take on this? Any suggestions on how we might overcome the issues? (before you ask; avoiding using the queue system is impossible, sorry!) Thanks!1 -
Would You Redirect a Page if the Parent Page was Redirected?
Hi everyone! Let's use this as an example URL: https://www.example.com/marvel/avengers/hulk/ We have done a 301 redirect for the "Avengers" page to another page on the site. Sibling pages of the "Hulk" page live off "marvel" now (ex: /marvel/thor/ and /marvel/iron-man/). Is there any benefit in doing a 301 for the "Hulk" page to live at /marvel/hulk/ like it's sibling pages? Is there any harm long-term in leaving the "Hulk" page under a permanently redirected page? Thank you! Matt
Intermediate & Advanced SEO | | amag0 -
Will 301 Redirects Slow Page Speed?
We have a lot of subdomains that we are switching to subfolders and need to 301 redirect all the pages from those subdomains to the new URL. We have over 1000 that need to be implemented. So, will 301 redirects slow the page speed regardless of which URL the user comes through? Or, as the old urls are dropped from Google's index and bypassed as the new URLs take over in the SERPs, will those redirects then have no effect on page speed? Trying to find a clear answer to this and have yet to find a good answer
Intermediate & Advanced SEO | | MJTrevens0 -
Do image "lightbox" photo gallery links on a page count as links and dilute PageRank?
Hi everyone, On my site I have about 1,000 hotel listing pages, each which uses a lightbox photo gallery that displays 10-50 photos when you click on it. In the code, these photos are each surrounded with an "a href", as they rotate when you click on them. Going through my Moz analytics I see that these photos are being counted by Moz as internal links (they point to an image on the site), and Moz suggests that I reduce the number of links on these pages. I also just watched Matt Cutt's new video where he says to disregard the old "100 links max on a page" rule, yet also states that each link does divide your PageRank. Do you think that this applies to links in an image gallery? We could just switch to another viewer that doesn't use "a href" if we think this is really an issue. Is it worth the bother? Thanks.
Intermediate & Advanced SEO | | TomNYC0 -
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 -
After the 301 redirect
Hi all, A quick question, after you have setup your 301 re-directs in .htaccess - is it necessary to keep your content in the original domains directory? My thinking is that requests do get as far as referencing the directory, thus it should be safe to delete all the files on the old domain? Thanx!
Intermediate & Advanced SEO | | gazza7770 -
Questions about 301 Redirects
I have about 10 - 15 URLs that are redirecting to http://www.domainname.comwww.domainname.com/. (which is an invalid URL)The website is on a Joomla platform. Does anyone know how I can fix this? I can't figure out where the problem is coming from.
Intermediate & Advanced SEO | | JohnParker27920 -
301 redirect from .html to non .html?
Previously our site was using this as our URL structure: www.site.com/page.html. A few months ago we updated our URL structure to this: www.site.com/page & we're not using the .html. I've read over this guide & don't see anywhere that discusses this: http://www.seomoz.org/learn-seo/redirection. I've currently got a programmer looking into, but am always a bit weary with their workarounds, as I'd previously had them cause more problems then fix it. Here is the solution he is looking to do: The way that I am doing the redirect is fine. The problem is of where to put the code. The issue is that the files are .html files that need to be redirected to the same url with out a .html on them. I can see if I can add that to the 404 redirect page if there is one inside of there and see if that does the trick. That way if there is no page that exists without the .html then it will still be a 404 page. However if it is there then it will work as normal. I will see what I can find and get back. Any help would be greatly appreciated. Thanks, BJ
Intermediate & Advanced SEO | | seointern0