What Is a Redirect Chain?
A redirect chain is a sequence of two or more consecutive redirects that a request must follow before it reaches a URL returning actual content.
A redirect chain is a sequence of two or more consecutive redirects that a request must follow before it reaches a URL returning actual content. One redirect is not a chain. A redirect loop is something else again: a loop never resolves, while a chain resolves eventually and quietly charges you for the trip.
Why redirect chains matter
Nobody builds a chain on purpose. A site moves from HTTP to HTTPS, drops the www prefix a year later, then restructures its URLs when the catalogue is rebuilt. Each change adds a rule and nobody retires the old ones. Three sensible decisions, taken years apart, produce a four-hop path to a single product page.
The cost lands in three places. Every hop is a round trip, so on a mobile connection the user waits longer before anything renders. Every hop is a separate crawler request, so a large site burns its crawl allocation resolving addresses instead of fetching pages. And every hop is one more rule that a future deploy can edit wrongly and break the entire path. Fix the chains on the URLs that still earn you real traffic before you touch the rest of the redirect map.
What happens at each hop
- The client requests URL A. The server answers with a 3xx status and a Location header naming URL B. No page content comes back at this point, only an instruction to go elsewhere.
- The client requests URL B. If B also answers with a 3xx, the process repeats against URL C. Each hop is a complete request and response cycle, and when a hop crosses hostnames it can carry a fresh connection cost too.
- Google counts the hops. Google Search follows up to 10 redirect hops. If no content arrives inside that limit, Search Console records a redirect error in the Page Indexing report and the destination never gets indexed.
- Google reads the target as a canonical signal. Permanent redirects are a strong signal for which URL should be canonical, and temporary ones are a weak signal. That distinction is why how temporary redirects are treated matters whenever a chain mixes the two types.
- The chain persists until someone edits it. Google may eventually learn the endpoint, but your server keeps serving the same path to every browser, every other crawler and every AI fetcher on every request.
Chain shape decides how much any of that matters. Length alone is a poor severity score, because a two-hop chain on a same-host path and a two-hop chain that mixes permanent with temporary redirects cause completely different problems.
| Chain shape | What it actually costs you |
|---|---|
| A to B, one hop, same host | Nothing meaningful. This is a redirect working as designed. |
| A to B to C, two hops | Extra latency per request. Worth tidying, rarely urgent. |
| Chain mixing permanent and temporary redirects | Muddled canonical signal, because the weakest hop colours the whole path. |
| Every hop crossing a different hostname | A new connection per hop, which is where user-facing delay accumulates. |
| More than 10 hops | Google stops. The final URL is never fetched, so it cannot be indexed. |
The blunt version
Redirect chains get sold as a link equity problem. They are mostly not one. Google’s long-standing guidance is that PageRank is not lost through 3xx redirects, and Google Search follows up to 10 hops before it gives up. A two-hop chain is therefore not a ranking emergency, and the tool that scored it red alongside your broken canonicals was counting, not diagnosing.
The real bill is crawl waste and latency. Say a catalogue with 60,000 product URLs where every product is reached through a two-hop chain. That is 120,000 crawler requests to fetch 60,000 pages, so half of everything the crawler does on your site returns no content at all. Add the second hop to a user’s page load and you have paid twice for the same page: once in crawl, once in speed.
So use the length as a triage rule, not a verdict. Under three hops on pages that already rank, leave it and spend the sprint elsewhere. Over five hops, or anywhere near the 10-hop limit, fix it that week, because the failure mode there is a page Google abandons. Chains stack up fastest during a move between website platforms, when a new URL structure gets layered on top of two older ones that nobody documented.
Example
Say a publisher migrated to HTTPS in one year and dropped www in the next. An old article URL now runs: http://www.example.com/post to https://www.example.com/post to https://example.com/post. Two hops, both permanent, both correct. Then editorial renames the article and the CMS adds a third rule pointing the old slug at the new one. Nothing is broken and nothing errors. But every external link earned across a decade now takes four requests to resolve, and the newsletter archive linking to those URLs loads visibly slower on mobile. The fix is not to remove rules. It is to rewrite the first rule so it points straight at the final URL, and leave the others in place for anyone arriving mid-chain.
FAQ
How many redirects in a row is too many?
Google Search follows up to 10 hops, so that is the hard ceiling. Practically, aim for one hop and accept two. Past three you are adding user-facing delay for no benefit, and you are one careless deploy away from crossing a limit that stops the page being indexed at all.
Do redirect chains lose link equity?
Google’s guidance has for years been that PageRank is not lost through 3xx redirects. Treat equity loss as the wrong reason to fix a chain. The defensible reasons are crawl efficiency on large sites, page speed for real users, and the fragility of a path that depends on several rules staying correct.
How do I find the chains on my site?
Crawl your own site with a tool that reports the full redirect path rather than the final status, then crawl your XML sitemap and your top landing pages separately. Server access logs show the same chains from the crawler’s side, including hops that your internal links no longer point at.
Related terms
- 302 Redirect — the temporary status code that turns a tidy chain into an ambiguous canonical signal.
- Manual Action — a real penalty with a Search Console notice, which a redirect chain will never trigger.
- Site Reputation Abuse — the policy breach that redirected subfolders are most often used to hide.
A two-hop chain is a housekeeping job; an eleven-hop chain is a page Google never sees. If your audit report gave both the same severity colour, it counted your redirects rather than reading them.