Guide
Validating redesigns and migrations
Use a redirect map to verify nothing breaks when URLs change.
4 min read
Import your redirect map
In the project's Settings drawer, open Migration Validation and paste your redirect map: one source and target URL pair per line. This is the list of old URLs that must permanently forward to their new homes.
What the audit verifies
Each mapped redirect is followed and checked: it must use a permanent 301 or 308, land on the expected target, resolve in one hop where possible, return 200, avoid soft-404 pages, and keep the destination indexable with a sane canonical.
Catch what the map missed
Beyond the configured map, audits also observe redirects encountered while crawling: chains, loops, and temporary 302s that should be permanent all surface as findings.
Re-run after launch
Run an audit immediately after the migration goes live, then again a few days later. Caches, CDNs, and stale sitemaps often surface a second wave of issues once real traffic hits.