PHASE 01
Paste the map
Use one old and one new address per line. A tab, arrow or semicolon can separate them.
- Up to 10,000 rows
- 410 for removed content
- Absolute or relative URLs
Routing console / 02
301 redirect generator
Paste old and new URL pairs. The generator validates the map, reports conflicts and produces nginx and Apache rules without sending the list anywhere.
Release sequence
Move through the launch in order
PHASE 02
Read the findings
Errors stop output. Warnings flag chains, soft-404 patterns, insecure targets and server limits.
- Loops blocked
- Duplicates blocked
- Chains identified
PHASE 03
Test on the server
Validate the configuration first, then check every old URL and its http and www variants.
- nginx -t
- One final hop
- Expected status and target
Local routing console
Build and inspect redirect rules
The URL map stays in this browser. Generated configuration still has to be reviewed and tested on the target server.
One pair per line. Separate columns with a tab, arrow, semicolon or two spaces. A first header row is allowed.
Validation
nginx
Apache / .htaccess
Operator briefing
Decisions before buttons
Permanent means 301 or 308
Use a permanent response for a lasting URL change. Both 301 and 308 are permanent signals; 301 is the widest default. A temporary 302 or 307 is appropriate only when the destination is genuinely temporary.
Every old address needs an explicit decision
Send an old URL to the closest relevant replacement. If there is no replacement, allow a real 404 or return 410. Sending unrelated URLs to the home page can confuse visitors and may be treated as a soft 404.
Browser tests are not enough
Browsers cache permanent redirects. Test with curl, inspect the response code and Location header, and confirm that each path reaches its final address in one hop.
Related routes