Redirect Mapper
Bulk-check your redirect map and see where every old URL actually lands. Free, no signup.
A redirect map is the spreadsheet you build before a site migration: every old URL, and the new URL it is supposed to point to. The trouble is that the map records intent. Once the rules are live, the only way to know they did what you meant is to request each old URL and watch where it comes out. That is the job this redirect mapper does.
Paste a plain list and you get the current destination for each URL. Paste the whole map as old,new pairs and you get something a bulk status checker cannot give you: a mismatch flag on the rows that redirect perfectly well to the wrong page. The redirect map tool also marks the chains and loops hiding behind a healthy 200, and shows the hop count so you can tell a clean 301 from a rule that fires three times before it settles.
How it works
- 01
Paste the old URLs
One per line. A bare URL tells you where it currently goes. Add a comma and the destination you expect (old,new) and the tool checks the map itself, not just the redirect.
- 02
Run the map
Sitewell requests each old URL and follows every 301 and 302 to the final response, recording the status code and how many hops it took to get there.
- 03
Fix the red rows
Mismatches and 404s are what cost you rankings. Chains are slower but survivable. Export the table as CSV and hand it to whoever owns the redirect config.
Frequently asked questions
- What is a redirect map?
- It is a list pairing every old URL with the new URL that should replace it. Teams build one in a spreadsheet before a site migration and hand it to whoever writes the server config or the CMS rules. The map describes what should happen. This redirect mapper checks what did happen, by requesting each old URL and comparing where it lands against where the map said it should go.
- What does the mismatch verdict mean?
- You gave an expected destination in an old,new pair and the URL landed somewhere else. Usually that means a typo in the config, an earlier rule that fires first and wins, or a second redirect sitting on the new URL that moves it again. Mismatches are the reason to use a redirect mapping tool rather than a plain status check: the redirect worked, it returned a healthy 200, it just went to the wrong page.
- How is this different from the Redirect Checker?
- The Redirect Checker traces one URL and shows you every hop in the chain, which is what you want when you are debugging a single strange redirect. The mapper is built for volume. It runs up to 200 URLs at once and gives you one verdict per row instead of a full trace, so you can scan a whole migration in a single pass.
- Why do redirect chains matter?
- Every hop costs another round trip for the visitor, and Google stops following after a handful of them. A chain usually means an old rule and a new rule are both firing on the same URL, which is easy to miss because the page still loads fine. Our guide on redirect chains and loops covers how to collapse them.
- How many URLs can I check at once?
- 200 per run, free, with no account. If your redirect map is bigger than that, split it into batches and run them back to back. The tool is rate limited to a few runs a minute because each row can mean several requests.
- Do you store the URLs I check?
- No. The URLs are processed to return your results and are not tied to an account. We do not sell your data or reuse the URLs you check for anything else.