Review migration mappings
Check source and destination pairs before launch so old URLs point to the right new pages without obvious redirect loops.
Validate redirect mapping inputs before migration QA, SEO cleanup or launch checks.
These are the signals I would review manually when deciding what needs fixing first.
Review this area to understand whether it is helping or hurting growth.
Review this area to understand whether it is helping or hurting growth.
Review this area to understand whether it is helping or hurting growth.
Review this area to understand whether it is helping or hurting growth.
A little context makes the numbers more useful. Use these notes to understand where this tool fits inside content, SEO and website reviews.
Check source and destination pairs before launch so old URLs point to the right new pages without obvious redirect loops.
Permanent migrations usually use 301 or 308 responses, while temporary redirects are better for tests, campaigns or short-lived changes.
The checker highlights same-origin and cross-origin destinations, which helps QA domain moves, HTTPS changes and external redirects.
Redirect rules are parsed locally in your browser, so migration spreadsheets and client URL mappings are not uploaded.
Quick answers about how this tool works and when to use it.
No. It validates redirect rule inputs locally, including source URL, destination resolution, status code and likely loop risks.
Yes. Relative paths are resolved against the source URL origin so you can check common server and CMS redirect mapping formats.
For long-term URL migrations, 301 and 308 are the usual permanent redirect options. Temporary status codes are better for short-lived routing.
No. The validation, report copy and report download actions run in the browser without sending the URLs to a server.
Add a full source URL, destination URL or path and the expected redirect status.