What Is Redirect Chain?
Written byFlavio Amiel Founder, Roborank
A redirect chain is a sequence of two or more redirects that a request passes through before reaching its final destination — for example URL A redirects to B, which redirects to C. Each extra hop adds latency for users and consumes crawler budget, and Googlebot follows only a limited number of hops before giving up.
- Googlebot follows up to 10 hops in a redirect chain; if it does not reach content within that limit, Search Console flags a redirect error and the page is excluded from indexing.
- Google advises redirecting to the final destination directly, and when that is impossible, keeping the chain to ideally no more than 3 redirects and fewer than 5.
- Chained redirects add latency for users, and not all user agents and browsers support long chains.
- Chains commonly accumulate over time — an HTTP-to-HTTPS hop, then a non-www-to-www hop, then an old-path-to-new-path hop can silently stack into a three-link chain.
How a Redirect Chain Works
A redirect chain is what you get when the answer to “where does this URL go?” is itself another redirect. A client requests URL A, the server responds with a redirect to URL B, the client requests B, and the server responds with yet another redirect to URL C, which finally returns real content. Each arrow in that sequence is one hop. A single redirect (A to B) is not a chain; a chain begins at two hops and grows from there.
Every hop is a full round trip. The browser or crawler has to issue a new request, wait for the response, read the Location header, and repeat. For a human visitor that means measurable added latency, especially on mobile networks where each connection carries real cost. For a search engine it means spending crawl budget on intermediate URLs that were never the intended destination. The links in the chain can be any redirect type — 301s, 302s, or a mix — and the mix matters, because a permanent-signal chain and a temporary-signal chain resolve differently for canonicalization.
There is also a hard ceiling. Google Search Central states that Googlebot follows up to 10 hops in a chain of redirects. If the crawler does not receive real content within those 10 hops, Google Search Console records a redirect error and the page is excluded from indexing. So a chain that grows long enough stops being merely inefficient and becomes a page that simply cannot get indexed.
How Chains Form and What Google Recommends
Chains rarely start life as chains. They accumulate as a site evolves, with each new redirect rule layered on top of the last:
- An HTTP-to-HTTPS redirect is added during a security migration.
- A non-www to www (or the reverse) canonicalization rule is added later.
- An old-path to new-path rule is added during a URL restructure.
An inbound link to the original HTTP, non-www, old-path URL now has to traverse all three rules in sequence to reach the live page — a three-hop chain that no one deliberately built. Multiply that across an old site’s link profile and the waste compounds.
Google’s guidance is direct. In its site-move documentation it advises redirecting to the final destination directly, and when that is not possible, keeping the number of redirects in the chain low — ideally no more than 3 and fewer than 5. The stated reasons are the two costs above: chaining redirects adds latency for users, and not all user agents and browsers support long redirect chains. The 10-hop figure is a technical failure point, not a target; the practical target is one hop.
Example of a Redirect Chain
Google’s own site-move documentation supplies the canonical illustration: a chain written as Page 1 > Page 2 > Page 3. Consider a concrete version. A blog published years ago links to http://example.com/old-post. Since then the site has moved to HTTPS, standardized on the www host, and restructured its blog URLs. A visitor clicking that old link now travels:
http://example.com/old-post— 301 to the HTTPS versionhttps://example.com/old-post— 301 to the www hosthttps://www.example.com/old-post— 301 to the new pathhttps://www.example.com/blog/new-post— 200 OK, the real page
That is a three-hop chain (four URLs, three redirects), comfortably inside Googlebot’s 10-hop limit but already past the “ideally no more than 3, fewer than 5” comfort zone Google describes, and costing every visitor and crawler three extra round trips. The fix is to add or rewrite a single rule so the original http://example.com/old-post points directly to https://www.example.com/blog/new-post in one hop. The intermediate rules can stay in place for requests that legitimately start at those URLs, but no single request should ever have to climb the whole staircase. Collapsing chains to one hop is a standard, high-value step in any site migration checklist.
Redirect chains are almost never designed; they accrete. Someone adds an HTTP-to-HTTPS redirect one year, a www canonicalization the next, and a URL restructure after that, and suddenly a single old link drags a crawler through three hops to reach the real page. Each layer was reasonable on its own, which is exactly why nobody notices the pileup. The fix I recommend is boring and effective: audit your redirect rules periodically and rewrite every chain so the original URL points straight at the final destination in one hop. You don’t remove the intermediate rules for their own direct traffic — you just make sure no request has to walk the whole staircase.
Frequently Asked Questions
Are redirect chains bad for SEO?
How many redirects can Googlebot follow?
How do I fix a redirect chain?
What is the difference between a redirect chain and a redirect loop?
The Bottom Line
A redirect chain is what happens when a request has to hop through several intermediate URLs before it lands on a live page. It still works, but every extra link costs load time for visitors and crawl budget for search engines, and past 10 hops Googlebot simply stops and flags the page. The remedy is to point the very first URL at the very last one, collapsing the staircase into a single step.
Sources
- Site moves with URL changes (redirect chains and hops) — Google Search Central
- How Google handles redirects for Search — Google Search Central
Roborank crawls every redirect path on your site and reports the multi-hop chains draining crawl budget — with the single-hop rewrite for each one.
Find your redirect chains →Rank & Cash — the weekly SEO breakdown
One practical teardown a week on ranking in search and getting cited by AI. No fluff.