URL Redirect Mapping Planner
Turn old and new URLs into a redirect map or a draft of Apache rules you can review.
One redirect per line: the old path, a comma, then the new path or full address. Example: /about-us.html, /about
Your result
List each old path and its new place. The checked redirect rules appear here.
Rules to add to your server
Permanent (301) redirects. Rules marked Skipped are left out of the file. Test a few old links after you install the rules.
How to use it
- Type old, new paths.
- Keep both paths rooted at /.
- Copy the lines.
Examples
- One redirect/old, /new Redirect 301 /old /new
- Two redirects/old, /new and /a, /b Redirect 301 /old /new Redirect 301 /a /b
- A nested path/blog/old, /blog/new Redirect 301 /blog/old /blog/new
Tool details and privacy
List old paths and their new places. The page checks for chains, loops, and repeats, then writes the 301 rules for Apache, Nginx, Netlify, or as CSV.
A text file of redirects is not the same as a server that follows them.
Options
- Old addresses can be full links; only their path is kept. New places can be paths or full links.
- A redirect that points to another redirect is sent straight to the final page.
Limits
- Nothing is installed on a server.
- Loops, self-redirects, and repeated old paths are left out of the file.
Privacy
What you type stays in your browser. Nothing is uploaded or saved on the server.
Questions
Are the rules installed?
No. Copy or download them.
What does /old, /new become for Apache?
Redirect 301 /old /new
Can the new place be on another site?
Yes. Use a full https address.
Are the paths uploaded?
No.