What Is a Redirect Chain?
A redirect chain exists whenever a URL does not resolve directly to its final destination. Instead of A → final, you get A → B → final, or worse, A → B → C → D → final. Each step is an additional HTTP round-trip that every crawler and browser must complete.
Redirect chains most commonly accumulate during site migrations. URL A was redirected to URL B during a first migration. Later, URL B was redirected to URL C during a second migration. Nobody updated URL A to point directly to URL C, so the chain grew by one hop. Repeat this pattern over several years and chains of five or six hops are not unusual.
A single redirect (a redirect loop excepted) is not a chain — it is simply a redirect. The problem arises at two or more sequential redirects, though even a two-hop chain causes measurable damage at scale.
- Two or more sequential HTTP redirects before reaching the final URL constitute a chain
- Chains most often form during repeated site migrations where old redirects are not updated
- Chains grow silently — each migration adds hops without fixing previous ones
How Redirect Chains Affect SEO
Each redirect hop consumes a portion of your crawl budget. Googlebot allocates a finite number of requests per day to your domain. If significant portions of those requests are spent following chains rather than discovering new content, you reduce the share of your site that gets crawled.
Upload your Screaming Frog CSV — free, instant, nothing stored.
See your internal link equity in 30 seconds →Link equity also bleeds at each hop. While Google has said that 301 redirects pass PageRank, the amount passed through a chain of three or more redirects is meaningfully lower than a direct link. External backlinks pointing to a chain starting-point URL lose equity at every intermediate hop.
Internal links are the compounding factor. If your site has 10,000 internal links pointing to URL A, and URL A redirects through a three-hop chain, every one of those 10,000 links is wasting equity and crawl budget simultaneously. Fixing the internal links to point directly to the final URL is an immediate, high-leverage fix.
- Each hop consumes a crawl budget request — chains on popular pages waste significant crawl allocation
- Link equity leaks at each redirect step, reducing PageRank delivered to the final URL
- Internal links pointing into chains multiply the damage across your entire link graph
How to Find Redirect Chains
Screaming Frog's redirect chain report identifies all chains of three or more hops by default. Run a full crawl and export the redirect chains report to CSV. This gives you the starting URL, each intermediate URL, the final destination, and the hop count.
Upload this export to LinkJuice alongside your All Inlinks export. LinkJuice will cross-reference which of your internal links are currently pointing to chain-start URLs — showing you not just where chains exist, but exactly which internal links need to be updated to bypass them.
Prioritize chains by the number of internal links pointing into them. A three-hop chain with 500 internal links pointing to it is far more damaging than a two-hop chain with 3 links.
- Screaming Frog redirect chain report — exports all chains of 3+ hops with hop counts
- Cross-reference with your inlinks report to see which internal links feed into each chain
- Prioritize by inbound link volume — fix chains with the most internal links first
How to Fix Redirect Chains
The permanent fix is to update every redirect in the chain to point directly to the final destination URL. URL A should redirect directly to URL C, skipping URL B entirely. Update the redirect on the server or CMS, not just the internal links.
After updating the redirects, update all internal links that point to the old starting URLs to point directly to the final destinations. This eliminates the crawl and equity cost entirely — instead of a redirect, Googlebot follows a clean direct link.
For large sites with thousands of affected internal links, prioritize updating links on high-PageRank pages first. Those links pass the most equity, so fixing them recovers the most value immediately.
- Update redirects server-side so URL A points directly to the final destination URL
- Update all internal links from chain-start URLs to the final destination URL
- Prioritize by page authority — fix redirects fed by your highest-PageRank pages first
Upload your Screaming Frog CSV — free, instant, nothing stored.
Find your site's weakest links before Google does →Frequently Asked Questions
- What is a redirect chain in SEO?
- A redirect chain is a sequence of two or more HTTP redirects that must be followed before reaching the final destination URL. For example: /old-page → /interim-page → /new-page. Each hop wastes crawl budget and leaks link equity.
- How many redirects are too many?
- Any chain of two or more redirects is worth fixing. Google may stop following chains after approximately five hops, effectively making the final destination uncrawlable. Even a two-hop chain bleeds measurable equity at scale.
- Do redirect chains hurt SEO?
- Yes. Redirect chains waste crawl budget, leak PageRank, and add server latency. On large sites where chains are fed by thousands of internal links, the cumulative damage to crawl coverage and equity distribution is significant.
- How do I fix redirect chains quickly?
- Export Screaming Frog's redirect chain report, then update each chain to point directly to its final destination URL. Then update all internal links pointing to chain-starting URLs to use the final URL directly. LinkJuice identifies exactly which internal links need updating.
Find Internal Links Feeding Redirect Chains
Upload your Screaming Frog CSV and see exactly which internal links are pointing to redirect chain URLs — so you can fix them in one pass.
Upload crawl & start🔒 Runs in your browser. Your data never leaves your machine. No email needed.