Redirect chains in 2026: data from 806 checks
Across 806 checked addresses: 48% answer directly and another 35.4% after a single hop (http → https or www). The mean is 0.74. 2.9% take three or more, and one address in the sample returned ten. .ru redirects more: 0.80 against 0.59 for .com.
Where the numbers come from. Our own checks, with the sample and its limits spelled out.
Free online tool — redirect checker: instant results, no signup.
Methodology and the limits of this data
Every number here comes from our own checks, and they share one origin.
Between 17 April and 27 August 2026 our redirect checker ran 1,263 checks. What follows counts the latest verdict for each of 806 unique addresses.
This is neither a sample of the web nor a top list: these addresses reached us because somebody chose to check them, often on suspicion of an extra hop. Comparing zones inside the sample is sound; carrying the level over to "all websites" is not.
We count redirects, not "hops": zero means the address answered directly, one means a single redirect. A hop count runs one higher, and the two should not be confused.
How many hops there actually are
| Redirects | Addresses | Share |
|---|---|---|
| 0 — answered directly | 387 | 48.0% |
| 1 | 285 | 35.4% |
| 2 | 111 | 13.8% |
| 3 | 12 | 1.5% |
| 4 | 7 | 0.9% |
| 5 or more | 4 | 0.5% |
The mean is 0.74 redirects per address. Nearly half answer immediately; another third survive exactly one hop, usually http → https or normalising www. That hop is normal and unavoidable.
The tail is the interesting part: 2.9% of addresses take three or more, and one address in the sample returned ten. Ten is no longer configuration but sediment — a domain change, then a move to https, then a new URL structure, with nobody collapsing the chain back to a single step.
.ru redirects more
| Zone | Addresses | Mean | Answered directly | Two or more |
|---|---|---|---|---|
| .ru | 543 | 0.80 | 42.7% | 17.5% |
| .com | 97 | 0.59 | 55.7% | 13.4% |
The gap is small but consistent: Russian addresses average about a third more hops and answer directly less often — 42.7% against 55.7%.
On sample size: 97 addresses in .com is few, and we do not consider the 4-point difference on "two or more" established. The 13-point gap on "answered directly" does look solid at this size.
What an extra chain costs
- Every hop is a separate connection. On a mobile link one extra redirect costs hundreds of milliseconds before the first byte, and nothing wins that time back.
- A crawler spends its budget on the chain. Three hops instead of one means three requests instead of one for the same page.
- Chains break in the middle. An intermediate address stops answering one day and the page becomes unreachable although the final address is alive.
- Mixing 301 and 302 inside a chain leaves the engine unsure which address is canonical.
What a site owner should do
- Collapse the chain to one hop. The rule should lead from the original address straight to the final one, not down a staircase. See your own chain with the redirect checker.
- One hop is fine.
http → httpsand www normalisation are unavoidable; there is no need to fight for zero. - Check that internal links point at the final address. Chains usually come not from server configuration but from old links scattered across the site.
- Watch that the chain does not break. Intermediate addresses deserve monitoring too — they fail more quietly than the final one.
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: return 301 https://example.com$request_uri; (not via www). Separate server block for www: return 301 https://example.com$request_uri;. 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?
Enterno Redirects checker — enter the URL, see the full chain + codes + timing. Or: curl -ILk https://example.com.
Try the live tool that powered this guide
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.