The goal is not merely to load the home page. The journeys that create an outcome must work: search, forms, login, checkout, email, analytics and integrations.
Preflight before the change window
Record scope, owners, timing, success criteria and rollback conditions. Freeze non-essential changes and take a verified backup of the environment that will be replaced.
The technical checklist covers production configuration, secrets, HTTPS, redirects, canonical and hreflang links, robots, sitemap, forms, email delivery, payments, analytics and consent.
- Approved scope, owners and communication channel
- Backup and tested rollback route
- Production configuration without test credentials
- Responsive, accessibility and browser checks
- SEO, redirects, structured data and sitemap
- Privacy, cookies and required legal information
Controlled DNS, SSL and production cutover
Plan DNS changes around TTL, existing records and dependencies such as mail, verification records and external services. Avoid changing unrelated systems in the same window.
After cutover, test the real public route from another network: certificate chain, HTTP redirects, static assets, APIs, forms, email and critical transactions.
The first 72 hours
Temporarily increase check frequency and monitor availability, logs, error rates, performance, submissions, orders and integrations. Alerts should route to an accountable owner rather than an unprioritised shared inbox.
Compare observations with a baseline and review user reports. Small fixes should follow the same controlled route so launch does not become a chain of rushed production changes.
- Synthetic checks for key pages and journeys
- Monitoring of 4xx, 5xx and browser errors
- Form, transactional email and checkout verification
- Performance and Core Web Vitals baseline
- Analytics and consent event review
From launch to steady operation
After the initial period, record findings, fixes and outstanding work. Establish the normal rhythm for updates, content changes, restore tests, security review and performance review.
Add new URLs to the sitemap and monitor search coverage. Discovery and indexing take time; the objective is a clean technical foundation and consistent observation, not repeated urgent submissions.
- Launch report and action list
- Normal maintenance calendar
- Backup and restore verification after cutover
- Search Console and analytics review
- Prioritised improvement roadmap