Redirect Chains Explained: Why Too Many Hops Hurt SEO
A redirect chain sends visitors and crawlers through several URLs before they reach the final page. Here's why chains hurt, how to find them and how to fix them.
Key takeaways
- A redirect chain is any URL that redirects more than once before reaching the final page.
- Chains slow pages, waste crawl budget and add risk of breaking.
- Googlebot follows up to about 10 redirect hops, but each hop adds delay and points of failure.
- Fix chains by pointing every redirect, and every internal link, directly at the final URL.
A redirect chain happens when URL A redirects to URL B, which redirects to URL C, and so on before reaching the final page. A redirect loop happens when the redirects send users back to an earlier URL, so the page never loads.
How chains happen
Chains usually build up over years:
- You moved
/services/to/our-services/(redirect 1) - Then moved HTTP to HTTPS (redirect 2)
- Then switched from non-www to www (redirect 3)
- Then renamed
/our-services/to/seo-services/(redirect 4)
A visitor clicking an old link now passes through four hops.
Why chains hurt
- Slower pages: each hop is another request, especially noticeable on mobile
- Wasted crawl budget: Googlebot spends requests following hops (see crawl budget)
- Risk of breakage: each hop is another thing that can break
- Crawl limits: Googlebot follows up to about 10 hops before giving up on a URL
Google has said 301 redirects pass ranking signals, but chains still add delay and complexity, and internal links pointing at redirected URLs are an unnecessary waste.
How to find redirect chains
- A site crawler: most crawlers report redirect chains and loops, with every hop listed
- Browser developer tools: the Network tab shows each redirect when you load a URL
- Search Console: the Page indexing report lists “Page with redirect” and “Redirect error”
How to fix them
- Update redirect rules so every old URL points directly to the final destination (A → D, B → D, C → D).
- Update internal links to point straight to the final URL, so internal navigation never triggers a redirect.
- Update canonical tags and sitemaps to use final URLs only.
- Fix loops by finding the conflicting rules (often between a plugin and server config).
- Ask important backlink sources to update their links where practical.
Best practice for future changes
- When changing URLs, check whether the old URL is already the target of redirects, and update those too
- Keep a redirect map (old URL → new URL) for every migration
- Avoid changing URLs unless there’s a clear benefit
Redirects are part of our technical SEO audit. Related: how to fix broken links.