Redirect map input
Paste CSV or choose a local file
Recognized headers include source/target, from/to, old_url/new_url, and origin/destination. Headerless two-column input is accepted.
No redirect data has been processed.
Free browser tool
Audit a redirect map before it reaches production
Paste a two-column redirect map or upload a CSV. The tool finds duplicate sources, conflicting destinations, chains, loops, self-redirects, and malformed entries without fetching any URL.
Everything runs in this browser tab. The file is not uploaded, stored, or checked against the live web.
Findings
Rows to review before deployment
Export contains the findings below. It does not include or transmit unaffected rows.
No structural conflicts were found in the supplied map. Live response verification is still required.
| Severity | Row | Source | Destination | Finding | Detail |
|---|
Input
Literal source and destination pairs
Use headers such as source/target, from/to, old_url/new_url, or origin/destination. Headerless two-column CSV also works. Relative paths and absolute HTTP(S) URLs are accepted.
Boundary
Map analysis, not live redirect verification
This catches contradictions inside the supplied map. It does not request the source or destination, execute regex or wildcard rules, inspect server precedence, or prove the production response.
Need production verification?
A clean map can still fail at the server, CDN, or application layer.
I can compare the intended map with live status, Location headers, canonical output, internal links, and sitemap state before or after release.