Redirect Map Generator
Generate one-to-one redirect maps for site migrations.
Old URLs
New URLs
Mapping
Start here · Why auto-generate redirect maps?
Migrations break internal and external links when URLs move. A redirect map lists each legacy URL and its permanent destination.
Paste two columns: legacy URLs on the left and launch URLs on the right. The matcher scores pairs using exact path equality, final slug equality, or stopword-stripped token overlap.
Export buttons format the same pairs for nginx rewrite rules, Apache Redirect lines, Netlify _redirects, or a CSV with confidence scores for QA.
When to use this tool
- Domain or path replatform
Drop crawl exports before and after information architecture work, then review anything tagged manual review.
- Agency handoffs
Ship a CSV with confidence scores so engineering can script imports and marketing can spot risky fuzzy matches.
- Staging smoke tests
Compare staging hosts once paths stabilize, knowing hostname differences still need human verification.
- Microsite merges
When legacy microsites collapse into one hub, token overlap often surfaces near matches faster than eyeballing spreadsheets.
Examples
Walk through these with the form above — they are practice scenarios, not live data.
Slug preserved, folder changed
Try this
Old /blog/topic-name versus new /guides/topic-name with identical final slug.
What to look for
Expect Slug match confidence near 0.8. Confirm the content truly matches before enabling the redirect.
Ambiguous tokens
Try this
Two new URLs might partially overlap one old URL. Check the suggested new_url column for ties.
What to look for
Rows without a confident target show No match — manual review. Resolve them before export.
Short tutorial
Follow in order the first time you use the tool; later you can skip to the step you need.
- Step 1 — Normalize URL lists
One HTTPS URL per line, trimmed. Include trailing slash consistency your server expects.
- Step 2 — Paste old versus new
Left textarea is legacy, right textarea is destination inventory.
- Step 3 — Read confidence and reason
Exact path rows are safe. Token similarity rows need editorial confirmation for intent match.
- Step 4 — Export the right format
Pick CSV for spreadsheets, nginx or Apache for servers, Netlify for static hosts.
- Step 5 — Test hops in staging
Use Post-Migration Auditor or curl loops to ensure each 301 lands once with the expected HTML.
More detail
New here? Skim Start here first, then run one Examples scenario in the form above.
Redirect Map Generator does one job: generate one-to-one redirect maps for site migrations. It lives under Technical SEO on SEOToolkits, where the beginner idea is simple: Technical SEO keeps pages crawlable, indexable, fast enough, and understandable to search engines.
FAQ
- Will nginx exports always work?
- They assume paths parse as URLs. Escape or edit special characters your config requires.
- Why are matches missing?
- Very different slugs or non-Latin tokens may score zero. Add manual rows to your spreadsheet instead.
- Does it handle regex or wildcards?
- No. Each line is a concrete old URL paired to one new URL unless you edit exports externally.
- Can I chain redirects?
- Aim for single-hop 301s. Chain detection belongs in redirect audits, not this generator.
Related tools
Same workflow cluster on SEOToolkits — open another module without leaving context.
Redirect Chain Checker
Find chains and inefficient hops in your 301/302 graph.
Post-Migration Auditor
Compare pre/post-migration crawls for regressions and 404s.
Canonical Checker
Validate canonical tags across a domain for consistency.
Broken Link Checker
Crawl a site for 4xx/5xx links across pages and assets.