Free tools

Free tool

Redirect map generator: match old URLs to new ones and export 301s

This redirect map generator builds the 301 redirect map for a site migration. Paste your old URLs and your new URLs, one per line, and it matches each old URL to the closest new one by path and slug. You fix any wrong match, then export a CSV, a Netlify or Cloudflare _redirects file, a Next.js redirects() array or a vercel.json block. It all runs in your browser.

MatchesChange any destination that's wrong. Send a page home only when nothing on the new site replaces it.
4 redirects, all permanent (301, or 308 in Next.js and Vercel)

Matching compares paths, not page content, so read every match before you ship it. Redirects point straight at the final URL, with no chains.

At a glance

  • Matches old URLs to new ones by path, slug and shared words
  • Every match is editable, including no redirect or the home page
  • Exports CSV, _redirects, Next.js and vercel.json
  • Runs in your browser; your URL lists aren't uploaded
  • ATQLeads
  • Update AI
  • LeanScale
  • CSSinc.ai
  • HeyInterests
  • JuPay
  • PowerPulse
  • WireFox
  • Reactive Growth
  • Minexa.ai
  • SmileJoy
  • LFG Business Group
  • ORBITX
  • Funnels.com
  • Sentipi
  • UNIVIT Research
  • LifeLink
  • Wolf Automation
  • Shaqir Hussyin
  • Q-TARO
  • MainPlume

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.

  1. 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.

  2. List the new URLs

    Export every page on the new site, including blog posts and CMS items.

  3. Paste, match and review

    Check every match, starting with the weak ones. Open both pages when the topic isn't obvious.

  4. Export and deploy

    Add the file or array to the new site and deploy before or at the moment you switch DNS.

  5. 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.

What our clients had to say

Pricing

Fixed prices for fixed scopes, agreed before we start, or a monthly retainer when you need a team on call. All prices in USD.

Website

A multi-page marketing site, written and designed by us, developed in Next.js and animated.

What’s included

  • Up to 6 pages, written, designed and developed
  • Custom design, never a template
  • Built in Next.js, fully responsive
  • Animations and interactions
One-time, up to 6 pages

$8,000

+$500 for each extra page
Book a call
4.92 on Contra · 11 reviews

Free 30-minute intro call, no commitment

Not sure yet? Try a week together.

One week of design and development, so you can see how we work before you commit.

$1,000Book a trial week

Frequently asked questions

Should I redirect every old URL?
Redirect every old URL that has a relevant replacement, plus any with traffic, backlinks or rankings. Pages with no equivalent and no value can return a 404 or 410 instead. What you shouldn't do is send all of them to the home page, because visitors land somewhere unrelated and search engines may treat those redirects as soft 404s.
What's the difference between a 301 and a 308 redirect?
Both are permanent. A 301 is the long-standing permanent redirect; a 308 is the newer version that also keeps the request method, which matters for form posts and APIs. Next.js and Vercel send a 308 when you set permanent: true. Google's documentation treats both as permanent, so either works for a migration.
Are my URL lists uploaded anywhere?
No. The matching and the export happen in your browser, and the URL lists you paste aren't sent to a server. When you download a file, it's generated on your device. That makes the tool safe to use with staging URLs or unreleased page names, but keep your own copy of the CSV, because the tool doesn't save your work.
Can it handle query strings and wildcard rules?
It matches and exports paths only, so query strings are dropped from sources, because each format handles them differently. It writes one literal rule per URL rather than wildcard or pattern rules. If a whole folder moved, such as /2023/04/post to /blog/post, you can replace many rows with a single pattern rule by hand, using your platform's syntax.
How long should redirects stay in place?
Keep them for as long as you can, ideally permanently. Old links on other sites, bookmarks and email archives keep sending people to the old URLs for years. Google's guidance is to keep redirects in place for at least a year, and there's little cost in keeping them longer on most platforms.

Ready to qualify better leads and boost brand perception?

We take craft seriously over at Designify Studio. We do deep research and do what we do best - pay attention to the smallest details and make sure we speak to the right audience.

Schedule Call