Redirect Map Generator
Build Apache, Nginx or CSV redirects from a list, with loops and chains caught first.
About this tool
Paste `old | new` pairs and get redirect rules for Apache, Nginx, or a CSV for a platform that imports one.
Before writing anything it checks the map against itself. A URL redirecting to itself is an infinite loop the server will serve without complaint. A chain of A→B→C wastes a round trip on every visit and can be flattened to two direct redirects — this tool flattens it and tells you. A cycle is refused outright rather than emitted.
Common questions
301 or 302?
301 for a permanent move — it passes ranking signals and gets cached by browsers. 302 for a genuinely temporary one. Using 302 for a permanent move is a common and expensive mistake, since signals stay with the old URL.
Why flatten chains?
Every hop is a round trip before anything renders, and crawlers give up after a handful. A→B→C should be A→C and B→C, which this tool writes for you.
Do redirects lose ranking?
A single 301 to a genuinely equivalent page passes signals essentially intact. What loses ranking is redirecting everything to the homepage, which is treated as a soft 404 because the destination does not answer the original query.
Where does this configuration go?
Apache rules go in .htaccess or a virtual host block. Nginx rules go in the server block. Test on staging first — a wrong redirect rule can take a whole site offline.