Huge httaccess with old 301 redirects. Is it safe to delete all redirects with no traffic in last 2 months?
-
We have a huge httaccess file over several MB which seems to be the cause for slow server response time.
There are lots of 301 redirects related to site migration from 9 months ago where all old URLs were redirected to new URL and also lots of 301 redirects from URL changes accumulated over the last 15 years.
- Is it safe to delete all 301 redirects which did not receive any traffic in last 2 months ?
- Or would you apply another criteria for identifying those 301 that can be safely deleted?
- Any way to get in google analytics or webmaster tools all 301 that received traffic in the last 2 months or any other easy way to identify those, apart from checking the apache log files ?
-
Aleyda, this is super useful , thanks a lot for this excellent advice.
I will still need to do some research on how to best compile a comprehensive list of incoming links, as moz and search console data is still kind of limited for this purpose. -
Hi there,
The best way to identify if it's already safe to eliminate the 301 redirects from a previous Web migration/redesign is to verify if the old pages (you need to have a list of those old URLs) that were redirected in the past:
- Are still crawled and indexed? (You can check the indexation easily in Google with "site:" directly, and then if you identify these old URLs in Google Search Console Search Analytics, by filtering by pages). If so, which pages? Are they also ranking still well for relevant terms? Which ones? Identify why is still ranking instead of the new version of the page: Is the redirect correctly implemented? Going to a new version that is really relevant? The old pages being linked from internal or external sources that are passing high value? What's the historical and trend of crawling activity of those pages over time? Is it going down? (that you can analyze via logs).
- Are still getting traffic? Identify which source: is it organic search traffic? referral from other sites? You can check this by verifying the URLs activity from the old site version in Google Analytics.
- Are still being linked? A must if you're still ranking with these pages and traffic. Verify which sources are still linking to them and which are the one passing the highest value. Make the most to update these links to go to the new URL versions to stop passing value and traffic to the old URLs.
If you verify that these old URLs are not indexed, nor getting visibility or traffic anymore either from organic search or any other traffic source, then it's ok to eliminate the redirects.
Nonetheless, if they are still getting visibility & traffic you will need to keep the redirects, otherwise you will lose those visitors (and also give a bad user experience). The goal in this case would be to ask the previous questions among others to identify the reason why are they still being indexed, linked, etc. and update the relevant links, content, etc. to change this behavior and help Google to catch up with the URLs migrations.
I hope it helps
-
The problem is: It is delaying server response time to 1,5 seconds on average and is increasing significantly server load. We are talking here about more than 19.ooo rows with hundreds of rewrite rules based on URL patterns. So we have a pressing need to take action.
Is there a way to easily identify those URLs that triggered a 301 in the last 2 months? Doing it based on the apache logs seems a bit daunting as I did not find a tool that filters from the apache logs the 301s. Can I get this information from analytics or any other way easily?
-
Hi there,
Does it represent a problem for you, having those redirects in the htaccess?
Personaly, and in a SEO perspective, I will never delete the 301s redirects done in any site.The fact that those pages havent recieved traffic doesn't mean that the old URL might have any links or authority that is now redirected to the actual URL.
Here you have a Q&A question, answered by some experts:
How long should I keep the 301 redirect file - Moz Q&AHope it helps.
GR.
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 it worth keeping a decades-old domain that's merely 301 redirecting to the main domain?
Hi fellow Moz SEOs, We have a bigger client who we just did an SEO Site Audit for, and it was discovered that they have several domain names that are simply 301 redirecting to their main domain name. One of their domains in particular is decades old, and the client is asking if there is any value in keeping it (and the others), or simply leaving them as-is. Considering the domain age, does anyone have any recommendations? Much appreciated, Zack Barton
Intermediate & Advanced SEO | | Zack
Barton Interactive
(833) 442.6853 // office
(408) 910.7750 // mobile
https://bartoninteractive.com0 -
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 -
Pages that did NOT 301 redirect to the new site
Hi, Is there a tool out there that can tell me what pages did NOT 301 redirect to the new sites? I need something rather than going into google.com and typing in site:oldsite.com to see if it's still indexed and if it's not 301 redirecting.. I'm not sure if screaming frog can do that. Thanks.
Intermediate & Advanced SEO | | ggpaul5620 -
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 -
Blog tags are creating excessive duplicate content...should we use rel canonicals or 301 redirects?
We are having an issue with our cilent's blog creating excessive duplicate content via blog tags. The duplicate webpages from tags offer absolutely no value (we can't even see the tag). Should we just 301 redirect the tagged page or use a rel canonical?
Intermediate & Advanced SEO | | VanguardCommunications0 -
301 Redirect To Another 301 Redirect
Hi, We have a client with an old domain that they want to redirect to their primary domain. They also have a few older domains pointing to the old domain. Do you recommend leaving them as redirects that point to the old domain? This will create a redirect to a redirect situation. Or, is it better to go ahead and redirect those older domains to the primary one's, removing one layer of redirect? Thank you! Jessie
Intermediate & Advanced SEO | | JessieT0 -
Need advice on 301 domain redirection
Hello friends, We have two sites namely spiderman-example.com & avengers-example.com which sells the same product listed out under similar categories, since we are about to stop or put down the site “avengers-example.com” because we just want to concentrate in bringing up a single brand called spiderman-example.com. “Spiderman-example” has comparatively more visitors and conversion rates than ''avengers-example'' ie. 90 % more traffic and conversion. Avengers-example has a small fraction of loyal customers who still search for the brand-name & there are a hand-full of potential keywords those ranking on its own. So is it advisable to redirect Avengers-example to spiderman-example using 301-redirect? Will this help to gain any link-juice from Avengers-example? If so how can we effectively redirect between two domain’s with minimal loss in page authority & linkjuice to enhance ''spiderman-example''? Off beat:These names "Avengers" and "Spiderman" were just used as an example but the actual site names has no relation to the ones mentioned above.
Intermediate & Advanced SEO | | semvibe0 -
Explaining 301 redirects instead of 302
I am trying to explain in layman's terms to a client why using 302 for their redirects (which they have done themselves) is not right. There view is they do not seem to listen or believe what is being said to them and do not want to do permanent damage to the old domain so are using 302 redirects. I have explained over and over 301 is needed but I do not seem to be good at communicating this. Can someone give me a good example or description I can use to get my point across?
Intermediate & Advanced SEO | | JohnW-UK0