Map every old URL to its new home before you migrate. Paste both lists, fix duplicates, chains and loops, then export a clean CSV or ready-made server rules.
Output will appear here.
Runs entirely in your browser. Nothing is uploaded to any server.
301 redirects pass visitors and most link equity from old URLs to their new equivalents.
Every old link, bookmark and backlink keeps working after launch.
Chains slow pages down and loops break them; finding them in a spreadsheet is far cheaper than in production.
Use 301 (or 308) redirects for permanent moves so search engines transfer signals to the new URL, and 302 or 307 only for temporary changes. Map each old page to its most relevant new page rather than sending everything to the homepage, which search engines may treat as a soft 404.
A chain happens when a new URL is itself redirected again, for example A to B and B to C. Each extra hop adds latency and risk, so this tool can rewrite A to point straight at C. A loop, such as A to B and B to A, makes the page unreachable and is excluded from the output until you fix it.
RewriteRule lines with exact-match patterns and an optional query string condition.
Exact location blocks with a return statement for each old path.
Plain _redirects lines or a JSON array for Vercel-style configs and scripts.
Either works. Server rules need paths, so "Convert old URLs to paths" is on by default. New URLs are kept exactly as entered.
When detecting duplicates, chains and loops, the tool ignores letter case in the host, the www prefix and trailing slashes. The output keeps your URLs as written.
Both are permanent. 308 guarantees the request method is kept, which matters for form posts; 301 is the most widely used for page moves.
No. The map is built in your browser.
Always test redirect rules on a staging server before deploying, as server configurations vary.
More free tools from My Panda Toolbox.