↳ RouteLedgerMIGRATION WORKSPACEHow it works ↗

CHECK THE ROUTE. KEEP THE VALUE.

Every old URL
needs a good landing.

Compare your sitemaps and redirect plan before you move. Find missing pages, broken mappings, and loops — in one clear report.

Check your migration ↗

◉ Files stay in your browser. No account needed.

YOUR MIGRATION, MAPPED

Start with your URL inventories.

LOCAL PROCESSING

Paste URLs, one per line, or a sitemap XML.

The URLs that will exist on your new site.

03 · Add your redirect plan Optional CSV

Use source,target headers with absolute URLs. We check the mapping you provide, not live HTTP responses.

Up to 50,000 URLs per list · 10 MB per input

A SMALL CHECK BEFORE A BIG MOVE

Make your migration easier to review.

01

Save the old inventory.

Keep a copy of the sitemap before changing your site. You can also paste URLs from a crawl export.

02

Compare the plan.

Add your new URLs and optional redirect CSV. Review missing destinations, conflicting rules, and multi-hop routes.

03

Verify on the live site.

Fix the issues, then test the real HTTP status codes after deployment. Monitor Search Console during the move.

Use a URL sitemap (urlset), not a sitemap index. Upload its child sitemaps separately. URL paths and query strings remain case-sensitive; fragments are ignored. Google’s migration guidance ↗