Redirect Chain.
Trace redirect chains, detect loops, and measure timing per hop.
About Redirect Chain Analyzer
Redirect chains occur when a URL redirects through multiple intermediate URLs before reaching the final destination. Long chains slow down page loads and can hurt SEO. This tool follows each redirect hop, recording the HTTP status code, destination URL, and response time. It also detects infinite redirect loops that would cause browsers to give up. Use it to audit your redirects, debug shortened URLs, or verify migration paths.
How to Use
- Enter the URL you want to trace.
- Click "Trace Redirects" to follow the chain.
- Review each hop with status code, URL, and timing.
Key Features
- ✓ Follow up to 20 redirect hops
- ✓ Show HTTP status code per hop (301, 302, 307, 308)
- ✓ Measure response time for each hop
- ✓ Detect infinite redirect loops
- ✓ Show total chain time and final destination
Common Use Cases
- • Auditing redirect chains for SEO optimization
- • Debugging URL shortener behavior
- • Verifying domain migration redirects
- • Checking affiliate link redirect paths
Frequently Asked Questions
What is a redirect chain?
A redirect chain is a sequence of HTTP redirects where URL A redirects to B, B redirects to C, and so on. Each redirect adds latency. Google recommends keeping chains to 3 hops or fewer.
What is a redirect loop?
A redirect loop occurs when URL A redirects to B, and B redirects back to A (or through a longer cycle). Browsers detect this and show an error like "too many redirects."
What is the difference between 301 and 302?
301 is a permanent redirect — search engines transfer ranking to the new URL. 302 is temporary — the original URL keeps its ranking. Use 301 for permanent moves.
How many redirects are too many?
Google follows up to 10 redirect hops. For best performance and SEO, aim for 1-2 hops maximum. This tool follows up to 20 hops to help identify long chains.