Free website migration tool · no signup
MAP IT.
THEN PROVE IT.
Map every old URL to its new destination, review uncertain matches, export deployable 301 rules, then verify the live redirect chain after launch.
Plan the moveAuto-map · confidence · human review
Export 301 rulesCSV · Netlify · Nginx · Apache
Verify the launchStatus · hops · destination · final response
Website Migration Redirect Mapper
OLD URLS.
NEW HOMES.
Paste one URL per line. Add an optional page title after a tab if you have crawl data or an export. Matching stays in this browser; live validation only runs when you explicitly request it.
Old URLs
Pages that need a permanent destination after the migration.
New URLs
The destination set from the new site, staging sitemap or crawl.
Redirect review queue0 mappings
| Old URL | Suggested destination | Confidence | Why | Risk |
|---|
Review anything marked Review or Low before export.
Redirect launch plan
SHIP IT.
THEN CHECK IT.
Weak / risky mappings
| Old | Target | Why review |
|---|
Post-launch proof
Validate the live redirects
After the rules are deployed, check up to 100 mapped public URLs. We follow the HTTP redirects server-side and compare the final destination with the plan above.
Website migration control
A MAP IS ONLY
HALF THE JOB.
The map records where every old URL should go. The validator checks what the live site actually does. Keeping both together catches chains, temporary redirects and wrong destinations that a spreadsheet alone cannot prove.
Match intelligently
Compare paths, slugs, tokens and optional page titles. Show confidence and ambiguity instead of silently pretending every fuzzy match is correct.
Deploy cleanly
Catch self-redirects, avoidable chains, homepage dumping and suspicious many-to-one mappings before exporting 301 rules.
Prove the launch
Request the old URLs after launch and verify permanent status, hop count, final destination and final HTTP response.
Questions
BEFORE YOU
FLIP THE SITE.
Redirects are infrastructure. Review high-value pages manually and validate the live behaviour after deployment.
Do my URL lists leave the browser?
No during mapping. When you click live validation, the selected old and intended target URLs are sent to the validator because a server has to request those public URLs to observe the real redirect chain.
Should every suggested match be accepted automatically?
No. High confidence means the URL/title evidence is strong, not that the pages are semantically identical. Review business-critical pages and anything marked Review or Low.
Should permanent migrations use 301s?
For genuinely permanent moves, 301 or 308 is normally the appropriate HTTP signal. Temporary 302/307 redirects are flagged for review during live validation.
Does passing the validator guarantee SEO rankings?
No. It proves the observed HTTP redirect behaviour at that moment. Search indexing, canonicalisation, internal links, sitemaps and ranking outcomes still need separate migration checks.