PHASE 01
Map what exists
Record old URLs, valuable pages, files and search data before the old system disappears.
- URL inventory
- Content baseline
- Restorable backup
Launch control / 01
A new website should launch with its history intact
A redesign is ready only when old URLs, search signals, forms, DNS and real devices have all been checked. This site turns that release work into a sequence you can inspect.
Release sequence
Move through the launch in order
PHASE 02
Prepare the route
Match every old address to a relevant destination and test the final response before launch.
- One-hop redirects
- Canonical host
- Real 404 responses
PHASE 03
Watch the launch
Verify forms, indexing and server behaviour on launch day, then follow evidence for 30 days.
- Live-device check
- Search Console
- Measured follow-up
Operator briefing
Decisions before buttons
Choose the route that matches your launch
A first website, a replacement on the same domain and a move to a new domain have different risks. Start with the launch checklist, then use the migration or domain-change guide for the parts that apply to you.
Two tools run entirely in your browser
The pre-launch checklist keeps its state only when you ask it to. The 301 redirect generator turns URL pairs into nginx and Apache rules and warns about loops, chains and conflicting destinations. Your input is not uploaded.
A release is a controlled change
Keep the old system recoverable, make each step observable and define the signal that would trigger a rollback. That discipline protects both visitors and search visibility.
Related routes