URL Redirect Mapper
Planning a site migration? Paste your list of old and new URLs and get redirect rules in the format your server needs: Apache Redirect lines, mod_rewrite rules, Nginx locations or a map, Netlify _redirects, Vercel JSON or CSV. Before writing them, the mapper checks for loops, chains, duplicate sources and pages that redirect to themselves, and can shorten chains automatically.
- Runs in your browser
- No sign-up
- Free to use
How to use URL Redirect Mapper
- Paste one redirect per line: old URL, then new URL.
- Leave the new URL out for pages that are gone (410).
- Choose the output format and the redirect type.
- Fix any reported problems, then copy the rules into your configuration.
URL Redirect Mapper features
Seven formats
Apache, mod_rewrite, Nginx location, Nginx map, Netlify, Vercel and CSV.
Loop detection
Finds rules that lead back to where they started.
Chain shortening
Points every old URL straight at its final destination.
Duplicate check
Reports old URLs with conflicting targets.
Gone pages
A line with only the old URL becomes a 410.
Query-string warning
Flags rules that path-only formats cannot match.
When to use URL Redirect Mapper
- Moving a website to a new URL structure.
- Merging two sites or sections.
- Cleaning up after deleting old content.
- Converting a redirect spreadsheet into server rules.
URL Redirect Mapper FAQ
Which redirect type should I use?
301 for permanent moves, which passes search ranking to the new URL. 308 if the method must be kept, for example for form posts. 302 or 307 only for temporary changes.
What is a redirect chain?
A redirect to a URL that itself redirects. Chains slow pages down and search engines may stop following them. The mapper shortens them so each old URL points directly to the final one.
What is a redirect loop?
Rules that send a URL around in a circle, so it never loads. The mapper reports and leaves out such rules.
When should I use 410 instead of a redirect?
When a page is gone and there is no equivalent. Redirecting everything to the home page is treated by search engines as a soft 404.
Do the rules handle query strings?
Apache Redirect, RewriteRule and Nginx location match the path only. For old URLs with parameters, use the Nginx map output or add a RewriteCond.
Is anything uploaded?
No. The rules are generated in your browser.
Redirects decide whether a migration keeps its traffic
When URLs change, every link, bookmark and search result pointing at the old addresses breaks unless the old URLs redirect to the new ones. A complete, correct redirect map is the single most important technical part of a site migration.
Most maps start in a spreadsheet with two columns. Turning them into server rules by hand is tedious and error-prone, and the errors are subtle: a rule that redirects a page to itself, two rules for the same URL with different targets, or a series of rules that form a chain or a loop. The mapper finds all of these before they reach the server.
Chains deserve particular attention. After several redesigns a site can have old URLs that redirect three or four times before reaching a page. Each hop costs time, and search engines may stop following long chains. Shortening them so every old URL points directly to its final destination is easy to do with a map and hard to do by eye.
Test after deploying. Request a sample of old URLs and check that each returns a single 301 to the right page. The Redirect Checker on this site traces chains hop by hop and confirms the result.