One redirect is harmless — a single detour sign saying "moved over here." But when that detour sign points to another detour sign, which points to another, which finally reaches the page? That's a redirect chain, and it's one of those quiet technical problems that costs you rankings, crawl budget, and visitors without ever throwing an error.
Nobody builds redirect chains on purpose. They accumulate: a migration here, an HTTPS switch there, a www consolidation two years later, a plugin adding its own redirect on top — until a URL that once resolved in one hop bounces through four.
Say your site moved to HTTPS years ago, then consolidated www and non-www, then redesigned with new URLs. An old backlink might now resolve like this:
http://www.example.com/old-page → 301 → https://www.example.com/old-pagehttps://www.example.com/old-page → 301 → https://example.com/old-pagehttps://example.com/old-page → 301 → https://example.com/new-pageThree hops for one page — three full extra HTTP requests between the browser (or Googlebot) and your server.
The ideal version is one hop:
http://www.example.com/old-page → 301 → https://example.com/new-page
Same destination, no middlemen. That single hop is the goal of everything below.
Chains are accidents of history. The usual suspects:
Stacked migrations. Each migration adds a layer: one migration pointed old URLs at that era's structure, and the next redesign pointed those URLs at the new structure — instead of pointing the originals straight at the final destination. A few migrations deep, chains run five hops long.
HTTPS and www rules applied separately. The most common chain on the modern web. One rule forces HTTP → HTTPS; another forces www → non-www. An old http://www. link takes two hops before reaching your content rules. Combine both into a single rule and the chain disappears.
Trailing-slash and case fixes. A rule adding trailing slashes, plus one lowercasing URLs, plus the migration redirect — three hops for what should be one.
Plugin and platform layers. Redirect plugins, CDN page rules, and server configs can fire in sequence. Each layer is correct alone; together they chain.
Shorteners and tracking links. Fine for marketing — but keep this pattern away from your core site URLs.
Crawl budget. Every hop is a separate fetch for Googlebot. Budget spent bouncing through redirects is budget not spent indexing your content — and Google may stop following after several hops, leaving the final page uncrawled.
Link equity dilution. Each hop is another chance for signal loss. A backlink passing through four redirects is worth less than the same link pointing directly at the final page.
Speed. Every hop adds a network round trip, commonly 100–300ms. Three extra hops on mobile can add a full second before the page starts loading. Our guide on 301 vs 302 redirects covers choosing the right redirect type; chains are the next layer of the same problem.
Start with the URLs that matter most — homepage, top landing pages, and any URL with valuable backlinks:
Pay special attention to URLs with backlinks: you can't control where others link, but you can make the first hop land directly on the final page.
Every old URL should point directly at the final destination in a single hop.
Before (chained): /old-page → 301 → /2019-page → 301 → /new-page
After (flat): /old-page → 301 → /new-page, and /2019-page → 301 → /new-page
In practice:
Don't delete the intermediate redirects and leave them 404ing — external links still point there. Keep each alive as a direct single-hop 301.
More than one hop is more than you need. Two hops is common and tolerable, but three or more wastes crawl budget, dilutes equity, and adds noticeable latency. Google may stop following after around five hops, so anything near that actively harms crawlability.
Indirectly, yes. Chains slow page loads (a ranking factor), waste crawl budget (pages get crawled less often), and dilute link equity to the final page. No single hop is catastrophic, but the compound effect across a site is real and measurable.
A chain eventually arrives — A → B → C → final page. A loop never does: A → B → A → B…, and the browser quits with a "too many redirects" error. Loops are emergencies; chains are slow leaks.
Yes — and they're the easiest to fix. If your navigation or content links to URLs that redirect, update them to point directly at the final URLs. Unlike external backlinks, you control internal links completely.
Keep the rules, flatten the chaining. Old URLs may carry backlinks for years, so the 301s should stay indefinitely — but each old URL gets its own direct single-hop rule to the final destination.
Redirect chains never announce themselves. Pages still load, visitors still arrive, everything looks fine — while crawl budget, link equity, and load time leak at every hop. Find the chains, flatten each into a single direct 301, and keep them flat with regular audits. It's among the highest-ROI technical SEO work you can do, because it recovers value you've already earned.
Check your URLs for redirect chains free with our WWW Redirect Checker — paste any URL and see every hop between it and the final page.
.jpg)
