Before a website goes live, run this launch checklist in order: prove every form delivers, check the site on a real phone, confirm Google can index it, set redirects from any old URLs, and verify backups and analytics work. Most launch-day disasters are boring — an enquiry form emailing a dead inbox, a 'coming soon' block left on indexing, a site with no backup — and every one of them is caught by an unglamorous hour of checking.
This checklist is the distilled version of what experienced teams run before flipping the switch, organised so a small business owner can work through it without a technical background. It assumes a new site or a redesign replacing an old one. If you want it as a printable document you can tick off at your desk, the shop's WordPress Business Website Launch Checklist is exactly that — this article is the full method behind it.
Content and Proofreading Checks (1–7)
1) Read every page aloud once — typos hide from eyes and confess to ears. 2) No placeholder text, lorem ipsum or 'TODO' survives anywhere, including footers and error pages. 3) Contact details are identical everywhere: phone, email, address, opening hours — and match your Google Business Profile. 4) Prices, service areas and claims are current; nothing promises what the business no longer offers. 5) Every image has alt text that describes it for someone who cannot see it. 6) Links all resolve — click every menu item, button and footer link; one 404 on launch day is a visitor lost. 7) Spelling of names, places and your own business name is consistent, including in page titles.
Forms, Email and Conversion Checks (8–13)
8) Submit every form yourself — contact, quote, booking, newsletter — and confirm the message arrives in the right inbox, not just that the site says 'thank you'. 9) Check the spam folder too; form notifications landing in spam is a silent business leak. 10) Test the thank-you page and any auto-reply email the visitor receives. 11) Click every phone number on a phone — it should dial. 12) Test online payments with a real small transaction if you sell anything. 13) Confirm enquiry notifications go to an inbox a human checks daily, not a legacy address. If your launch follows a build project, cross-check timing expectations against the realistic website timeline — launch checks belong in the schedule, not after it.
Where launch problems are usually found, by checklist area (illustrative share, %) — hover or tap each bar for details.
Mobile, Speed and Technical Checks (14–20)
14) Browse the whole site on your own phone: menus open, text is readable without zooming, buttons are tappable, nothing overflows sideways. 15) Test on the other platform too (borrow an iPhone if you are Android, and vice versa). 16) Run the homepage and one inner page through a speed test on a mobile connection profile; images are the usual culprit — the workflow for compressing images without losing quality fixes that before launch, not after. 17) The site works in private/incognito mode — no cookie-dependent breakage. 18) HTTPS padlock shows on every page with no mixed-content warnings. 19) The 404 page is friendly and links home. 20) Favicons and social-share images are set, so links shared on WhatsApp and social media show your branding, not a grey box.
SEO and Analytics Checks (21–27)
21) Search engines are allowed to index the site — the single most expensive launch mistake is a leftover 'discourage search engines' setting from development. 22) Every page has a unique title and meta description (the small business SEO checklist covers what good looks like). 23) The XML sitemap exists and is submitted in Google Search Console. 24) If this replaces an old site: every old URL that had traffic or links redirects to its new equivalent — build the redirect list before launch day from the old sitemap. 25) Analytics (for example GA4) is installed and you can see your own test visit in real-time reports. 26) Search Console ownership is verified for the business, not a developer's personal account. 27) One canonical domain is chosen — www or not, http redirects to https — and every variant lands on it.
| Check | How to verify in 2 minutes | Cost if missed |
|---|---|---|
| Forms deliver | Submit each form; watch the inbox | Lost enquiries from day one |
| Indexing allowed | Search Console URL inspection | Invisible on Google for weeks |
| Redirects from old URLs | Open 3 old bookmarks | Rankings and backlinks lost |
| Backups running | See a completed backup in the dashboard | No recovery after any incident |
| Analytics live | Real-time report shows your visit | Launch performance unmeasurable |
Legal, Security and Ownership Checks (28–32)
28) Legal pages exist and name the real business: privacy policy, terms, and cookie consent where your region requires it (the EU/UK/Spain rules are stricter than the US baseline). 29) A backup has run successfully at least once and you know where restores live. 30) Admin accounts are individual, with strong passwords and two-factor where offered — and the business owns the master accounts for domain, hosting and analytics. 31) Software, themes and plugins are updated to current versions on day one. 32) Someone has written down: where the site is hosted, when the domain renews, and who to call when it breaks. If that last item sounds trivial, you have never watched a business discover its domain expired.
None of these checks require deep skill; they require a list, an hour and honesty. Which is why the list exists — memory is not a launch process. For the printable, tick-box version with space for notes per check, the launch checklist in the shop mirrors this article check for check.
Launch Day and the Week After
Go live early in a working day, never Friday evening: the people who can fix things should be awake and available for the first hours. After switching, repeat the form test and the phone browse on the live domain (staging passes tests the live site can still fail), watch analytics real-time for your first real visitors, and check Search Console over the following days for crawl errors. Keep the old site's backup and redirect map untouched for at least a few months.
Then hand over to routine: the checks that keep a launched site healthy — updates, backups, uptime, content reviews — are a maintenance rhythm, not a launch event; our guide to website maintenance costs prices that rhythm for US readers, and the principles translate anywhere. More launch and growth guides live on the Asad Webs blog.
Want this as a printable worksheet for your desk? The WordPress Business Website Launch Checklist in the Asad Webs shop is the tick-box companion to this article.
Frequently Asked Questions
What is the most important check before launching a website?
Submit every form and confirm the messages arrive in a monitored inbox. A beautiful site whose enquiries vanish is worse than no site, because the business believes it is reachable when it is not.
How long does a launch check take?
About an hour for a typical small-business site if you work the list in order, plus time to fix what you find. That hour is cheaper than any single item on the 'cost if missed' list.
Do I need redirects if my site is brand new?
Only if something existed before — an old site, a previous domain, or pages that others have linked to. A truly first website on a fresh domain has nothing to redirect, but still needs the sitemap, Search Console and indexing checks.
Should I launch on a Friday to have the weekend to fix things?
No — launch early on a normal working day. Your host, developer and payment provider are all reachable then, and most launch issues surface within the first hours of real traffic.
What's the difference between this checklist and the shop version?
This article is the complete method, free. The shop version is the same checks formatted as a printable tick-box worksheet with notes space — for people who want the document on the desk during launch day.
Be the first to share a useful question or thought.