Redirect Chain Analyzer
Trace redirect chains, detect loops, and find unnecessary hops. Up to 500 URLs, response time per hop, migration mode, and User-Agent selector.
What is a redirect chain?
A redirect chain occurs when a URL redirects to another URL, which then redirects again — creating a sequence of hops before reaching the final destination. For example: URL A → URL B → URL C → URL D (final destination). Every intermediate hop is unnecessary if A can point directly to D.
Why do redirect chains form?
Chains typically appear after poorly planned site migrations, domain changes (HTTP→HTTPS, non-www→www), URL restructuring, or redirect plugins that accumulate rules over time without review. They're also common in e-commerce when categories are reorganized or products removed.
Why redirect chains hurt SEO
- They waste crawl budget: Googlebot follows a limited number of redirects per session. Every unnecessary hop consumes crawl budget and can delay indexing of important pages.
- They dilute PageRank: each intermediate redirect transfers less authority than a direct one. A 3-hop chain means a notable loss of link equity compared to a 1:1 redirect.
- They increase load time: each hop requires a new HTTP request, adding milliseconds to TTFB and negatively affecting Core Web Vitals, especially LCP.
- They damage user experience: slow redirects cause frustration and increase bounce rates, especially on mobile where latency is higher.
HTTP redirect types and when to use each
Not all redirects are equal. Choosing the right type is critical for preserving SEO:
| Code | Description and use |
|---|---|
| 301 | Moved Permanently. The most important redirect for SEO. Transfers virtually all link equity. Use for domain changes, HTTP→HTTPS migration, or consolidating duplicate URLs. |
| 302 | Found (temporary). Google keeps the original URL indexed and does not transfer PageRank. Use only when content will return to its original URL. Common mistake: using 302 for permanent changes. |
| 307 | Temporary Redirect (HTTP/1.1). Similar to 302 but preserves the original HTTP method. Recommended with HSTS when provisional redirects are needed. |
| 308 | Permanent Redirect (HTTP/1.1). The modern equivalent of 301 that also preserves the HTTP method. Use in modern stacks when you need to preserve POST requests. |
| Meta refresh | HTML redirect, not HTTP. Very slow, doesn't transfer PageRank efficiently, and Google treats it with less trust. Avoid whenever possible. |
How to detect redirect chains
- 1.The fastest way is this tool: enter the suspect URL and you'll see each hop with its status code and response time. For large sites, export the CSV and filter by hops > 1.
- 2.Google Search Console → Coverage → excluded pages: look for URLs marked as 'Redirected'. If you see main content pages there, it may indicate misconfigured chains.
- 3.Screaming Frog: in the 'Response Codes' tab filter by 3xx. The paid version has automatic chain detection.
How to fix redirect chains
The solution is always the same: make each source URL point directly to the final destination, eliminating all intermediate hops.
In Apache (.htaccess) — point A directly to C:
Redirect 301 /old-page https://www.yourdomain.com/new-page
In Nginx:
rewrite ^/old-page$ https://www.yourdomain.com/new-page permanent;
In WordPress: use the 'Redirection' plugin or edit .htaccess. Review accumulated rules that unintentionally form chains.
After applying the change, verify here that the new configuration resolves in a single 301 hop.
Common redirect management mistakes
- Using 302 instead of 301 for permanent changes: Google does not transfer PageRank through temporary redirects.
- Redirect loops: A→B→A. The crawler gets trapped and the page won't be indexed. This tool detects loops automatically.
- Redirecting everything to the homepage: during a migration, redirecting non-existent pages to the home page seriously damages SEO.
- Not updating internal links: even if the redirect works, every internal link pointing to the old URL adds an unnecessary hop.
- Chains accumulated by plugins: WordPress redirect plugins keep adding rules over time. Audit them regularly.