Collect old URLs from more than one source
Use the crawl, XML sitemap, CMS export, analytics, Search Console, important backlinks and known campaign or printed links. One source rarely contains every valuable address.
Runs privately in your browser
Turn an old URL inventory and a proposed site structure into an editable launch register. The tool suggests likely matches, flags obvious risks and exports a CSV—but leaves content decisions with you.
Read the result correctly
The same words in two URLs do not prove that both pages serve the same need. Preserve evidence, compare intent and treat every automatic suggestion as a starting point for approval.
Use the crawl, XML sitemap, CMS export, analytics, Search Console, important backlinks and known campaign or printed links. One source rarely contains every valuable address.
A person following an old bookmark should arrive at content that solves the same problem. Similar slugs can help discovery, but the page purpose decides the mapping.
After launch, request each old URL and confirm one permanent hop to the final destination. Reject loops, chains, staging targets, soft errors and unexpected homepage redirects.
Limits and next steps
Paste URL lists or upload TXT, CSV or XML sitemap files. The builder reads up to 500 unique URLs from each side inside your browser.
No. Suggestions use URL-path similarity. A person must compare the old content and new destination to confirm equivalent purpose and customer intent.
No. The pasted or uploaded lists and editable map stay in your browser. Only generic row counts may be measured in analytics.
No. Broad homepage redirects often hide missing content and create a poor experience. Choose a useful equivalent destination, intentionally merge content or use an appropriate retirement response.
A server-side permanent redirect such as 301 or 308 is commonly appropriate for a true move. The correct implementation depends on the platform and must be tested against the live response.
WANT A PERSON TO REVIEW THE RESULT?