Redirect Chains
A series of multiple consecutive URL redirects that waste crawl budget and dilute link equity.
Also known as: Redirect Loops, 301 Chains, Redirect Hops
Category: Concepts
Tags: seo, technical, crawling, performance, web
Explanation
A redirect chain occurs when a URL redirects to another URL, which redirects to yet another URL, creating a sequence of hops before reaching the final destination. Each hop wastes crawl budget, increases page load time, and can dilute the link equity passed to the final page.
Example of a redirect chain:
Page A (301) -> Page B (301) -> Page C (301) -> Page D (final)
Instead, Page A should redirect directly to Page D.
Types of redirects and their impact:
- **301 (Permanent)**: Passes most link equity (~90-99%). Tells search engines the move is permanent.
- **302 (Temporary)**: May not pass full equity. Signals the original URL should remain indexed.
- **Meta refresh**: Client-side redirect. Slower, passes less equity, poor user experience.
- **JavaScript redirects**: May not be followed by all crawlers. Unreliable for SEO.
Why redirect chains are harmful:
- **Crawl budget waste**: Each hop costs an additional server request; Google may stop following after 5+ hops
- **Link equity loss**: Some equity is lost at each redirect step
- **Slower page load**: Each redirect adds latency (typically 100-500ms per hop)
- **Indexing confusion**: Search engines may index an intermediate URL instead of the final destination
- **User experience**: Noticeable delays with long chains
Common causes:
- Site migrations done incrementally over years
- CMS URL changes without updating old redirects
- HTTP to HTTPS migration layered on existing redirects
- Domain changes without consolidating redirect rules
- Trailing slash inconsistencies
How to fix:
- Audit redirects with tools like Screaming Frog, Ahrefs, or Sitebulb
- Replace chains with single direct redirects to the final destination
- Update internal links to point to final URLs directly
- Monitor server logs for redirect patterns
- Implement redirects at the server level (not via JavaScript or meta tags)
- Review redirect rules during site migrations
Related Concepts
← Back to all concepts