Redirect Chains: Top-1k Benchmark 2026
Enterno.io measured redirect chains on first access for top-1000 sites (March 2026). 42% of sites make 2+ hops (e.g. http://example.com → https:// → https://www. → https://www./en/). 8% make 4+ hops, which is critical for SEO (Google and Yandex lose up to 15% of PageRank on long chains). Optimization leader: no-www + single-hop (25%).
Below: key findings, platform breakdown, implications, methodology, FAQ.
Key Findings
| Metric | Pass-rate / Value | Median | p75 |
|---|---|---|---|
| 1 hop (http→https, ideal) | 58% | — | — |
| 2 hops | 26% | — | — |
| 3 hops | 8% | — | — |
| 4+ hops (SEO risk) | 8% | — | — |
| Redirect loop (≥10 hops = halt) | 0.1% | — | — |
| 301 redirect | 82% | — | — |
| 302 redirect (wrong) | 11% | — | — |
| 307/308 redirect | 7% | — | — |
Breakdown by Platform
| Platform | Share | Pass / Detail | avg |
|---|---|---|---|
| WordPress | 18% | avg 2.1 hops | — |
| 1С-Bitrix | 14% | avg 2.8 hops | — |
| Next.js / SPA | 9% | avg 1.4 hops | — |
| Shopify | 4% | avg 1.8 hops | — |
| Tilda | 3% | avg 1.3 hops | — |
| Custom PHP | 32% | avg 2.2 hops | — |
Why It Matters
- Each hop adds 50-200ms to the first request — Core Web Vitals FCP/LCP degrade
- Google officially: "rel=canonical on the final URL is fine. But >5 hops slow crawl budget"
- Typical chain: http://example.com → https://example.com → https://www.example.com → https://www.example.com/en/ → https://www.example.com/en/home — 4 hops
- Fix: one server block handling every hostname variant with the right final canonical redirect
- 302 instead of 301 — search engines do not transfer link equity. Always use 301 for permanent
Methodology
Top-1000 Tranco (March 2026). curl -IL -w "%{num_redirects}\n" for every URL, separately http:// and https:// and with/without www. 301/302 classified by Location header + status. Platform detection — by Server/X-Powered-By/HTML signatures.
Why teams trust us
How it works
Enter URL
Redirect chain followed
Codes & final URL shown
Redirect checker: optimize redirect chains
Incorrect or long redirect chains slow down the site, lose PageRank and confuse search crawlers. The tool visualizes the full redirect chain with response codes and timing for each hop.
Full hop chain
Shows each redirect step: URL → code → URL → code, through to the final destination.
Time per hop
Measures latency at each redirect step for precise identification of performance bottlenecks.
Redirect type
Distinguishes 301, 302, 303, 307, 308 — each has different behavior for SEO and browsers.
Loop detection
Automatically detects circular redirects and warns before the browser throws an error.
Who uses this
SEO
redirect chain audit
Developers
301/302 debugging
DevOps
HTTPS redirect check
Marketers
UTM link tracking
Common Mistakes
Best Practices
Get more with a free account
Redirect check history and API for automated chain auditing.
Sign up freeLearn more
Frequently Asked Questions
How critical is a 3-hop chain?
UX — +100-300ms load time. SEO — Google accepts up to 5 hops without major losses. 6+ hops = red flag, especially for crawl budget.
How to fix in nginx without a double redirect?
In http:// server block do: <code>return 301 https://example.com$request_uri;</code> (not via www). Separate server block for www: <code>return 301 https://example.com$request_uri;</code>. Everyone lands on the final URL in 1 hop.
301 or 308 for www→non-www?
301 — traditional, universal support. 308 — RFC 7538, better for non-GET methods. For www→non-www (almost always GET) — both work, 301 is safer.
How do I check my redirect chain?
<a href="/en/redirects">Enterno Redirects checker</a> — enter the URL, see the full chain + codes + timing. Or: <code>curl -ILk https://example.com</code>.