
For teams moving a site, renaming pages or preparing a release while preserving working routes from old addresses.
Turn source-target pairs into deployment-ready Apache 301 redirects and make any old path left without a destination easier to spot.
After renaming several pages, a team prepares a file with old routes and their new destinations. They paste the pairs into the tool, retrieve Apache 301 rules and check that no important old address was missed before the release.
Input
/old|https://example.com/new
/contact|https://example.com/contactOutput
Redirect 301 /old https://example.com/new
Redirect 301 /contact https://example.com/contactThe conversion happens entirely inside your browser. The source-target pairs and the generated result are not uploaded outside. You can close the page once you have copied the rules.
The visible example uses an old address, a vertical bar and the new address, with one pair per line. You can also import a text, CSV, JSON, Markdown, XML or YAML file if your data is already structured that way.
No, this tool is designed to produce Apache 301 redirects. For another technology, you will need to adapt the rules manually or use a tool built for that specific configuration.
Review the generated output and check that every old address from your list appears with a target. If a line is skipped or malformed, fix the corresponding pair and run the generation again.