Redirect Chains and Loops: Why They Hurt and How to Fix Them

A redirect chain is when URL A redirects to B, which redirects to C. A redirect loop is when the path eventually points back on itself, so the page never loads. Both are common after years of site changes — and both cost you.

Why chains hurt

• Wasted crawl budget: each hop is a request Google did not spend on real pages.
• Diluted signals: link equity can erode across multiple hops.
• Slower for users: every hop adds latency, hurting experience and Core Web Vitals.

Why loops break everything

A loop returns a browser error ("too many redirects") — the page is completely inaccessible to users and crawlers. It is an emergency-level bug.

How to fix them

1. Crawl your site (Screaming Frog, Sitebulb) and list every redirect with its hop count.
2. Flatten chains: point the first URL directly to the final destination, removing intermediate hops.
3. Break loops by finding the rule that points back and correcting the destination.
4. Update internal links to the final URL so you stop generating new chains.
5. Re-crawl to confirm every redirect is a single hop.

Related: 301 vs 302 · Crawled – currently not indexed