Website migration utility
Catch redirect-map mistakes before they reach production
A 301 mapping sheet is only useful when its routes are internally consistent and send the visitor somewhere relevant. Paste a two-column plan to detect obvious duplicate, self-referential, chained and looping mappings. Nothing is uploaded or fetched.
Inspect a proposed old-to-new mapping
Use safe root-relative paths, one `source,target` pair per row. Start with the sample below, which deliberately contains a chain and a loop. The tool does not contact your website; real destination relevance, headers and content must be reviewed separately.
What this checker can and cannot prove
This is a local consistency checker: it catches repeated source paths, self-redirects and linked rules that create a chain or cycle. It cannot confirm whether a mapped URL exists, whether a source returns 301 in production, whether the destination is indexable, or whether the replacement genuinely matches the user's original intent. It also does not process full CSV quoting, query-string commas or host-level www and HTTP rules.
For a release, combine these findings with an actual source URL inventory, real HTTP requests, a destination-content review and an authorised production retest. The migration mapping acceptance guide provides the wider test contract and a downloadable spreadsheet.
Official source: Google's site move guidance.
Discuss a migration mapping problem