Launch day is where a migration plan meets real traffic. A short checklist helps the team verify the public site, important customer paths, and search signals before small issues become invisible losses.

Assign each check to a person and record the time, result, and follow-up owner.

Before the switch

Confirm the backup, deployment artifact, domain and DNS access, certificates, environment variables, redirects, analytics, forms, integrations, support contacts, and rollback plan. Freeze unplanned content changes during the cutover.

Check the public configuration

Verify the domain, HTTPS, canonical URLs, robots rules, XML sitemap, favicon, social previews, status codes, and error pages. Make sure staging protections are not accidentally blocking production.

The redirect audit checklist covers URL mapping and chains.

Test real customer actions

Submit contact and quote forms, call links, bookings, payments, account login, search, filters, file uploads, and newsletter actions. Confirm the visitor sees a useful response and the team receives the right record.

Run a crawl and mobile pass

Crawl representative URLs, check broken links and redirects, open important pages on a phone, review images, test keyboard access, and confirm the new templates render the content that matters.

Watch the first hours

Monitor uptime, forms, calls, analytics events, server errors, Search Console signals, redirects, and support messages. Keep the previous version available until the critical checks are complete.

The relaunch checklist provides a broader pre- and post-launch process.

Planning a migration without a launch owner? Ask Vertinus to turn the cutover into an assigned checklist.