Should you worry about redirect chains longer than five hops?

What does this limit of five redirects mean in practice?

Google imposes a technical limit of five hops during a crawl session. If your URL A redirects to B, which redirects to C, and so on until F, the bot stops before reaching the sixth destination.

This is not a soft recommendation. It is a strict technical constraint. If your chain exceeds this limit, the final page will never be reached during that crawling session, which totally compromises its indexing.

Why does Mueller emphasize the clarity of the structure?

Contradictory signals between HTTP redirects and canonical tags create ambiguities. Imagine a page A that redirects to B with a 301, but also has a rel=canonical pointing to C.

Google has to make a choice. It will pick based on its own logic, not necessarily the one you had in mind. Mueller reminds us that the engine interprets these mixed signals without any guarantee that its choice will align with your strategic intention.

What use cases trigger this type of problem?

Poorly planned site migrations easily accumulate redirects. A site migrates from domaine-v1.com to domaine-v2.com, then to domaine-v3.com, then adds HTTPS, then changes URL structure.

The result: an initial URL can traverse four or five hops before reaching its final version. Add to that poorly configured canonical tags during the transition, and you get a chaotic signal.

• Strict limit: Google only follows a maximum of 5 redirects in a single crawl pass
• Risk of conflicts: mixing HTTP redirects and canonical tags without consistency creates random interpretations
• Indexing impact: a final URL inaccessible beyond 5 hops will never be indexed properly
• Multiple migrations: each domain or structure change adds an additional hop
• Verification needed: regularly audit chains to avoid invisible accumulations

Is this limit of five hops consistent with field observations?

Yes, and it is often even more severe than that. On high-volume sites, it has been observed that Google may sometimes abandon the crawling process before even reaching the fifth hop if the response time for redirects is too long.

The crawl budget is not infinite. Googlebot calculates the time cost of each request. A chain of slow redirects unnecessarily consumes budget, and the bot may cut short to optimize its passage.

What should you do when redirects and canonicals conflict?

Google generally favors HTTP redirection over canonical tags, but not always. If page A redirects to B but has a canonical pointing to C, Google may ignore the redirect if it determines that C is more consistent with other signals (backlinks, internal linking, history).

The problem? You lose control. Instead of relying on Google’s logic, eliminate any ambiguity. A URL should carry only one destination signal: either a redirect or a canonical, never both pointing to different targets.

When does this rule become critical?

E-commerce sites with product variant management are particularly exposed. A product URL may redirect to a default variant while having a canonical pointing to a category page.

The same goes for multi-regional sites. A URL may redirect based on IP geolocation while carrying a canonical to a generic international version. Google must then interpret contradictory signals, and the outcome is never guaranteed. [To be checked] on each deployment: test with different IPs and monitor Search Console to spot ignored canonicals.

How to audit redirect chains on an existing site?

Use Screaming Frog in list mode and enable the 'Follow Redirects' option. Export all URLs that exceed 2 redirects. Any chain of 3 hops or more needs immediate correction.

Also check the server logs: an URL generating multiple successive Googlebot requests before reaching its target unnecessarily consumes crawl budget. If you see repeated patterns of 3+ requests for the same source URL, it's a warning signal.

What strategy should be implemented during a domain migration?

Redirect directly to the final destination, never in a cascade. If you are moving from ancien-domaine.com to nouveau-domaine.com, ensure that each URL from the old domain points directly to its corresponding one on the new domain, without going through intermediate redirects.

Remove the canonicals from the old domain as soon as the redirects are in place. A canonical on a page that redirects creates a double unnecessary signal. The redirect is enough. Keep the canonicals only on the active pages of the new domain.

What to do if a long chain is technically unavoidable?

Sometimes, technical constraints require multiple hops (CDN, load balancer, server rules). In that case, document the entire chain and monitor Search Console for any indexing loss.

Use server-side 301 redirects rather than meta refresh or JavaScript redirects. Google follows classic 301s better, and they consume less processing time. If you exceed 3 hops, consider a technical redesign to bypass intermediate steps.

These optimizations for redirects and canonicals may seem simple on paper, but their implementation on a complex site requires thorough technical analysis. Identifying all hidden chains, coordinating migrations and redesigns, and monitoring indexing impacts demand specialized expertise. Engaging a specialized SEO agency helps avoid costly mistakes and ensures a smooth transition without loss of visibility.

• Audit all URLs with Screaming Frog to identify chains of 3+ redirects
• Eliminate canonicals on pages that already redirect in HTTP 301
• Redirect directly to the final destination, never in a cascade
• Test redirects with multiple user-agents and geolocations if the site targets different countries
• Monitor Search Console for ignored canonicals or non-indexed URLs
• Favor server-side 301 redirects over meta refresh or JavaScript