Redirect chains and loops
A redirect chain is a sequence of hops (A to B to C) before reaching the final URL; a redirect loop never resolves. Chains waste crawl budget, slow signal consolidation, and can stop crawlers following beyond a hop limit. The fix is to point each source straight at the final destination.
What chains and loops are
A redirect chain is when a URL redirects to another URL that itself redirects, and so on, before the final destination is reached: A to B to C. A redirect loop is a cycle that never resolves — A to B back to A — so the final resource is never delivered.
Each hop is a separate request the crawler must make before it can index anything.
Why chains waste crawl budget
Every redirect hop is an extra fetch. A chain multiplies the requests needed to reach one page, consuming crawl budget that could discover new content, and it slows the consolidation of signals onto the final URL. Search engines also follow only a limited number of hops; beyond that they may stop, leaving the destination uncrawled.
Loops are worse: the page is unreachable until the cycle is broken.
The fix is to update each redirect rule and internal link to point directly at the final URL, collapsing the chain to a single hop.
- Each hop is an extra crawl request
- Keep redirects to one hop to the final URL
- Crawlers stop after a hop limit; loops never resolve
Operator checklist
Audit redirects for chains and rewrite them to point straight at the final destination. Detect and break any loops. Update internal links and sitemap entries to use the final URL so neither users nor crawlers traverse a redirect at all.
How it appears in analytics and logs
Multiple redirects before the final URL mean a chain; a redirect that returns to an earlier URL is a loop. Both waste crawl budget; loops can prevent a page from being reached at all. Crawlers stop following after a limited number of hops.
Diagnostic use case
Find and collapse multi-hop redirect chains and detect loops, so crawlers reach final URLs in a single hop and stop wasting budget.
What WebmasterID can help detect
WebmasterID can surface URLs that redirect to crawlers, helping you spot chains and loops and confirm that links resolve in a single hop.
Common mistakes
- Adding new redirects on top of old ones, building a chain over time.
- Linking internally to URLs that redirect instead of the final URL.
- Creating a loop where two rules redirect to each other.
Privacy and accuracy notes
Redirect status codes carry no personal data. WebmasterID reports redirect patterns for crawler traffic without exposing individual visitors.
Related pages
- HTTP 301 Moved Permanently for crawlers
301 Moved Permanently tells clients and crawlers that a resource has permanently moved to a new URL. It is the standard signal for migrations and URL changes: crawlers follow it, update their index over time, and consolidate ranking signals onto the new location. Use it whenever content has a stable new home.
- Crawl budget waste: causes and fixes
Crawl budget is the finite attention a search engine spends on your site. It is wasted when crawlers spend it on low-value URLs — endless faceted combinations, parameter variants, soft 404s, and redirect chains — instead of your important pages. Reducing that waste helps key content get crawled.
- Website observability
See which URLs redirect and whether they resolve in one hop.
Sources and verification notes
- Google Search Central — Redirects and Google SearchDocuments how Google follows redirects and the effect of chains.
- MDN — Redirections in HTTP
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.