How many redirects can Googlebot follow before it gives up?

What does 'a few redirects' actually mean?

Google deliberately remains vague about the exact limit. The phrasing 'a few redirects' suggests a flexible threshold, while 'unlikely' beyond five indicates a decreasing probability, not a systematic block.

In practice, Googlebot can technically follow more than five redirects, but the likelihood that it will give up increases with each additional hop. This uncertainty creates a risk: some pages may be indexed after six or seven redirects, while others will be abandoned after four.

Why does Google impose a limit on redirects?

Redirects consume crawl budget exponentially. Each hop requires a new HTTP request, a new download, a new check. On a site with thousands of pages, these multiple chains quickly saturate the allocated resources.

Beyond the technical aspect, long redirect chains often signal a disorganized architecture or poorly planned migrations. Google interprets them as an indicator of low quality, which can influence crawling priority.

How do different redirect codes behave in a chain?

All redirect codes (301, 302, 307, 308) count in the chain. A series of 301 to 302 to 301 represents three distinct hops, each consuming crawl budget and potentially diluting PageRank.

JavaScript or meta-refresh redirects add additional complexity. Google may interpret them differently depending on the context, and their combination with standard HTTP redirects creates hybrid chains that are difficult to predict.

• Beyond five redirects, Googlebot risks giving up crawling before reaching the target page
• Each additional hop dilutes the PageRank transmitted to the final destination
• Long chains consume crawl budget and slow down the overall site indexing
• Mixing redirect codes (301, 302, JavaScript) complicates tracking for Googlebot
• A clean architecture limits redirects to a single hop between the original URL and the final destination

Is this limit of five redirects consistent with real-world observations?

Yes, this statement aligns with empirical findings from SEO audits. Sites with chains of four to six redirects regularly show non-indexed target pages or pages indexed several weeks late. [To be verified] Google does not specify whether this limit applies uniformly to all sites or if it varies according to domain authority.

High-authority sites seem to benefit from a slightly higher tolerance, with chains of six redirects sometimes fully followed. That said, relying on this tolerance remains risky: the limit can fluctuate depending on server load, allocated crawl budget, or algorithmic adjustments.

What nuances should be applied to this rule?

The transmission of PageRank degrades with each hop, even if Google technically follows the entire chain. A single redirect already loses a small percentage of authority (estimated between 0% and 5% according to tests), and this loss accumulates over several hops. A chain of five redirects can thus lose 15% to 25% of the initial PageRank.

Moreover, Google does not guarantee identical treatment for all URLs. Strategic pages with numerous backlinks may benefit from an increased crawling effort, while secondary pages will be abandoned more quickly. This inequality in treatment makes a universal rule impossible.

In which cases does this rule not apply strictly?

Redirects within the same domain seem to be treated more flexibly than inter-domain redirects. Google can follow six or seven hops on the same site, while it gives up more quickly if the chain crosses several distinct domains.

Temporary redirects (302, 307) in a chain create additional ambiguity. Google may interpret the entire chain as temporary, delaying or preventing the consolidation of PageRank to the final destination. In these cases, the practical limit may be well below five hops.

What concrete steps should I take to adhere to this limit?

The first action is to audit all existing redirect chains with a professional crawler (Screaming Frog, Oncrawl, Botify). Identify every chain exceeding two hops and correct it by redirecting the original URL directly to the final destination.

When migrating a site, plan redirects in advance to avoid stacking 301s on existing 301s. If the site has undergone several redesigns, clean up any historical redirects before adding a new layer. This hygiene prevents turning a simple migration into a maze of redirects.

How can I verify that my site does not exceed the critical limit?

Set up your crawler to automatically detect chains of three redirects or more. Export the complete list and prioritize corrections based on organic traffic volume and the number of backlinks pointing to the original URLs. Strategic pages should be corrected first.

Use Google Search Console to identify URLs that have been crawled but not indexed. Cross-check this data with your redirect audit: a target page not indexed after several weeks may signal a chain that is too long or abandoned by Googlebot. Server logs confirm whether Google actually reaches the final destination.

What mistakes should I avoid when correcting chains?

Never remove a redirect in the middle of a chain without replacing it. This would create a 404 error for all URLs pointing to that link. Always correct by directly redirecting the source to the final destination, then remove the intermediate hops once the new rule is active.

Avoid circular redirects or infinite loops when making manual corrections. Test each modification with an HTTP checking tool (curl, HTTPStatus, Redirect Checker) before deploying it in production. A redirect loop can completely block crawling and indexing of an entire section of the site.

• Crawl the complete site to detect all redirect chains of three hops or more
• Prioritize corrections for chains affecting high-traffic pages or those with many backlinks
• Directly redirect the original URL to the final destination to eliminate intermediate hops
• Check via Search Console for URLs that have been crawled but not indexed, often a symptom of chains that are too long
• Analyze server logs to confirm that Googlebot is indeed reaching target pages after redirection
• Test each correction with an HTTP tool to avoid loops or accidental 404 errors