What does the redirect map generator do?
It turns two URL lists into a reviewed, permanent redirect map in one of four formats. Paste every URL from the old site in the first box and every page on the new site in the second, as full URLs or paths. The tool lists each old URL with its suggested destination and a confidence label, and you change any destination from a dropdown before you export.
A redirect map is the single most important document in a migration: it decides whether old links, bookmarks and rankings land on the right page or on a 404. Our redirect map guide explains why, and the 301 redirect map template shows the columns teams use when they build one by hand.
How does the URL matching work?
The matcher compares paths, not page content, in three passes. An identical path is a perfect match. The same final slug, ignoring extensions like .html or .php, is the next best. Otherwise it blends the letter-pair similarity of the two slugs, which catches rewording and typos, with the share of path words the two URLs have in common.
Label | What it means | What to do |
|---|---|---|
Same path or slug | The path or final slug is identical | Usually right; spot-check it |
Close match | Strong overlap in slug and path words | Open both pages and confirm the topic |
Weak match, check it | Some overlap, possibly coincidental | Pick the right page by hand |
No match, sent home | Nothing in common with any new URL | Choose a relevant page, or no redirect |
Before matching, it lowercases paths, decodes escaped characters, drops trailing slashes and ignores query strings. Duplicate lines are removed. Each dropdown lists every new URL, the home page and a No redirect option, for pages you're deliberately retiring.
Which export format should you use?
Use the format your new host reads, and the CSV for your records and for platforms with a redirect importer. Every format lists sources as paths. A destination keeps its domain only when the old and new URLs are on different domains, so a domain change produces absolute destinations.
Format | File | Use it for |
|---|---|---|
CSV | redirects.csv (old_url, new_url, status) | Spreadsheet review and platform importers |
_redirects | One line per rule: source, destination, 301 | Netlify and Cloudflare Pages |
Next.js | An async redirects() array with permanent: true | next.config.js or next.config.ts |
vercel.json | A redirects block with permanent: true | Any project deployed on Vercel |
In Next.js and Vercel, permanent: true sends a 308 rather than a 301; Google's documentation treats both as permanent redirects. Paths for those two formats are escaped, because characters like parentheses and colons are pattern syntax there. Copy the output or download the file. See Next.js redirects for where the array goes, and the Webflow 301 redirects and Framer redirects guides for no-code platforms, whose settings and importers change, so check their current docs.
How do you build a complete redirect map?
Start from every URL that has traffic, links or rankings, not just the pages in your navigation. The tool can only match what you paste, so the old list decides the quality of the map.
Collect the old URLs
Combine your sitemap, a crawl of the live site and the pages with clicks or backlinks in Search Console and your SEO tool.
List the new URLs
Export every page on the new site, including blog posts and CMS items.
Paste, match and review
Check every match, starting with the weak ones. Open both pages when the topic isn't obvious.
Export and deploy
Add the file or array to the new site and deploy before or at the moment you switch DNS.
Test the old URLs
Request a sample of old URLs and confirm each returns one permanent redirect to a page that loads.
Hypothetical example: a 40-page WordPress site moving to Next.js
For example, suppose a startup moves a 40-page WordPress site to Next.js. Old blog posts live at /2023/04/post-name and new ones at /blog/post-name, so the matcher finds them by identical slug. Services pages were renamed, so /services/web-design matches /services/website-design as a close match. Three old category archives have no equivalent and come back as weak matches; the team sends one to the blog index and marks the other two as no redirect. They export the Next.js array, paste it into next.config.ts and test twenty old URLs after launch.
What mistakes break a redirect map?
Chains, loops and missed URLs cause most post-migration traffic drops. Google's documentation says Googlebot follows up to 10 redirect hops, but every hop slows users and dilutes the signal, so point each old URL straight at its final destination. The generator does this by design and leaves out any row where the source equals the destination.
- Old redirects left in place: merge existing rules into the new map so nothing points at a URL that now redirects again. Read redirect chains and SEO.
- Temporary redirects: 302s and 307s for a permanent move send a weaker signal. Use 301 or 308.
- Forgotten URLs: images, PDFs and old campaign landing pages often carry links too.
- No monitoring: watch 404s and indexing for the weeks after launch, as our post-migration SEO monitoring guide describes.
When should you get help with a migration?
Get help when the site has hundreds of URLs, a domain or structure change, or a lot of organic traffic at stake, because the map is where those migrations go wrong. The full website migration SEO checklist covers everything around the map.
Our website package is $8,000 for up to 6 pages, with copywriting, custom design, a Next.js build, a CMS and animation. Migration work is scoped on the intro call, and we include redirects and SEO checks in any migration we take on. See our website migration service. The next step is a free 30-minute call.
















