Redirect Chain Visualizer
Free toolPaste or upload an already-exported redirect list (source, destination, HTTP status). We detect multi-hop chains, loops, chains longer than recommended, and final destinations that don't return 200, without crawling any URL live: everything is computed from the data you provide. Everything is processed in your browser: nothing is uploaded to RA Software Apps servers.
Detected chains
Distribution by number of hops
| Chain | Hops | Final status | Findings |
|---|
Report
Markdown report
JSON
How to use it
- Export your redirects to a list with source, destination and status code.
- Paste it or upload the file.
- Review multi-hop chains, loops and final destinations that do not return 200.
What it works out and how
The tool links each source to its destination and follows the chain to the end using only the data you give it: it visits no URL. That is how it finds redirects that go through several intermediate stops, loops where a URL ends up pointing back to itself, and chains that finish in an error or in yet another redirect.
Frequently asked questions
How many hops are too many?
Ideally one: from the source straight to the final destination. Every extra hop adds latency, and Googlebot stops following a chain after about ten hops.
What is the difference between 301 and 302?
A 301 signals a permanent move and consolidates signals on the destination; a 302 is temporary and keeps the original URL as the reference.
How do I fix a chain?
Edit each intermediate rule so it points straight to the final destination, and update internal links so they do not go through the redirect.