Direct answer
A website launch checklist should confirm that the site is usable, mobile-friendly, fast enough, secure, trackable, crawlable, backed up and aligned to the original business goals. It should include content checks, forms, links, redirects, SEO basics, analytics, privacy requirements, backups, browser testing, accessibility checks and a post-launch monitoring plan.
Going live is not the same as being launch-ready.
The real problem
Website launches often focus on whether the site looks finished. The pages are designed, the logo is in place, the images are loaded and the homepage feels ready.
But a site can look finished while important launch risks remain hidden.
Forms may not send. Mobile layouts may break. Old URLs may disappear. Analytics may not track enquiries. Metadata may be missing. Redirects may be wrong. Backups may not exist. Search engines may be blocked. Privacy pages may be incomplete. The client may not know how to update the site after launch.
A launch checklist protects the site from avoidable failure.
The useful distinction: live vs launch-ready
A live website is accessible to users.
A launch-ready website has been checked against the things that matter after users arrive.
Launch readiness means the site can be used, found, measured, maintained and recovered if something goes wrong.
That requires more than design approval.
What to include in the checklist
1. Content check
Review every important page for accuracy, spelling, outdated claims, missing sections, broken formatting, duplicated copy and placeholder text.
Check names, phone numbers, email addresses, service descriptions, pricing cues, team bios and location details.
2. Mobile and responsive check
Test the site on real mobile sizes, not only desktop previews.
Look at menus, forms, buttons, images, spacing, tables, headings and sticky elements. Many launch problems appear only on smaller screens.
3. Forms and enquiry paths
Submit every form before launch.
Check that notifications arrive, confirmation messages make sense, required fields work, spam controls do not block real users and the correct person receives the enquiry.
4. Links and navigation
Click every main navigation item, footer link, button, internal link and important call to action.
Broken links create trust problems and may block conversions.
5. SEO basics
Check page titles, meta descriptions, headings, indexability, sitemap, robots settings, URL structure, internal links and redirects from old pages.
If the site is replacing an existing site, map important old URLs to relevant new URLs. Do not simply delete pages that have search value.
6. Analytics and conversion tracking
Install and test analytics before launch.
Track the actions that matter: form submissions, phone clicks, email clicks, booking clicks, downloads or key CTA events. Without tracking, the business cannot judge whether the new site is working.
7. Performance check
Check whether pages load acceptably, especially on mobile.
Large images, unnecessary scripts, weak hosting, too many plugins or heavy page-builder sections can slow the site down before it even launches.
8. Security and SSL
Make sure HTTPS works correctly, SSL certificates are valid, admin accounts are protected, plugins and themes are current, and unnecessary users or temporary access accounts are removed.
9. Backup and rollback
Create a backup before launch and know how to restore it.
If the launch involves migration, DNS changes or a major rebuild, have a rollback plan. A launch is less stressful when recovery has been considered before something breaks.
10. Legal and privacy basics
Check privacy policy, cookie notices where needed, terms, POPIA or other relevant compliance content, contact details and data collection statements.
This is not a substitute for legal advice, but missing basics should not be ignored.
11. Browser and device testing
Test major browsers and common devices. Look for layout breaks, font issues, animation problems, menu behaviour and form usability.
12. Post-launch monitoring
After launch, monitor uptime, forms, analytics, search indexing, redirects, speed and user feedback.
The launch does not end when the site is visible. The first few days are part of the launch process.
Common mistake
The common mistake is treating the checklist as a last-minute admin task.
A launch checklist should influence the project earlier. If analytics, redirects, proof, content, forms and maintenance are considered only at the end, they become rushed fixes.
A better approach is to design with launch readiness in mind.
When this does not apply
A very small landing page may not need the same depth of checklist as a large WordPress site, ecommerce site or migrated business website. But the basics still apply: content, forms, links, mobile, tracking, security and recovery.
The checklist should match the risk of the site.
Soft next step
Before launching a website, ask what would be costly if it failed on day one.
Then check those items first.
A good launch checklist is not about perfection. It is about preventing avoidable problems before the public version goes live.