A redirect chain occurs when a URL redirects to another URL, which redirects to yet another URL, creating multiple hops before the final destination. Each hop adds 50-500ms of page load latency, leaks a fraction of link equity, and consumes crawl budget. Google's crawler stops following chains after 5 hops — URLs requiring more are effectively uncrawlable.
Redirect chains are rarely created intentionally. They accumulate incrementally — one redirect for http to https, another for a slug change, a third for a domain migration. No single engineer creates a chain, but after enough site changes, chains become the default state of a site's redirect infrastructure.
What is a redirect chain?
A redirect chain is any sequence where getting from URL A to the final destination requires passing through one or more intermediate URLs. A direct redirect looks like this:
/old-page/→/new-page/ (301)
A redirect chain looks like this:
http://example.com/old-slug/
→ https://example.com/old-slug/ (301 — http to https)
→ https://example.com/new-slug/ (301 — slug change)
→ https://www.example.com/new-slug/ (301 — www canonicalisation)
200 OK (final destination)
Google's John Mueller has confirmed that Googlebot follows up to 5 redirects before stopping. An Ahrefs study of 10 million domains found that 17% had redirect chains affecting important pages — a significant prevalence for something that damages rankings silently.
Google states that 301 redirects pass PageRank, but the documentation also notes that "a long redirect chain is problematic." Practical audits consistently show that URLs at the end of 3+ hop chains rank below equivalent pages reached in one redirect — even with identical content and backlinks.
Why do redirect chains matter for SEO?
Four measurable consequences of redirect chains:
- Link equity dilution. Each redirect hop passes slightly less authority than a direct redirect. A backlink to your original URL that has to traverse 3 hops delivers less PageRank to the final destination than a direct redirect would. At scale, across hundreds of pages, this accumulates into a meaningful ranking disadvantage.
- Page load latency. Each redirect requires a separate HTTP request-response cycle. Each cycle adds 50-500ms. A 3-hop chain adds 150ms-1,500ms before the page even begins loading — enough to measurably increase bounce rate on mobile.
- Crawl budget waste. Google allocates a crawl budget to each site based on authority and server capacity. Every unnecessary redirect hop consumes budget that could be spent crawling actual content. Sites with hundreds of chains may see important new pages crawled less frequently.
- Googlebot crawl cutoff. After 5 hops, Googlebot stops following and does not index the destination URL. Any URL requiring 6+ redirects is effectively invisible to Google.
How redirect chains accumulate over time
Chains rarely appear in a single deployment. The pattern is consistent across sites:
- Site launches on http — no redirects
- SSL certificate added — all http URLs redirect to https (1 hop)
- URL slugs restructured for SEO — old https slugs redirect to new https slugs (2 hops from original)
- Domain migrated — old domain redirects to new domain (3 hops from original)
- New content architecture — categories restructured (4 hops from original)
At each step, a developer or SEO sets up the current redirect correctly. No one updates the original redirects. The chain grows one hop at a time.
Redirect chain vs. redirect loop — what's the difference?
| Issue | What happens | Effect on crawlers | Effect on users |
|---|---|---|---|
| Redirect chain | A → B → C → D (reaches destination eventually) | Equity dilution, budget waste | Latency, frustration on slow connections |
| Redirect loop | A → B → A (never reaches destination) | URL flagged as inaccessible | Browser error: "Too many redirects" |
| Single redirect | A → B (correct) | Full equity passed | Minimal latency (one round trip) |
Real redirect chain examples
Example 1 — Real estate blog, ranking recovery
A real estate blog with 230 backlinks was ranking at position 8 for its target keyword. An audit revealed the blog post URL was at the end of a 3-hop chain: http original → https → new slug → www canonical. After consolidating all three redirects into a single direct 301 from the original URL to the current www canonical URL, the page moved from position 8 to position 3 within 6 weeks. The backlinks were effectively carrying less authority through the chain than they should have been.
Example 2 — SaaS blog, CMS migration
A SaaS company migrating from WordPress to a headless CMS discovered that 340 of its 800 blog posts were in redirect chains averaging 2.8 hops. Googlebot was spending the majority of its crawl budget on redirect resolution rather than new content. After flattening all chains to direct redirects and updating internal links, Googlebot's crawl efficiency improved enough that the company's 30 new posts per month were being indexed within 48 hours versus the previous 10-14 day average.
Redirect chain vs. 301 redirect — the core difference
A 301 redirect is a tool. A redirect chain is what happens when you use that tool badly — or rather, when the accumulated use of that tool over time creates unnecessary complexity.
Correct: single 301 redirect
- Old URL → Final URL in one hop
- Full link equity passed
- One HTTP request round trip
- Googlebot resolves in milliseconds
- All backlinks credited to final URL
Problem: redirect chain
- Old URL → Intermediate 1 → Intermediate 2 → Final URL
- Equity leaks at each hop
- Multiple HTTP request round trips
- Googlebot uses crawl budget on resolution
- Backlink authority partially absorbed by intermediaries
6 best practices to prevent and fix redirect chains
- Audit redirects before every site migration. Export your full redirect map before changing URL structures, CMS platforms, or domains. Identify all existing chains and flatten them as part of the migration, not after.
- Always redirect to the final destination. When setting up a new redirect, check whether the destination URL already has a redirect on it. If so, skip the intermediary and point directly to the true final URL.
- Update internal links alongside redirects. A redirect is a temporary fix for an old URL. The right long-term fix is updating internal links to point directly to the new URL, which also eliminates one path that leads through a potential chain.
- Run a redirect crawl quarterly. Use Screaming Frog, Ahrefs Site Audit, or SEMrush monthly for high-traffic sites, quarterly for smaller ones. Chains are easier to fix when caught at 2 hops than at 5.
- Prioritise fixes by backlink count, not page count. A single page with 500 backlinks in a 3-hop chain is worth fixing before 100 pages with no backlinks. Run your redirect chain report against your backlink data and sort by inbound link count.
- Document your redirect map as a living asset. Maintain a spreadsheet or database of all active redirects. Every new redirect gets logged. Before adding a redirect, check if the destination already redirects somewhere. This single habit prevents most chain accumulation.
The most common fix error: updating redirect B → C to redirect B → D (the final destination), while leaving redirect A → B untouched. The chain is now A → B → D (still 2 hops). The correct fix is to update A → D directly, so all inbound traffic to A reaches D in one hop. Always work from the source, not the middle.
Common redirect chain mistakes to avoid
- Fixing the most recent redirect instead of the originating one. Shortening B → C → D to B → D still leaves A → B → D as a 2-hop chain. Fix from A.
- Not updating external links after fixing chains. If a high-authority site links to your old URL, even a perfectly configured single redirect still requires one round trip. Reach out to update high-value external links to the final URL.
- Treating redirect crawl results as a one-time project. Redirect chains return. New content, new CMS plugins, new marketing campaigns — each can introduce chains. Schedule quarterly audits.
- Confusing chains with loops. A redirect loop (A → B → A) is a different issue requiring a different fix. Loops need investigation of the rules creating the circular reference, not just redirect consolidation.
- Neglecting mobile redirect chains. Some sites serve separate mobile URLs via redirects (m.example.com). Mobile redirect chains are just as damaging to Core Web Vitals on mobile as desktop chains — and harder to spot if your audit tool crawls only desktop.
Frequently asked questions
Yes. Google states that 301 redirects pass PageRank, but practical testing and Google's own documentation confirm that authority diminishes at each hop in a chain. A 3-hop chain loses measurably more equity than a direct redirect to the same final destination.
One redirect is ideal. Two is temporarily acceptable during migrations. Three or more constitutes a chain that should be consolidated. Google's crawler, Googlebot, stops following a redirect chain after 5 hops — meaning any URL requiring 6 or more redirects to resolve is effectively uncrawlable.
Use Screaming Frog's SEO Spider (free for up to 500 URLs), Ahrefs Site Audit, or SEMrush Site Audit. All three report redirect chains as issues. In Screaming Frog, look under Reports, then Redirects, then Redirect Chains. In Ahrefs, check the Issues tab for "3xx redirect chains."
Prioritise by impact. Fix chains on your highest-traffic pages and pages with the most inbound backlinks first — those are the pages where link equity loss is most damaging. Low-traffic pages with no backlinks are lower priority. Use crawl data to sort by organic traffic and inbound links.
Redirect chains accumulate incrementally over time. A site migrates from http to https (adds one redirect), then changes URL slugs (adds a second), then migrates to a new domain (adds a third). No single change creates a chain — they build up through multiple site changes without anyone updating the originating redirects.
Related glossary terms
Sources
