How many redirect hops can Google actually follow before it loses track?

Why does Google impose a limit on the number of redirects?

Googlebot has a crawl budget that is limited for each site. Following a chain of redirects unnecessarily consumes this budget since the bot has to make multiple HTTP requests to reach the final destination.

Each additional hop in a chain of redirects adds latency. If your technical architecture imposes three, four, or five redirects before reaching the actual content, you force Googlebot to multiply requests. The risk? The bot may simply give up before reaching the target page, especially if your crawl budget is already tight.

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

A simple redirect (A → B) is standard and generally poses no issue. A chain of redirects occurs when A redirects to B, which redirects to C, which redirects to D. This is the scenario that Matt Cutts discusses.

These chains often form accidentally: redesign after redesign, successive migrations, poorly documented URL changes. The result? The architecture becomes a layered stack of inherited redirects. Google can technically follow these paths, but it will not do so indefinitely.

What is the real impact on indexing and ranking?

The first consequence: response time increases mechanically. Each redirect adds 100 to 300 ms depending on server configuration. Multiply that by four or five hops and you reach 500 ms to 1.5 seconds just for the redirects.

The second documented effect: the dilution of PageRank. Although Google has stated that 301 redirects fully transmit equity for several years, each additional hop in a chain introduces friction. Matt Cutts does not quantify this loss, but field observations show that beyond two hops, the final pages lose perceived authority.

• Crawl budget: each redirect consumes a separate HTTP request, reducing the number of pages actually crawled
• Risk of abandonment: beyond 5-6 hops, Googlebot may stop following before reaching the destination
• Cumulative latency: each redirect adds 100-300 ms, degrading user experience and performance signals
• Equity transmission: PageRank dilution becomes noticeable beyond two hops, even if Google does not explicitly acknowledge it

Is this limit of three hops really respected by Google?

In practice, yes. Crawl tests show that Googlebot rarely follows beyond four or five consecutive redirects. Matt Cutts' recommendation (limit to one or two hops) is not arbitrary: it is a safety margin.

Let's be honest: if your architecture systematically imposes three redirects to access content, you have a structural problem. The real question is not "Will Google follow?", but "Why does my architecture impose this detour?" A chain of redirects often signals accumulated technical debt.

When do we observe problematic chains?

Poorly cleaned successive migrations. A typical example: a site migrates from HTTP to HTTPS, then changes its domain name, then restructures its hierarchy. If redirects stack instead of being consolidated, you end up with HTTP → HTTPS → new domain → new URL. Four hops.

Another frequent case: poorly configured geolocalized or language redirects. A user arrives at example.com, which redirects to example.com/fr/, which redirects to example.fr, which finally redirects to example.fr/home/. Result: user experience is degraded, and Googlebot struggles to identify the canonical page.

What is the actual loss in terms of PageRank?

Matt Cutts remains vague on this point, and Google has never published an official figure. [To verify] According to field observations, each additional hop beyond the first seems to introduce an equity loss of about 5 to 10%. This is not officially documented, but it is consistent with the ranking variations observed.

The problem is not so much the theoretical loss, but the signal sent to Google: a site that imposes four redirects before displaying its content suggests a poorly managed architecture. This lack of technical rigor can impact the trust granted by the algorithm, even if this causal link is difficult to prove.

How to audit redirect chains on your site?

Use Screaming Frog or Sitebulb in "Spider" mode. Configure the tool to display full redirect chains. Export the list and filter all URLs with more than two hops.

Another method: analyze server logs. Identify URLs that generate multiple successive HTTP requests before serving a 200 code. This approach is more precise as it reflects Googlebot's actual behavior, not a simulation.

What to do once chains are identified?

Consolidate redirects. If A redirects to B, and then B to C, replace the A → B redirect with a direct A → C redirect. Remove the intermediary. This operation requires access to the .htaccess file, nginx.conf, or CDN rules depending on your stack.

Warning: never abruptly remove an intermediary redirect without verifying that no external link points directly to it. First check in Google Search Console or Ahrefs if any backlinks target these intermediary URLs. If so, maintain a direct redirect from each of these URLs to the final destination.

What mistakes should be avoided at all costs?

Never create redirect loops (A → B → A). This seems obvious, but after several migrations, these loops sometimes appear accidentally. Screaming Frog detects them immediately: error code "Redirect Loop".

Another trap: conditional redirects (based on user-agent, geolocation, cookies) that create different chains depending on the context. Googlebot may follow a different path than a real user, making auditing complex. Always test with the Googlebot user-agent explicitly.

These technical optimizations require in-depth knowledge of server architecture and SEO issues. If your infrastructure is complex or if redirect chains affect strategic pages, it may be wise to consult a specialized SEO agency for a complete audit and customized action plan. A misstep can break critical redirects and immediately impact traffic.

• Audit your site with Screaming Frog or Sitebulb to identify all redirect chains
• Consolidate chains: replace A → B → C with A → C directly
• Check backlinks to intermediary URLs before removing a redirect
• Test with the Googlebot user-agent to detect conditional redirects
• Monitor server logs after modification to confirm that Googlebot follows the new redirects
• Document each redirect chain and the reason for its creation to prevent it from reforming