Quick answer: A redirect chain happens when one URL redirects to a second URL, which redirects again before a browser or crawler reaches the final page. Each extra hop adds load time and wastes crawl budget, and Googlebot stops following after 10 hops.
A clean redirect is one hop: old URL sends you straight to the new URL. A redirect chain is what you get when nobody cleans up. Page A redirects to B, B redirects to C, C finally serves the content. The visitor still lands in the right place, so nothing looks broken, which is exactly why chains sit on sites for years.
They build up in a predictable way. A 2021 migration adds one rule. A 2023 category rename adds another on top. Then HTTP moves to HTTPS, then non-www moves to www, and each of those is written as its own rule instead of one. Now a single old blog URL takes four hops to resolve, and every internal link, backlink and ad click pointing at it pays that toll.
Why redirect chains matter
First, kill the myth. Redirect chains do not drain your link equity per hop. Google’s Gary Illyes settled this publicly in July 2016 when he confirmed that 30x redirects no longer lose PageRank, which retired the old “you lose 15% per redirect” rule of thumb. If someone is still selling you a chain cleanup on the promise of recovering lost authority, they are quoting advice from over a decade ago.
The real costs are speed, crawl efficiency and signal clarity. Every hop is a full round trip across the network before any content starts loading, and Google’s own Lighthouse documentation notes that this can delay the resource by hundreds of milliseconds, with a page failing the audit once it has two or more redirects. That delay lands on Time to First Byte and Largest Contentful Paint, before your hero image has even been requested.
There is also a hard ceiling. Googlebot follows up to 10 redirect hops, and if it does not reach real content within those hops, Search Console reports a redirect error and the page is left out of the index. In practice Google follows around 5 hops in a single crawl and picks up where it left off next time, so long chains do not kill a page outright, they just slow its discovery down (Ahrefs).
For a paid account, the cost is more direct. You are paying by the click, and every hop happens after the click and before the landing page renders. Worse, a redirect rule that is not written to carry the query string will strip your UTM parameters and click IDs on the way through, so the visit shows up as direct or organic in GA4 and the campaign that paid for it gets no credit. A redirect chain on a paid landing page slows down traffic you already bought and can break the attribution you use to decide where the next rupee goes.
The newer problem is AI search. Answer engines crawl on much tighter budgets than Google does, and Vercel’s analysis of AI crawler traffic found that ChatGPT’s crawler spent 14.36% of its fetches following redirects and 34.82% hitting 404s (Vercel, The rise of the AI crawler). Roughly half of that bot’s effort went on detours and dead ends instead of content. The same study found that none of the major AI crawlers execute JavaScript, so a JavaScript or meta refresh redirect that works fine for a human is a dead end for GPTBot, ClaudeBot and PerplexityBot. If you care about being cited in AI answers, read our take on GEO vs SEO.
Redirect chain vs single redirect vs redirect loop
These three get lumped together. They are not the same problem and they do not carry the same urgency.
| Attribute | Single redirect | Redirect chain | Redirect loop |
|---|---|---|---|
| What happens | A goes to B, done | A goes to B goes to C goes to D | A goes to B goes back to A, forever |
| Does the user reach the page? | Yes, immediately | Yes, slower | No, the browser gives up |
| What the user sees | The page | The page, after a delay | ERR_TOO_MANY_REDIRECTS |
| Googlebot behaviour | Follows and indexes the target | Follows up to 10 hops, wastes crawl budget | Abandons the URL, drops it from the index |
| Severity | Healthy, this is correct use | Medium, fix in batches | Critical, fix today |
| Fix | Nothing to fix | Point the first URL straight at the last | Break the cycle, pick one canonical URL |
A chain costs you speed and crawl efficiency; a loop costs you the page entirely. If an audit surfaces both, fix every loop before you touch a single chain.
How to find and fix redirect chains
Finding them takes an afternoon. The fixing is the part people skip.
- Check a single URL fast. Run curl -IL https://yoursite.in/old-page in a terminal and count the 301 and 302 responses before you see a 200. One 3xx is fine. Three means you have work to do.
- Crawl the whole site. In Screaming Frog, crawl the site or upload a URL list, then open Reports, Redirects, Redirect Chains. It maps every chain, its hop count, and flags loops separately. Turn on Always Follow Redirects under Configuration first, or chains that leave your start folder get missed.
- Cross-check Search Console. The Pages report flags “Page with redirect” and “Redirect error”. A redirect error usually means a loop or a chain that ran past Googlebot’s patience.
- Flatten the rules. Rewrite A goes to B goes to C goes to D as A goes to D and B goes to D. Keep the intermediate rules pointing at the final URL, do not delete them, because old backlinks still hit those middle URLs.
- Fix the source of the hop. Update internal links, navigation, XML sitemaps, canonical tags and hreflang to the final URL. A redirect you never trigger costs nothing.
- Audit your ad landing pages separately. Paste every live Google, Meta and LinkedIn final URL into a crawler and confirm each returns 200 with the query string intact. This is the highest-value list on the site because it is the one you pay to send traffic to.
- Combine the housekeeping rules. HTTP to HTTPS, non-www to www and trailing slash should resolve in one hop, not three stacked rules.
Worked example, crawl budget on a mid-size store:
- Site with 60,000 URLs, of which 8,000 still redirect from old category and product paths.
- Average chain depth after three migrations: 3 hops.
- Requests spent reaching those 8,000 destinations: 8,000 x 3 = 24,000.
- After flattening to one hop each: 8,000.
- Requests freed up for actual content: 16,000.
On a 200-page brochure site, that same fix is worth almost nothing, and we will tell you so rather than bill for it. On a large catalogue with new SKUs going live weekly, it is the difference between new products getting indexed in days and in weeks.
Now the paid side. Say you spend ₹2,00,000 a month on Google Ads at a ₹40 CPC, which is 5,000 clicks, converting at 2% into 100 leads at a CPA of ₹2,000. Your landing page sits behind 3 hops. If clearing that delay lifts conversion rate even to 2.1%, you get 105 leads for the same spend and your CPA drops to roughly ₹1,905. That 0.1% is an assumption, not a benchmark, so treat it as a reason to run the test on your own account rather than a promise. Our landing page checklist covers what else to fix once the redirect is gone.
Common mistakes
- Stacking a new redirect rule on every migration. Each replatform adds a layer instead of rewriting the old rules to point at the new final URL. Three migrations later you have four-hop chains nobody remembers creating. Every time you add redirect rules, re-point the existing ones at the new destination in the same release.
- Fixing the redirect and leaving the links. Internal links, menus, sitemaps and canonical tags keep pointing at the old URL, so the chain fires on every crawl and every click. Update the links and most chains stop being triggered at all.
- Mixing 302s into a permanent chain. A 301 followed by a 302 sends Google a contradictory message about which URL should be canonical. Permanent moves get 301 or 308 the whole way through, with no temporary hop in the middle.
- Using JavaScript or meta refresh redirects. They are slower, they send a weaker signal than a server-side 3xx, and AI crawlers that do not run JavaScript never reach the destination at all. Use a server-side redirect wherever you can.
- Ignoring ad landing pages. SEO audits crawl the site’s internal link graph, and paid final URLs with tracking parameters often are not in it. Chains and stripped UTMs on those URLs go unnoticed for months while you keep paying for the clicks.
Frequently asked questions
What is a redirect chain?
A redirect chain is a sequence in which one URL redirects to a second URL, which redirects to a third, before the browser or crawler reaches the final page. The visitor still arrives at the right content, but every extra hop adds a network round trip and consumes crawl resources.
How many redirects in a chain is too many?
One hop is the target and two is acceptable. Googlebot follows up to 10 redirect hops before reporting a redirect error, but Google recommends redirecting straight to the final destination, and Lighthouse fails a page once it has two or more redirects. Anything past 3 hops should be on your fix list.
Do redirect chains lose link equity or PageRank?
No. Google’s Gary Illyes confirmed in 2016 that 30x redirects do not lose PageRank, so a chain does not dilute authority per hop the way older SEO advice claimed. The genuine costs are slower page loads, wasted crawl budget, and unclear canonical signals when redirect types are mixed.
What is the difference between a redirect chain and a redirect loop?
A redirect chain eventually reaches a working page, just slowly. A redirect loop never resolves because the URLs point back at each other, so the browser shows an ERR_TOO_MANY_REDIRECTS error and Google drops the URL from its index. Loops are urgent; chains are important but not an emergency.
How do I check for redirect chains on my website?
Run curl -IL on a single URL and count the 3xx responses before the 200. For a whole site, crawl it in Screaming Frog and open Reports, Redirects, Redirect Chains, which lists each chain, its hop count, and any loops. Google Search Console’s Pages report also flags redirect errors.
Do redirect chains affect AI search and ChatGPT citations?
Yes, indirectly. AI crawlers work on tighter budgets than Googlebot and none of the major ones execute JavaScript, so a JavaScript-based redirect is a dead end for them. Vercel’s crawler analysis found ChatGPT’s bot spent 14.36% of its fetches following redirects, effort that never reaches content worth citing.
How Uginix helps
Redirect chains usually surface during our technical audit, and we treat them by priority rather than by count: loops first, paid landing pages second, high-traffic organic URLs third, and the long tail only when the crawl numbers justify the dev time. Our SEO, GEO and analytics work checks that the URLs you actually spend money on resolve in one hop with tracking parameters intact, so your attribution stays honest. Not sure where your ad spend is leaking? That is exactly what our free growth audit finds.
Related terms
- 301 redirect: a permanent server-side redirect that tells search engines the new URL should be indexed in place of the old one.
- 302 redirect: a temporary redirect that keeps the original URL indexed, correct for short-term moves and wrong for permanent ones.
- Redirect loop: a closed chain where URLs redirect back to each other endlessly, making the content unreachable for users and crawlers.
- Crawl budget: the number of requests a search engine will spend on your site in a given period, which redirect hops consume without returning content.
- Canonical tag: the HTML signal that tells search engines which version of a URL is the preferred one to index.
Sources: Chrome for Developers, Lighthouse, Search Engine Land, Ahrefs, Screaming Frog, Vercel.