About this tool
Turn a reviewed old-to-new path map into one platform-specific file without treating incompatible wildcard or regex syntaxes as interchangeable.
Redirect Rule Generator converts a manually reviewed literal path map into bounded Netlify, Vercel, Apache, or Nginx configuration. It validates each source and destination, blocks duplicate sources and redirect cycles, warns about local chains, and exposes status and byte evidence before copy or download.
- Emits Netlify _redirects, Vercel vercel.json, anchored Apache RedirectMatch, or exact Nginx location blocks.
- Rejects incomplete, duplicate, unsafe, looping, or deployment-ambiguous source paths before exposing output.
- Distinguishes Vercel 308/307 behavior from the 301/302 statuses emitted for the other targets.
How to use Redirect Rules
Choose the deployment target, enter one exact incoming path and destination per rule, then select permanent or temporary behavior. Resolve every validation error, review chain and trailing-slash warnings, copy or download the configuration, and test it on the host that receives the old request.
When this tool is useful
- Emits Netlify _redirects, Vercel vercel.json, anchored Apache RedirectMatch, or exact Nginx location blocks.
- Rejects incomplete, duplicate, unsafe, looping, or deployment-ambiguous source paths before exposing output.
- Distinguishes Vercel 308/307 behavior from the 301/302 statuses emitted for the other targets.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Create a single 301 redirect
Example input
From: /old-pricing, to: /pricing
Expected output
Exact permanent mapping in the selected platform syntax
Vercel emits a 308 through permanent: true; Netlify, Apache, and Nginx emit 301 in this workbench.
Build a batch of redirects
Example input
/old-a -> /new-a /old-b -> /new-b
Expected output
Two validated exact-path mappings with graph and byte evidence
The workbench supports up to 200 manually reviewed rows; use platform bulk workflows for larger inventories.
Validation checklist
- Confirm the selected platform and its permanent or temporary status semantics.
- Avoid redirect chains by pointing old URLs directly to the final destination.
- Check duplicate sources, cycles, trailing slash, case, query, and destination behavior.
- Test status and Location headers in a staging environment before deployment.