Redirect Chains: What They Are and How to Fix Them

Find multi-hop redirects on your site · updated October 2026

A redirect chain is what happens when one old URL points at another old URL before finally reaching the live page — /post/2021-launch → /blog → /blog/launch → 200. One click, three round trips. Each hop was set up by someone who, usually, had no idea the other hops existed. Chains accumulate silently: every redesign, replatform, and HTTPS migration adds a layer. Here's what they cost and how to flatten them.

Why redirect chains hurt

Four costs, and they compound:

Latency. Every hop is a full extra request–response cycle before the browser even starts loading the real page. A two-hop redirect doubles that overhead, and mobile connections — where round trips are slower — pay the most.
Crawl budget. Search engine bots follow each hop separately and revisit each intermediate URL. On larger sites, chains and redirect loops quietly eat the budget that should be spent indexing new pages.
Signal propagation. When you consolidate URLs, crawlers pick up the change faster through a single 301 than through a stack of them. Chains also multiply breakage: remove or change one middle hop and every URL routing through it re-points or dies.
The failure mode that matters most: a chain that ends in a 404. The link passes through two or three hops and delivers the visitor to "page not found" — the worst outcome per unit of effort.

How to find redirect chains

Check a single URL first. The free redirect checker traces one address through every hop to its final destination — useful when you already suspect a specific link, an old campaign URL, or a competitor's moved page.

Then scan your site from the sitemap. Spot checks find nothing at scale: stale links hide in navigation templates, old blog posts, and legacy sidebars, and every page that repeats a stale link multiplies the problem. A sitemap-based scan visits each page it fetches, follows each link through its redirects, and reports where the first hop lands versus where the URL finally resolves:

The site scan reports each redirecting link as original → final destination with its status code, so multi-hop paths stand out — both endpoints are on one line, and anything between them is a hop you can delete.

How to fix redirect chains

Repoint internal links at the final destination. Most chains start here: a live page links to an old URL that redirects. Update the link itself and a hop disappears without touching the server.
Collapse the rules at the origin. Rewrite rules should send each old URL straight to its final home in a single 301 — one rule per old URL, pointing at the live page, never at another redirect.
Flatten stacked migrations. HTTP→HTTPS, www→apex, a domain move, a replatform — each adds a layer. A URL crossing all four is a four-hop chain by accident. Fold protocol and subdomain handling into one rule (or your host's edge) so path redirects only ever add one hop.
Fix chains ending in 404 first. They cost the most and take the same effort to repair as ones ending in 200. Point the old URL at the closest live equivalent — or let it 404 and remove the hops entirely.
Re-scan to verify. After collapsing, the same scan should report each former multi-hop path as a single redirect. That's the mechanical proof the cleanup worked — not "I think it's fixed."

Common pitfalls

Redirecting retired pages to the homepage. A soft 404: search engines treat it as a missing page wearing a 200, and visitors land somewhere that answers nothing they asked.
Mixing 302s into permanent moves. A temporary status mid-chain keeps the old URL alive in the index indefinitely. Permanent moves get 301 (or 308) end to end.
Legacy redirect tables nobody audits. After a replatform, old rules survive in .htaccess, nginx configs, or edge rules long after anyone remembers them. Multi-hop paths from three migrations ago are still in there — only an audit scan shows them.
Fixing one link and calling it done. The same stale URL usually appears in many places. Fix at the rule level or at every link; a one-off edit leaves the rest of the path intact.

Common questions

How many hops are acceptable? One. Crawlers will follow several, but each hop is latency for visitors and crawl spend for the index. If you can only fix some, prioritize paths longer than two hops.

Do multi-hop redirects lose link equity? Signals like PageRank pass through 301s and through multi-hop paths too — but slower, with more failure modes along the way. The equity argument for flattening is weaker than it used to be; the speed and crawl-budget arguments are not.

301 or 308? Both are permanent. 308 preserves the HTTP method (rarely needed for pages); 301 is the safe default every tool and crawler understands.

How long should redirects stay in place? As long as real traffic or links still arrive at the old URL — check server logs or Search Console. High-value old URLs (press links, bookmarks) are cheap to keep; dead ones are cleanup candidates.

Migrating a site and finding 404s at the same time? Work through the post-migration 404 checklist — redirect hygiene is step one. And if the problem is broader than redirects, start with the full guide to finding and fixing broken links.