Browser tools
Redirect map checker for website migrations
Review the structure of your migration decisions before deployment. Check a map and an optional old-URL inventory locally; live websites are not fetched.
Review a redirect map
Use exact local paths. Required map headers: source_path,destination_path. Optional: decision,status_code. Decisions are redirect, keep or remove; a map without a decision column is treated as redirects. Add an old-URL inventory with a path or existing_path header to check coverage.
A worked review
The original synthetic map sends /old through /middle, has a loop between two paths and lacks a decision for /missing in the inventory. The reviewed example points the changed paths directly to /new, retains the contact path, records a removal decision and explicitly keeps the missing path.
Download the original map and the manually reviewed map. These decisions are fictional and illustrate the workflow; choose destinations for your actual content.
Use this inventory with the example: path, followed by one path per line: /old, /contact, /retired, /missing. The reviewed example has zero findings for that inventory under the supported checks.
What this review covers
- Map consistency Competing sources, unsupported paths, invalid decision/status combinations, loops and multi-hop chains.
- Inventory decisions Identify old paths without a valid unique keep, redirect or remove decision.
- Human review A finding points to a decision to inspect; the tool does not choose where your content belongs.
- Export Download a text review without uploading the map or changing your website.
Paths are case-sensitive and trailing slashes are distinct. Full URLs, query strings, fragments, patterns and dot segments are unsupported. Regex matching, live HTTP status, destination relevance and server configuration need separate verification.
Use it in a migration plan
Read the WordPress-to-Next.js planning guide and record the source of your old-URL inventory. Check real deployed responses after the reviewed rules are applied. A clean spreadsheet is only one part of launch verification.
For implementation, explore Next.js development or agency implementation support. The separate CSV cleaner can help with general file cleanup; this checker focuses on URL decisions.