How many consecutive redirects can Google actually follow before giving up?

What happens technically when Googlebot encounters a redirect?

When the crawler requests a URL, the server may respond with a 301 (permanent) or 302 (temporary) status code and indicate a new address. Googlebot follows this instruction, sends a new request to the target, and repeats the process as needed.

The problem arises when this chain lengthens. Each hop consumes crawl budget, uses server resources, and increases total latency. Google therefore imposes a strict limit: five redirects maximum before cutting off.

Why don't two or three redirects block indexing but remain problematic?

On paper, two or three hops do not prevent Google from completing the crawl. The bot eventually reaches the target page and indexes it normally. However, the cost in response time accumulates.

A mobile user on a moderate connection endures additional latency of several hundred milliseconds. For sites with high traffic or significant volume, this friction amplifies: the crawler slows down, user sessions elongate, and the bounce rate rises.

When do we observe these redirect chains?

Classic scenarios include successive migrations (old domain to temporary domain then final domain), HTTP redirects to HTTPS then to www, or cascading category redirects after taxonomy overhauls.

Another common case: poorly managed parameter redirects, where a CMS automatically adds a final slash, then redirects to a canonical version, and then to a translated URL. Result: three hops for a single target page.

• Google tolerates up to five successive redirects before abandoning the crawl of that URL
• Two or three redirects are enough to degrade user response time without blocking indexing
• Each hop consumes crawl budget and increases total latency
• Chains often appear during migrations, HTTPS overhauls, or site restructurings
• Always prefer a direct redirect to the final target

Does this limit of five redirects really match field observations?

On high-authority sites with a large crawl budget, Google does indeed tolerate five hops. I have observed chains of four redirects indexed without issues on media with high crawl frequency. However, on less prioritized sites, three redirects can sometimes drastically slow down indexing.

The absolute limit of five seems more like a technical threshold than a guarantee of smooth indexing. Google can follow, but it doesn't mean it will do so quickly or consistently. [To be verified]: no official data specifies whether this limit applies uniformly according to PageRank or allocated crawl budget.

Should we really worry about two or three successive redirects?

Let's be honest: two redirects won't kill your SEO. But they add measurable latency that impacts Core Web Vitals, particularly LCP and FID. On mobile, every server round trip counts double.

And that's where it gets tricky: an HTTP redirect to HTTPS then to www already creates two hops. Add a poorly configured parameter redirect, and you reach three. In practical terms, that's wasted time for both the crawler and the user.

What types of redirects pose the most problems in practice?

JavaScript redirects or meta-refreshes do not count towards this limit of five, but they are even more penalizing: Google has to execute the JS or wait for the delay, massively slowing the crawl down. Avoid them completely for migrations or consolidations.

Improperly used temporary 302 redirects also prolong indexing: Google retains the source URL in the index rather than consolidating towards the target. This results in temporary duplication and dilution of PageRank. Always prefer 301 permanents to the final destination.

How can I detect and fix redirect chains on my site?

Start with a complete crawl using a tool like Screaming Frog, OnCrawl, or Botify. Configure the crawler to follow redirects and export the list of detected chains. Focus first on URLs with high organic traffic or significant backlinks.

In Search Console, filter indexed pages with multiple redirects in the coverage report. Correct by mapping the source URL directly to the final target in your .htaccess file or server configuration.

What cases require immediate action?

First, strategic pages: homepage, main categories, best-selling product pages. If these URLs go through several hops, they unnecessarily consume crawl budget and slow down indexing of new content or updates.

Next, recent domain migrations. Ensure your 301s point directly to the new domain without going through intermediate steps. An old domain redirecting to a transitional domain before the final domain dilutes the transfer of PageRank.

Can we automate this maintenance to avoid regressions?

Yes, by integrating continuous monitoring. Set up alerts in your crawl tool to detect any new redirect chains beyond two hops. Some CMSs allow for automatic consolidation of redirects upon publication.

For complex or high-volume sites, this maintenance can quickly become time-consuming. If your team lacks the resources or technical expertise to monitor and fix these anomalies regularly, considering support from a specialized SEO agency can save you valuable time and secure your long-term performance.

• Crawl your site with Screaming Frog or OnCrawl to identify all redirect chains
• Prioritize URLs with high traffic or quality backlinks
• Correct by mapping the source URL directly to the final destination (avoid intermediate steps)
• Ensure your migrations use 301 permanents to the final target only
• Set up automatic alerts to detect new chains beyond two hops
• Regularly audit the Search Console coverage report to spot anomalies