Turn a list of old and new URLs into ready-to-paste redirect rules — and catch the mistakes first. Paste source and destination pairs or drop a CSV, and the planner finds redirect chains, loops, duplicates and self-redirects, collapses every chain to a single hop, and writes the rules for Apache .htaccess, Nginx, Netlify or Vercel. It runs in your browser.
| Code | Meaning | Keeps method |
|---|---|---|
| 301 | Moved permanently | No (usually becomes GET) |
| 302 | Found (temporary) | No |
| 307 | Temporary redirect | Yes |
| 308 | Permanent redirect | Yes |
When A redirects to B and B redirects to C. Each extra hop slows the page down and weakens the link signals passed to the final URL. The fix is to point A straight at C, which this tool does.
A path of redirects that leads back to where it started, such as A → B → A. Browsers give up with a too-many-redirects error. The tool blocks the download until loops are fixed.
301 (or 308) for permanent moves — they pass link equity. 302 (or 307) for temporary ones. 307 and 308 also keep the request method, which matters for forms and APIs.
Apache for .htaccess, Nginx for your server block, Netlify for a _redirects file, Vercel for vercel.json.
Yes. Copy the from and to columns (and optionally a code column) and paste — tabs, commas and spaces all work.
No. Everything is analyzed in your browser.
Redirect lists grow over years of migrations, and the two failures are invisible until production: chains, where a URL redirects to another URL that itself redirects, costing an extra round trip per hop and diluting the link signals search engines pass along; and loops, where the hops lead back to a URL already visited, which browsers abort with a too-many-redirects error. The planner reads one rule per line — source, destination and an optional status code, separated by spaces, commas or tabs, so two spreadsheet columns paste straight in — and builds a map of sources. It follows each destination through that map; a destination that is itself a source extends the chain, and reaching a URL already on the path is a loop. Paths are compared without the scheme and host and ignoring a trailing slash. Chains are collapsed so every source points straight at its final destination, and the collapsed rule stays temporary if any hop was a 302 or 307. Duplicate sources, self-redirects and unreadable lines are reported. Output is written for Apache, Nginx (exact-match location blocks or rewrite rules with the path regex-escaped), Netlify's _redirects and Vercel's vercel.json. It all runs in the page.