PHASE 01
First website
There is no old URL history, so the focus is discoverability, trust and reliable contact paths.
- DNS and TLS
- Indexability
- Forms and business details
Mission profile / 06
Not every new website is the same kind of launch
A first site, a redesign and a domain move may look similar on launch day, but they require different URL, server and search handovers.
Release sequence
Move through the launch in order
PHASE 02
Replacement website
The domain stays, while platform, hosting or URLs change. Existing paths must be preserved or redirected.
- Old URL inventory
- Redirect map
- Content parity
PHASE 03
New domain
Both websites and their certificates must remain available while signals move to the new address.
- Old domain retained
- Cross-domain redirects
- Search Console handover
Operator briefing
Decisions before buttons
A redesign can be a migration
If URLs, rendering, hosting or content structure change, the release has migration risk even when the domain and visual identity stay the same. Name those changes explicitly before setting the launch date.
Keep the path when it still describes the page
Changing every URL for style alone creates work without helping visitors. Preserve useful addresses where possible and redirect only when the information architecture really changed.
Define completion before launch
Completion should include live response checks, received contact messages, final metadata, valid certificates and a recorded baseline. A visual sign-off alone does not cover those conditions.
Related routes