Full Launch Checklist for a New B2B Website
Key takeawayA master sheet covering six layers: domain, certificate, templates, forms, analytics and backup. Use it as the final gate before a new site opens to the public, and run it twice: three days before launch and again on launch day. Only go live with paid traffic when both runs pass.
Industries and use cases
- First public opening of a new domain for a B2B export site
- After migrating from a staging server to the production server
- First release after switching CMS or theme templates
- Taking over a legacy site and confirming whether it is launch-ready
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Domain resolution live | Apex and www both return 200, DNS records point to the target server IP and lookups from multiple regions agree | High | Set records 24 hours before launch and cross-check with lookup tools in at least two regions; avoid editing while testing. |
| HTTPS certificate chain | No browser security warning, certificate covers apex and www, more than 60 days of validity remaining | High | Install intermediate certificates, force HTTP to HTTPS site-wide and confirm the redirect fires only once. |
| Home page and duplicate entry points | Home returns 200 and duplicate paths such as /index.php or /home 301 to the root domain | High | Configure canonical redirects at server or CDN level so every entry point lands on one address. |
| robots.txt status | /robots.txt returns 200 with content type text/plain and contains no site-wide Disallow | High | Test environments often ship Disallow: /; replace it with production rules and re-crawl to confirm. |
| Sitemap reachable | /sitemap.xml returns 200, the XML is valid and the URL count matches the real page volume | Medium | Validate the syntax locally, open it in a browser to confirm no errors, then submit in Search Console. |
| Five template spot checks | One page each from home, category, product detail, contact and article templates returns 200 with intact layout | High | Review every template visually, especially inner pages where broken layout or empty modules appear only on detail views. |
| Mobile first screen | At 375px width there is no horizontal scroll, main content is visible within 3 seconds and the primary button is tappable | High | Test on a real device rather than a simulator and check whether the collapsed menu or sticky buttons cover body text. |
| Inquiry form loop | A test inquiry triggers a notification email within 5 minutes containing the source page, timestamp and every field | High | Test with an external mailbox, check the spam folder and read the error message shown when submission fails. |
| Analytics and webmaster tools | GA4 and Search Console are both verified, the sitemap is submitted and the status shows success | Medium | Verify ownership by DNS or HTML file; a verification file is easily deleted later. |
| Internal link spot check | A random sample of 50 internal links contains zero broken links and no chain longer than one hop | Medium | Crawl the site, export 4xx responses and multi-hop redirects, then fix them one by one. |
| Placeholder cleanup | No lorem ipsum, sample phone numbers, demo@ addresses, default theme copy or stock demo images remain | Medium | Search for common placeholder strings and replace product images with original or licensed assets. |
| Backup and rollback | A full file and database backup is taken before launch and restore steps are documented where the team can find them | High | Download one copy to separate storage and rehearse a restore at least once. |
Common misjudgements
- A working home page is treated as a finished launch: inner templates, form delivery and the certificate chain usually fail only on secondary paths or after a submit action.
- Slow DNS propagation is mistaken for a resolution error, and repeated edits extend the wait; wait for the TTL to expire and re-check instead.
- Leaving www and non-www both reachable splits one page across two addresses, so analytics and index data end up divided.
How to use this checklist
- Run in sequence with the domain and HTTPS verification sheet: clear the infrastructure layer first, then this sheet for content and conversion.
- Re-run before every major release; for routine changes only the template spot check and form loop are needed.
- Export the sheet as a shared team document and mark an owner and completion time for each line.
FAQ
How far ahead should a new site be checked?
Run the full sheet three days before launch to leave time for fixes, then re-check only the high risk items on launch day.
Which items can a non-technical owner complete?
Template spot checks, mobile device testing, form delivery and placeholder cleanup are doable alone; DNS and certificates are better handled with the hosting provider.
What comes after the checklist passes?
Watch crawl and index data for 48 hours after launch, then run the post-launch review sheet after one week.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
Brand Entity Review for AI Overviews and Answer EnginesRich Results Testing Workflow Before Site ReleaseDomain, DNS and HTTPS Verification for a New SiteFinal Pre-Publish Review for Content Used as an AI Sourcehreflang Configuration Review for Multilingual SitesNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.