PHASE 0–24h
Confirm critical paths
Test the public hostname, contact delivery, top landing pages and representative old URLs.
- 2xx and 3xx responses
- Form receipt
- No accidental noindex
Flight log / 10
The first 30 days after launch
A launch date starts the observation period. Check critical paths immediately, then move to a steady schedule based on errors, indexing and user behaviour.
Release sequence
Move through the launch in order
PHASE Week 1
Find patterns
Review crawl and server errors, indexing state and redirect misses without reacting to one isolated fluctuation.
- 404 and 5xx groups
- Coverage sample
- Device and browser checks
PHASE Day 30
Compare the baseline
Compare equivalent periods and document resolved issues, open risks and changes still being observed.
- Search queries and pages
- Conversion path
- Release notes
Operator briefing
Decisions before buttons
Watch the paths that create business value
Home-page uptime is not enough. Test the service pages people enter from search, the contact path, downloadable files and old URLs that previously received traffic or external links.
Separate noise from a technical fault
Daily traffic changes naturally. A repeated drop across important pages, a growing excluded-URL pattern or failed form delivery is actionable; one low day without another signal may not be.
Keep the launch record
Store the release time, configuration version, test results and major fixes. That record makes later changes easier to diagnose and gives the next migration a factual starting point.
Related routes