Redirect Chains: The Slow Leak Nobody Notices

A single redirect — old URL to new URL — is nearly free: an extra network round-trip measured in milliseconds, and search engines follow it without much friction. A redirect chain — URL A to URL B to URL C, three or four hops before landing on the page that actually exists — is a different problem, and it accumulates from a series of individually reasonable decisions rather than one mistake.

How chains actually form

Nobody sets out to build a four-hop redirect chain. It happens incrementally: a page moves from /old-page to /new-page with a redirect. Eighteen months later, /new-page gets renamed again to /newer-page, with a fresh redirect from /new-page. Nobody goes back and updates the original redirect from /old-page — it still points to /new-page, which now itself redirects onward. Repeat this pattern a few times across a site's history, especially through a URL structure change, a CMS migration, or a rebrand, and chains of three or more hops become common without any single change being the obvious culprit.

What it actually costs

Each hop in a chain adds a full round-trip to the browser's connection to your server before the actual page starts loading — for a visitor, this is directly additive latency, and it compounds with everything else already contributing to page load time. For search engines, most will still follow a handful of redirect hops, but the tolerance isn't infinite, and each additional hop is a place where a crawler might stop following, deprioritize the crawl, or dilute how much of the original URL's accumulated authority carries through to the final destination — the exact thing a redirect, like a canonical tag, was meant to preserve in the first place.

Finding and fixing them

The fix is almost always the same once you've found a chain: point the original URL directly at the final destination, collapsing three hops into one. This requires actually knowing your chains exist, which means periodically checking — a crawl of your own redirect rules, or a check of the URLs that show up in Search Console's redirect reporting, following each one through to see how many hops it actually takes before landing. The same crawl that catches broken links is where redirect chains tend to surface.

A practical rule going forward: any time you set up a new redirect, take thirty seconds to check whether anything else already redirects to the URL you're redirecting from. If so, update that earlier redirect to point straight to the new final destination instead of layering another hop on top. It's a small habit that prevents the exact accumulation that makes chains a "we didn't notice this happening" problem instead of a deliberate one.