Maintaining Link Value Of Old URLS With 301 Redirects
-
Large ecommerce site that has been around for a long time (15+ years.) During that time technology has changed a lot and we are running into issues maintaining 301 redirects for very old urls. For example we have a good amount of links to product and category pages. Some of the old links are to products that still exist and will exist for many years to come.(of note little to no traffic comes via these links. Most of them are close to 9 years old so they are buried deep within articles, forums, or websites) However as we make changes to the site and URL structure these old urls are taking up more resources to continue to maintain 301 redirects. I am Leary of no longer supporting them because I do not want it to impact rankings however there is concern on how much development time and technology resources it takes to continue to support as time goes on.
Does anyone have experience handling redirects 3 or 4 url structures old? Looking for insight from someone who has crossed this bridge before.
-
We have changed the URLS a few times over the past decade. It is just maintaining some of the super old backlinks to category and product pages that are getting harder to maintain.
I appreciate you taking the time to answer.
-
Okay, got it. To figure out how much value you're getting from that traffic, you need to figure out what you want customers to do once they hit those pages. If the customers do the thing you want them to do (buy, lead gen, consume more content, etc), then you still want to keep those redirects. If they don't, you can probably kill them without any repercussions to the brand/site. You can also reach out to those sites that are hosting your old links and ask them to put in new, more relevant links, if those links are still valuable in that the traffic from that link drives customers to do the action you want them to do.
I also wanted to add something that, I know you may fully realize, but no one has said yet, for every page that you're 301'ing to the new structure, you can take that old page and those old assets off your server. All you need is the 301 redirect code.
-
So you have old URLs; have they been changed already?
I'm assuming not since you're getting great traffic from organic. If that's the case, why change them? There appears to be no problem unless I'm missing something (assuming you haven't changed the URL).
This may be a question for developers that have more knowledge.
Thanks!
-
Erica,
Thank you so much for the response. To clarify so that i understand your recommendation correctly. The pages do still get traffic, some get a lot of traffic from organic search. They just do not get a lot of referral traffic from other websites. For example I have a lot of cases where a customer links to one of our products in a tutorial they did on their website. Because the tutorial is old the link to us is from many years ago and the url has a super old url structure. And maintaining the system that helps figure out where that old url should point to on our site is causing the problem. Because it is hard to know how to judge how much value is coming from that link from an SEO perspective I am having a hard time determining if we should continue to maintain these very old urls linking to us from external domains.
Does that help clarify?
-
If you don't get any traffic to these very old pages, there's really no reason to keep the redirects. When we rebranded from SEOmoz.org to Moz.com, we killed a lot of very old pages that didn't get any traffic anymore. We didn't redirect them, just tossed them away. We only redirected out-dated pages that were still getting traffic.
-
Cole,
First thanks for the response.
I probably should have added a bit more detail for clarification. The simple 301 redirect example.com/product-a-123-xyz.html is 301 redirected to example.com/product-a can be handled easily.
However because some of the Old urls had dynamic aspects to them our system has to run code to handle the redirect logic so that the 301 redirect takes sends them the to correct place. For example we sell tires for motorcycles. Because of old technology the url 10 years ago included vehicle specific elements like the year, model brand. Right now we have redirect logic that recognizes that the link is coming in from an old dynamic url and 301 redirect the customer to that specific tire on our site. Then at the product level they can then choose which vehicle they have, all dynamic aspects are taken care of now with ajax. But maintaining that old logic is eating up resources and I am debating if it is worth doing so.
-
Let me make sure I understand your question. You have migrated several (old) URLs into one (new) URL.
I would simply 301 redirect any old URL to a new URL that relates. For example, example.com/product-a-123-xyz.html is 301 redirected to example.com/product-a
You don't have to worry about what articles, bookmarks, etc. have the wrong URL because they are now redirected to the correct URL to maintain link value.
Do not 301 redirect page A to Page B that does not relate.
If you have any other 404s that come up via GWT or Moz and you have a relevant page for that 404, then go ahead and place a 301 redirect in. I would monitor this weekly (every Monday for example). It shouldn't be more than 20-30 to go through at most and that way you continue monitoring link value.
Does this answer your question? I hope this helps.
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
-
Is 301 redirect the only way when using Vanity URLs?
We have been using vanity urls for some of our pages. Mostly the pages that have a vanity URL have a long URL length. But now the problem is, the vanity URL is getting displayed on the search engine when the particular keyword related to the page is entered. I checked the google search console, the vanity URL is indexed and the original URL remains unindexed. What should I do? Is adding 301 redirect to the vanity URLs are solution? Since some of vanity URLs are not redirecting to the original. Some of the original pages are not getting traffic. Also, can using canonical tag help?
Technical SEO | | tejasbansode0 -
301 Domain Redirect from old domain with HTTPS
My domain was indexed with HTTPS://WWW. now that we redirected it the certificate has been removed and if you try to visit the old site with https it throws an obvious error that this sites not secure and the 301 does not happen. My question is will googles bot have this issue. Right now the domain has been in redirection status to the new domain for a couple months and the old site is still indexed, while the new one is not ranking well for half its terms. If that is not causing the problem can anyone tell me why would the 301 take such a long time. Ive double and quadruple checked the 301's and all settings to ensure its being redirected properly. Yet it still hasn't fully redirected. Something is wrong and my clients ready to ditch the old domain we worked on for a good amount of time. backgorund:About 30 days ago we found some redirect loops .. well not loop but it was redirecting from old domain to the new domain several times without error. I removed the plugins causing the multi redirects and now we have just one redirect from any page on the old domain to the new https version. Any suggestions? This is really frustrating me and I just can't figure it out. My only answer at this point is wait it out because others have had this issue where it takes up to 2 months to redirect the domain. My only issue is that this is the first domain redirect out of many that have ever taken more than a week or three.
Technical SEO | | waqid0 -
301 Redirect Question
I am working with a website and I ran a Screaming Frog and noticed there are 4,600 301's on the website (www.srishoes.com). It seems like the issue is between the www. and without it and they aren't working together. Is this something that the website provider should update and what type of impact might this have on the site? Thanks!
Technical SEO | | ReunionMarketing
Matt0 -
Redirect if old browser or OS to other domain?
Hi, I use cloudflare free SSL option. All is fine except it wont work with windows XP . How do you think is it ok in case of old OS/Browser redirect visitors to other domain or subdomain? What could be impacts or consequences of such step? On the moment if page meko.lv is accessed from XP sp1,2 there is error. If it is possible how could such redirect look? Thanks
Technical SEO | | Mekounko0 -
301 redirect not working
Hi there! I have recently moved a domain that has been indexed by google and setup redirects so that it forwards to the new domain. It seems like the only redirect that actually is working is the canonical and main domain but every other page and or page nested within a folder are not working. Here is an example of some of the redirects. Am I doing this wrong? It seems to be going to the new domain but can't find the actual pages.... RewriteEngine On
Technical SEO | | twotd
RewriteBase /
RewriteCond %{HTTP_HOST} !agoodsweep.com$ [NC]
RewriteRule ^(.*)$ http://agoodsweep.com/$1 [L,R=301]
redirect 301 woodstoveservicerepair.html http://agoodsweep.com/woodstoveservicerepair/
redirect 301 /westchesterchimney.html http://agoodsweep.com/west-chester-chimney/ Thanks in advance for any help!!0 -
301 Redirect / cross-domain canonical to a URL w/ Ampersand
I have a question regarding ampersands, we are needing to redirect to a URL w/ an ampersand in the URL: http://local.sfgate.com/b18915250/Sam-&-Associates-Insurance-Agency Will Google pass page authority/juice despite the fact that there is an ampersand in the URL, if we were to 301 redirect or cross-domain canonical to the url? Should we 301 redirect to http://local.sfgate.com/b18915250/Sam-%26-Associates-Insurance-Agency instead of http://local.sfgate.com/b18915250/Sam-&-Associates-Insurance-Agency? I don't have the option of removing the ampersand Thank you for your time!
Technical SEO | | Gatelist0 -
Where does Wordpress store the 301 redirects?
Hi, I've just created a campaign for my new wordpress blog and found 11 301 redirects which I was not aware of. It looks like wordpress has created them automatically. Does any one know how wordpress handles this issues or where are they stored so I can delete them? They are of no use for me. 9 of these redirects point to the same url with an added '/' and are in pages 1 is on a post. I've been changing the permalink and some urls several times and maybe one of these times the Wordpress has automatically created the 301 redirect. But why? I do not want to keep the old url. the last redirect is very strange it goes from http://www.mydomain.com/folder to http://www.mydomain.com where folder is the folder where I installed wordpress. But again, I want no one to type the url with the folder name or even know this folder exists. Any comment on this would be greatly appreciated. Thanks a lot, David
Technical SEO | | dballari0 -
Ajax #! URLs, Linking & Meta Refresh
Hi, We recently underwent a platform change and unfortunately our updated ecom site was coded using java script. The top navigation is uncrawlable, the pertinent product copy is undetectable and duplicated throughout the code, etc - it needs a lot of work to make it (even somewhat) seo-friendly. We're in the process of implementing ajax #! to our site and I've been tasked with creating a document of items that I will test to see if this solution will help our rankings, indexing, etc (on Google, I've read the issues w/ Bing). I have 2 questions: 1. Do I need to notify our content team who works on our linking strategy about the new urls? Would we use the #! url (for seo) or would we continue to use the clean url (without the #!) for inbound links? 2. When our site transferred over, we used meta refresh on all of the pages instead of 301s for some reason. Instead of going to a clean url, our meta refresh says this: . Would I update it to have the #! in the url? Should I try and clean up the meta refresh so it goes to an actual www. url and not this browsererrorview page? Or just push for the 301? I have read a ton of articles, including GWT docs, but I can't seem to find any solid information on these specific questions so any help I can get would be greatly appreciated. Thanks!
Technical SEO | | Improvements0