Home / Learn / Redirect chains & crawl budget

Redirect chains and crawl budget

A redirect chain is two or more redirects in a row between the URL someone requested and the page that finally answers. Here is what they cost, who should worry about crawl budget, and how to flatten them.

What a chain costs

Time for every visitor. Each hop is another request, and when the host changes, another DNS lookup and TLS handshake. On mobile networks a three-hop chain can add hundreds of milliseconds before the first byte of the real page.
A hard stop for Googlebot. Google's documentation says Googlebot follows up to 10 hops; beyond that the target isn't fetched and Search Console reports a redirect error.
Fragility. Every hop is a rule someone can break. Chains are where loops come from.
Mixed signals. A chain with a 302 in the middle blurs whether the move is permanent.

What chains don't do is "leak" PageRank per hop. Google has said that 3xx redirects don't lose PageRank. The case for flattening is speed, reliability and clarity.

Build a chain, then collapse it

What the visitor or old backlink requests

How the server's rules are written

301Requested
http://example.com/shop/blue-mug
301Rule 1: force HTTPS
https://example.com/shop/blue-mug
301Rule 2: add www
https://www.example.com/shop/blue-mug
301Rule 3: migration map
https://www.example.com/mugs/blue
200Rule 4: add trailing slash → canonical
https://www.example.com/mugs/blue/

4 hops Each rule fires on its own and hands the visitor to the next one. Switch to "One combined rule" to see the same fixes collapse into a single hop.

Crawl budget, plainly

Google Search Central's crawl budget guide defines it as the number of URLs Googlebot can and wants to crawl on a site, a mix of crawl capacity (how fast your server can be crawled without strain) and crawl demand (how popular and fresh your URLs are).

The guide is explicit that it's written for large sites: roughly a million-plus unique pages changing weekly, or 10,000+ pages changing daily, or sites with many URLs reported as "Discovered – currently not indexed". If your pages are usually crawled the day they're published, crawl budget is not your problem.

For those large sites, every redirect hop is a fetch spent on a URL with no content. Google lists long redirect chains among the things that hurt crawling, alongside faceted navigation, session IDs, soft 404s and duplicate content.

Finding and flattening chains

Export old URLs: the redirect map, backlink targets from your SEO tool, and URLs with traffic in the last 16 months of Search Console.
Run them through the bulk redirect checker and filter Chains.
Click Flatten chains in generator: each first URL is mapped straight to its final 200 URL.
Merge site-wide rules (HTTPS, host, slash) into one, as in the simulator. The generator's HTTPS/www/slash mode writes it for you.
Update internal links, canonicals and the sitemap to the final URLs, so your own site never triggers a redirect.
Re-run the bulk check. Target: one hop, permanent, ending in 200.

Questions

How many redirects are too many?

More than one is worth fixing; ten or more means Googlebot stops. Browsers give up at around 20 and show a "too many redirects" error.

Do redirect chains hurt SEO?

Indirectly. They slow pages, waste crawl requests on large sites, and break outright past 10 hops. Google says redirects themselves don't cause PageRank loss, so a single hop is perfectly fine.

What is the difference between a redirect chain and a redirect loop?

A chain eventually reaches a page. A loop returns to a URL it already visited, for example A → B → A, so it never ends and no page loads.

Does crawl budget matter for small sites?

Rarely. Google says most sites with fewer than a few thousand URLs will be crawled efficiently. Fix chains there for speed and reliability rather than crawl budget.