Redirect Chains vs. Redirect Loops: What's the Difference?

A redirect chain is a URL that redirects to another URL that redirects again — A → B → C — before finally landing somewhere. A redirect loop is a chain that never resolves: A → B → A, forever, until the browser gives up and shows an error. Chains are usually a performance and SEO problem; loops are a complete failure.

Redirect chains

Each hop in a chain is a full round-trip: the browser requests A, gets told to go to B, requests B, gets told to go to C, and only then loads the actual page. Every extra hop adds latency, and search engines pass less link equity through each additional step — a chain of three or four hops can meaningfully dilute the ranking value a redirect was supposed to preserve.

Chains build up gradually and often invisibly. A page moves once (redirect added), then moves again later during a redesign (a second redirect added on top instead of updating the first one), and now anyone visiting the original URL takes two unnecessary hops to get anywhere.

Redirect loops

A loop happens when the chain circles back on itself — most simply, A redirects to B and B redirects back to A. Browsers detect this and stop, usually showing an error like "too many redirects" instead of any page at all. Loops are almost always a configuration mistake: two rules pointing at each other, or a redirect rule that accidentally matches its own destination.

What the error actually says

Different browsers word the loop error differently, but it's the same problem underneath:

"ERR_TOO_MANY_REDIRECTS" is Chrome and Edge's version — you'll see "This page isn't working. [domain] redirected you too many times." It means the browser followed redirects until it hit its internal limit (usually around 20 hops) without ever landing on a real page.

"Load cannot follow more than 20 redirections" is Firefox's version, and you'll most often see it in the DevTools console rather than as a full-page error — it shows up when a fetch() or XMLHttpRequest call hits the same loop, not just a normal page navigation. If you're seeing this while a page otherwise looks fine, check for a specific request (an API call, an asset, a tracking script) that's looping rather than the page itself.

Either way, the fix is the same: find where the redirect points back on itself and break the cycle. Clearing cookies or cache almost never fixes this — the loop is in the redirect configuration, not in your browser.

Check a URL right now

How RedirectIQ finds chains for you

The widget above checks one URL, on demand, whenever you ask it to. If you have Edge Proxy enabled on a domain, RedirectIQ does something similar continuously: every proxied request is checked, and if your origin's own internal redirects eventually land on what looks like a broken or error page, that path gets surfaced as a "Chain" suggestion in your dashboard — with real hit counts, and, if you've connected Google Search Console, the impressions, clicks, and backlinks at risk. One click turns the suggestion into a proper, direct redirect rule, collapsing the chain to a single hop.

To be precise about scope: this catches chains that resolve to an error page on a proxied domain — it isn't a blanket scan for every possible chain across every redirect rule you've configured. For that broader picture, the same Suggestions system also accepts crawl exports from Ahrefs, SEMrush, and Screaming Frog, which is how most teams already find chains today if they don't have Edge Proxy enabled yet. For the full picture of how this fits into fixing 404s and chains at scale, see 404 Errors and Redirect Chains Are Quietly Eroding Your SEO.

Fixing a chain once you've found one

The fix is almost always the same: point the original URL directly at the final destination and remove the intermediate hop(s), rather than leaving the old redirects layered on top of each other. One rule, one hop.

Verifying the fix

Re-run the URL through the widget above, or the full redirect chain analyzer, and confirm you're down to a single hop. For a one-off check on a single URL without the chain view, the redirect checker works too.

Connect a domain and enable Edge Proxy, and RedirectIQ finds chains like this on your own site continuously — see how it works →