Free tool - nothing leaves your browser

Redirect Map Checker

Paste your planned redirects. Find conflicts, loops and unnecessary chains before launch.

1. Paste two columns
2. Check the map
3. Fix the rows it names

Your redirect map

Old URL and new URL, tab separatedTwo columns copied straight out of a spreadsheet: old_url then a tab thennew_url. A first row of old_url / new_url headers is optional. Every URL must be a full http:// or https:// URL - this tool never guesses a base domain, because guessing one is how a map gets checked against a site it does not describe.

Up to 2,000 data rows and 1 MiB of pasted text. Over either limit nothing is analyzed, so you never get a partial answer that looks complete.

How URLs are compared

URLs are compared exactly and case-sensitively, as the strings you supplied. Scheme, host spelling, explicit ports, path case, percent-encoding spelling, trailing slashes, query strings and their order, and fragments are all preserved and all significant.

Two consequences worth knowing

https://example.com and https://example.com/ stay two different strings here, so a map that mixes them is reported as two separate URLs. A host-only URL is valid and keeps the exact spelling you pasted.
A spelling the URL parser would reinterpret - a backslash, a /../ segment, a default :443 port, an upper-case host, a character that needs encoding - is reported for correction rather than silently rewritten.

What it does not model

It compares the spellings in your plan. It does not model server-specific rule matching, rule precedence, or any URL-equivalence rule your server applies.

Working through a full migration? Read URL inventory and redirect mapping for SaaS migrations.

Results

Paste a redirect map above, then choose Check map.

Need live migration checks? Explore the CoreAEX Diagnostic.

What this check cannot tell you

This checks the redirect plan you pasted, and nothing else. Every result is free and ungated, and your map stays in this browser tab: there is no upload, no account, no saved history and no request of any kind carrying what you pasted.

It cannot establish that these redirects are deployed, or deployed as written.
It cannot establish that the destinations exist, resolve, or return 200.
It cannot establish that the content or the indexability of a destination matches the old URL.
It cannot establish that your migration inventory is complete - a URL missing from the paste is invisible here.
It cannot model undocumented server normalization or rule precedence.