Technical

Redirect Chain

A redirect chain is when one URL redirects to another, which redirects to another, before finally landing on the destination page. Each extra hop slows the page, wastes crawl budget, and can leak ranking signals, so the goal is always a single direct redirect.

A clean redirect is one hop. Old URL points straight at the new URL, the user and the crawler arrive, done. A redirect chain is what happens when that simple move gets repeated and stacked over time. URL A redirects to B, but B was itself redirected to C, and C now points to D. Every visitor and every crawler has to walk that entire chain before they reach the page that actually exists. It works, technically, but it costs you on every front that matters.

Chains build up quietly. You migrate a site once and add redirects. You restructure URLs a year later and add more, pointing at the old redirected URLs instead of the live ones. Do that a few times and you have chains three and four hops deep that nobody planned and nobody is watching.

Why chains hurt

Speed: every hop is another round trip to the server, adding latency before the real page even starts to load.
Crawl budget: crawlers spend requests walking the chain instead of discovering and indexing your real content.
Signal loss: ranking equity can dissipate across hops, so the destination inherits less than a single redirect would pass.
Failure risk: the more links in the chain, the more chances one breaks and turns the whole path into a dead end.
Mobile pain: extra round trips hit hardest on slower mobile connections, where latency is already a problem.

bolt

Every redirect in a chain is a tax on speed and a leak in your ranking signals. The fix is almost always to flatten the chain to a single hop.

What a chain looks like versus the fix

Here is a three-hop chain, the kind that accumulates without anyone noticing.

/page-a/  ->  301  ->  /page-b/
/page-b/  ->  301  ->  /page-c/
/page-c/  ->  301  ->  /final-page/

And here is the same situation flattened. Instead of leaving the old hops pointing at intermediate URLs, you update every redirect to point directly at the final destination.

/page-a/  ->  301  ->  /final-page/
/page-b/  ->  301  ->  /final-page/
/page-c/  ->  301  ->  /final-page/

Now any entry point reaches the destination in a single hop. The user is faster, the crawler is happier, and the signals arrive with as little leakage as possible.

warningWATCH OUT

Watch for redirect loops, the worst version of a chain, where A points to B and B points back to A. That traps users and crawlers in an endless cycle and serves no page at all. Audit for loops every time you touch redirects.

How to find your chains

You cannot fix what you cannot see. A site crawler like Screaming Frog will flag redirect chains and loops directly, showing you the full hop sequence for each affected URL. Run a crawl after any migration or URL restructure, sort by redirects, and rewrite every chain so the first URL points straight at the last.

targetWhen you add a new redirect, check the target

The habit that prevents chains is simple. Before you create a redirect, confirm the URL you are pointing at is a live 200 page, not another redirect. If the target already redirects somewhere else, point your new redirect at that final destination instead. Build clean from the start and you never have to untangle a chain later.

One hop, always

A redirect chain forces users and crawlers through extra hops that cost speed, crawl budget, and ranking signals. Flatten every chain so the original URL points directly at the final destination, and audit for chains and loops after any URL change.

For the full playbook on moving URLs without losing rankings, read my guide on redirects and URL changes.

GO DEEPER

alt_route

Redirects

301s and canonicals, done right.

Want this handled by someone who has measured search for 20 years?

Work with me