Redirect Chain: When URLs Bounce Through Too Many Hops
A redirect chain sends crawlers through several hops before reaching the final URL. Learn why that costs you and how to flatten it into one redirect.
A redirect chain is a sequence where URL A redirects to B, which redirects to C, and so on, instead of A pointing straight at the final page.
What a Redirect Chain Does
Chains usually form over time as URLs get moved more than once, with each move adding another redirect on top of the old one.
Why Redirect Chains Matter
- They waste crawl budget on unnecessary hops.
- Each hop can dilute a little link equity.
- They add latency for real visitors.
- They raise the chance of a broken link or a loop.
How Chains Form
- Migrating a site more than once without updating existing rules.
- Redirecting a broken URL to another URL that also redirects.
- HTTP to HTTPS and www handling across multiple layers.
How to Flatten a Chain
- Run a crawl to map every chain and its final destination.
- Rewrite each rule so the first URL points straight at the final URL.
- Update internal links to skip the redirects entirely.
- Re-crawl to confirm the chains are gone.
The change: a blog moves from /old-blog to /blog, then from /blog to /guides.
The setup: the old URL now redirects to /blog, which redirects to /guides.
The reading: crawlers walk two hops to reach the final page.
Why it works better: pointing /old-blog straight at /guides cuts the chain to one hop.
Quick Tip
When you add a redirect, always point it at the final URL, never at another redirect. That one habit prevents most chains.
Frequently Asked Questions
Redirect Chains, Bottom Line
Redirect chains are silent leaks of crawl budget and link equity.
Flatten every chain so each URL reaches its destination in one hop.