Launch Acceptance Checklist: Twenty Technical Checks Before Going Live

Domain, SSL, redirects, 404s, sitemap, forms, mobile, speed and backups: checking each before launch is far cheaper than firefighting after.

Launch Acceptance Checklist: Twenty Technical Checks Before Going Live

The site is finished, the client glances at it, says it looks good, and it goes live. Three months later: the non-www version fails, form emails never arrive, images overflow on mobile and Google has indexed nothing. All of it could have been caught in two hours before launch.

Domain and DNS (4 items)

  1. Primary domain fixed, with non-www 301 redirecting to www or the reverse, keeping one entry point. 2. DNS propagated and reachable domestically and abroad. 3. Any legacy domains 301 to the new one so authority is not split. 4. MX records untouched and corporate email working.

Security and performance (4 items)

  1. SSL installed correctly, http redirecting to https, no browser warning. 6. Certificate valid for at least a year with an expiry reminder. 7. CDN enabled site-wide, static assets served from the CDN hostname. 8. First screen loads within three seconds, images in WebP under 100KB each.

Pages and links (5 items)

  1. Every navigation link resolves, zero 404s. 10. A custom 404 page exists with links back to home and main sections. 11. Page depth under three levels, key pages reachable within three clicks. 12. Pagination, breadcrumbs and back-to-top behave correctly. 13. Site search, if present, returns accurate results.

Forms and conversion (3 items)

  1. Inquiry forms submit and email notifications arrive; test with an external mailbox rather than only internally. 15. Required-field validation and success messages work, and submitted content is not wiped on error. 16. Every page has a visible inquiry entry and contact details appear in the footer.

SEO basics (4 items)

  1. Each page has unique TDK, with no empty or duplicate titles. 18. sitemap.xml is reachable and covers main pages, robots.txt does not block the site. 19. Structured data for Organization, Product and Article validates without errors. 20. Submitted to Search Console and Bing Webmaster Tools with analytics installed.

How to run it

Turn the twenty items into a sheet: the builder self-checks the day before launch, both sides review on launch day, and a spot check follows a week later. Only all three together guarantee more than a good first minute.

An easily forgotten close-out

Immediately after launch, take a full backup of files and database and verify it can be restored. Many incidents happen not during development but during the first content edit.

Compiled by the aibolg team from project practice and public industry material, for reference only.
← Back to listContact us →

Related Articles