A redirect chain occurs when a URL passes through two or more redirects before reaching its final destination. Each hop adds between 100 and 300 ms of latency — milliseconds that accumulate and that both search engines and users notice.
What Is a Redirect Chain
Imagine a user visits http://yourdomain.com/page and this happens:
http://yourdomain.com/page→ 301 →https://yourdomain.com/pagehttps://yourdomain.com/page→ 301 →https://www.yourdomain.com/pagehttps://www.yourdomain.com/page→ 301 →https://www.yourdomain.com/page/
That's three redirects before any content loads. The browser must complete a full request–response cycle at every hop. The result: an inflated TTFB, a slow user experience, and negative signals for Google's crawlers.
Why Redirect Chains Form
They're rarely intentional. The most common causes are:
Migrations Without Cleaning Up Old Redirects
When relaunching a site, new redirects are created but old ones remain. The result: URL-A → URL-B → URL-C, when the correct setup would go URL-A → URL-C directly.
Separate HTTPS and WWW Rules
Many sites have two separate rules: one that redirects HTTP to HTTPS and another that adds (or removes) the www prefix. If these aren't combined into a single .htaccess rule, they generate two hops instead of one.
Trailing Slash Inconsistencies
WordPress and other CMS platforms automatically redirect /page to /page/ (or vice versa). If the original link already pointed to the wrong version, that adds another redirect to the chain.
Accumulated Redirect Plugins
URL changes managed over time through redirect plugins create layers that were never audited as a whole.
The Real Impact on Website Speed
Each redirect involves:
- A new TCP request–response cycle.
- An additional TLS handshake in HTTPS if the domain changes.
- The browser cannot begin downloading any resources until it resolves the final destination.
On real mobile networks (average 4G latency of ~40 ms), a three-hop chain can add between 120 and 400 ms to the TTFB before a single byte of content loads.
| Number of hops | Added latency (estimated, 4G) | SEO impact |
|---|---|---|
| 1 (optimal) | ~40–80 ms | None |
| 2 hops | ~80–160 ms | Minor |
| 3 hops | ~120–300 ms | Moderate (PageRank dilution) |
| 4+ hops | 300 ms or more | High (Google may not follow the chain) |
Additionally, each redirect dilutes PageRank. Google passes less link authority through long chains, which can hurt the rankings of important pages.
How to Detect Redirect Chains
There are several ways to identify them:
Screaming Frog SEO Spider
The most widely used crawling tool in SEO. Go to Reports → Redirects → Redirect Chains and it lists every URL with more than one hop. The free version crawls up to 500 URLs.
Online Redirect Tracing Tools
Sites like httpstatus.io or redirect-checker.org let you paste a URL and see all redirect hops instantly, with nothing to install.
curl from the Terminal
If you have terminal access, this command shows every hop:
curl -s -L -o /dev/null -w "%{url_effective}\n" --max-redirs 10 -D - https://yourdomain.com/page 2>&1 | grep -E "^(HTTP|Location)"Google Search Console
In the Coverage report you can identify URLs that return redirects and verify where they ultimately point.
How to Eliminate Redirect Chains
The solution is always the same: collapse the chain into a single 301 redirect that goes directly from the source to the final destination.
Unify Rules in .htaccess (Apache)
Instead of two separate blocks (HTTP→HTTPS and non-www→www), write a single rule that does both:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]This converts any combination of HTTP/non-www into a single redirect to the HTTPS-with-www version.
Update Redirects in the Plugin
If you use Redirection, Yoast, or any similar plugin, check whether any destination URL is itself redirected. Update the target to the final URL directly.
Update Internal Links
Redirects are justified for external URLs you can't control. For internal links, the right move is to update the URL in the HTML itself — don't rely on the redirect.
A web performance agency can audit all your site's redirects, collapse the chains, and systematically update internal links so Google crawls your content without friction.
Key Takeaways
- A redirect chain is any URL that passes through 2 or more hops before reaching content.
- Each hop adds 40–150 ms of latency — critical on mobile networks.
- Long chains dilute PageRank and can prevent Google from crawling the final destination.
- The most common causes are unclean migrations, separate HTTP/HTTPS rules, and accumulated redirect plugins.
- The fix is to collapse the entire chain into a single direct 301 redirect to the final destination.
- Update internal links to point directly to the canonical URL — don't rely on internal redirects.
Auditing your site's redirects is one of the fastest ways to improve TTFB and SEO crawlability. Find more practical guides in the web performance category, or reach out to our team for a full technical audit.
FAQ
Does a single 301 redirect affect speed?
Yes, but minimally and acceptably. A single properly configured redirect (for example, HTTP to HTTPS) is standard practice and its TTFB impact is usually under 50 ms. The problem is chains of two or more hops.
Are 302 redirects faster than 301 redirects?
There's no speed difference; both require the same request–response cycle. The distinction is semantic: 301 is permanent (passes PageRank), while 302 is temporary (does not reliably pass PageRank).
How many redirects does Google follow?
Googlebot follows up to 10 redirects per URL. However, from the fifth hop onward, PageRank transfer becomes uncertain. Google recommends keeping chains to a maximum of 3–4 hops, though a single direct redirect is always the ideal.
How do I know if my .htaccess changes worked?
Run curl -I https://yourdomain.com/problem-page — if you see a single HTTP/2 301 followed by the final destination, the chain has been collapsed. You can also verify it with httpstatus.io or by re-crawling the site in Screaming Frog.
Further reading
Other providers and guides worth comparing:
