The short answer: A redirect chain occurs whenever a URL passes through more than one intermediary server before delivering content (e.g. http://site.com → https://site.com → https://www.site.com). You can squash this in your Nginx, Apache, or Cloudflare configuration by forcing Hop 1 to point directly to the final canonical address.
What Exactly is a Redirect Chain?
When a visitor or a search engine crawler requests an address, your server might respond with an HTTP 301 or 302 pointing to a new destination. If that second destination immediately responds with another redirect to a third address, you have a redirect chain.
In an ideal setup, any request reaches its final destination in exactly 0 or 1 hop. When chains grow to 3, 4, or 5 hops, user experience and SEO rankings take an immediate hit.
1.
http://example.com/blog (301 to HTTPS)2.
https://example.com/blog (301 to trailing slash)3.
https://example.com/blog/ (301 to WWW)4.
https://www.example.com/blog/ (200 OK)Result: The user waited through 3 full network roundtrips just to read a blog post.
How Much Latency Does Each Redirect Hop Add?
Every single redirect hop requires the client to tear down or re-negotiate connections:
- DNS Lookup: 15ms – 120ms (if changing subdomains or external domains)
- TCP Handshake: 20ms – 80ms
- TLS Negotiation: 30ms – 150ms
- Server TTFB: 50ms – 250ms
On desktop fiber connections, a 3-hop chain might only add 150ms. But on a 4G or 5G mobile connection with fluctuating signal, that exact same chain frequently adds 800ms to 1.5 seconds of blank-screen delay. In eCommerce, a 1-second delay translates directly to a 7% drop in conversions.
Does Googlebot Give Up on Long Redirect Chains?
Yes. Googlebot's official documentation states that search crawlers will follow up to 5 redirect hops in a single crawl attempt. If the chain exceeds 5 hops, Googlebot aborts the crawl, flags the URL as a redirect error in Google Search Console, and refuses to index or transfer PageRank to the destination page.
Even worse, if your site has thousands of legacy backlinks passing through multiple hops, you are squandering your site's crawl budget on useless 301 loops instead of indexing new content.
How to Squash a Multi-Hop Chain into a Single Hop
Squashing redirect chains requires ordering your server rewrite rules from most specific to least specific. Rather than executing chained checks sequentially, resolve the destination in a single rule.
Example Nginx Configuration (Clean Single Hop):
# Catch all plain HTTP and non-www requests in ONE rule
server {
listen 80;
listen 443 ssl;
server_name example.com http.example.com;
return 301 https://www.example.com$request_uri;
}
By routing both non-SSL and non-WWW traffic directly to https://www.example.com in a single statement, you eliminate two unnecessary intermediate hops instantly.