Redirect Chains and Loops: The Complete 2026 Guide

A single redirect is harmless. A chain of three or more is a performance and ranking liability. Redirect chains and loops silently degrade your site's health, and most site owners do not realize they exist until a traffic drop forces an audit. This guide covers everything you need to identify, fix, and prevent them in 2026.

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C, which finally serves a 200 response. Each hop adds latency. A browser or crawler must follow every link in the chain before reaching the destination.

Example chain:

/page-a  ->  301 ->  /page-b  ->  301 ->  /page-c  ->  301 ->  /page-d  200

A redirect loop is worse. URL A redirects to URL B, which redirects back to URL A. The browser or crawler bounces between URLs until it hits a maximum redirect limit and fails with an error.

Example loop:

/page-x  ->  301 ->  /page-y  ->  301 ->  /page-x  (infinite)

Crawl budget waste. Google's crawlers have a limited budget per site. Each hop in a chain consumes time and resources. A site with widespread redirect chains can waste 30-50% of its crawl budget.

Link equity dilution. Every hop in a chain causes some leakage of PageRank. While the exact formula is proprietary, each additional hop reduces the equity passed to the final destination.

Indexing delays. Chains slow down discovery. If Google encounters a chain during a crawl cycle, it may run out of time before reaching the final page, delaying indexing.

User experience impact. Each redirect hop adds 50-200ms of latency. A chain of four hops adds up to a full second of extra load time. Users bounce.

1. Direct all redirects to the final URL. If /a -> /b -> /c, change /a to redirect directly to /c.
2. Update internal links. Replace any link pointing to an intermediate URL with a direct link to the final destination.
3. Use a redirect audit tool. Tools like Redirect Path (Chrome extension) and HTTP status checkers highlight chain length in real time.
4. Set up monitoring. Regular crawl audits catch new chains before they grow.

• Maintain a redirect map. Document every redirect in a CSV or database with source, target, status, and date.
• Set chain-length alerts. Your monitoring should fire when any URL requires more than two hops.
• Avoid regex cascades. Complex redirect rules in .htaccess or nginx configs can create unintended chains. Test every rule against a URL inventory.
• Decommission old redirects. When you consolidate content, remove redirects that no longer serve traffic. Keep a log for historical reference.

• [ ] Run a full site crawl and export chain length data
• [ ] Fix all chains longer than two hops by rewriting source URLs to point to the final destination
• [ ] Identify and break all redirect loops (start with any URL that returns a 3xx after following redirects)
• [ ] Update internal links to skip intermediate redirect targets
• [ ] Set up monthly crawl monitoring with chain-length alerts
• [ ] Document all remaining redirects in a redirect map

1. Google Search Central. "Redirect chains and loops." developers.google.com/search/docs/crawling-indexing/redirects
2. Screaming Frog. "How to find and fix redirect chains." screamingfrog.co.uk/seo-tips/redirect-chains/
3. Moz. "Redirect Chains and Redirect Loops." moz.com/learn/seo/redirect
4. Ahrefs. "Redirect Chains: How To Find and Fix Them." ahrefs.com/blog/redirect-chains/