Website Launch Checklist: 45 Checks Before and After Going Live

Decide whether the site should generate calls, WhatsApp enquiries, forms, purchases, bookings, applications or another measurable action.

Visitors should be able to reach important services, products, locations and contact options without understanding your internal company structure.

Prioritise homepage, service pages, product pages, contact information, pricing, policies and conversion pages.

Phone numbers, email addresses, WhatsApp, addresses, hours and legal/business names should be consistent.

Search for lorem ipsum, sample testimonials, template pricing, demo images, test products and temporary links.

Confirm the business is allowed to use the images, logos, fonts, videos and other media included in the site.

Depending on the business, this can include privacy, terms, refunds, shipping, disclaimers, cookie information and required regulatory disclosures.

Decide who can update pages, publish new content, approve changes and maintain factual accuracy.

Review navigation, hero sections, buttons, forms, accordions, tables, sliders, sticky elements and popups at real mobile widths.

Buttons should be visible, understandable and connected to the intended next step.

Verify the correct number opens and that mobile visitors can act without copying contact details manually.

Body copy, headings, form labels and buttons should remain legible without zooming.

Important navigation and controls should remain usable for visitors who do not rely on a mouse.

Describe useful images appropriately while leaving decorative visuals out of unnecessary keyword-heavy alt text.

Do not stop after seeing a success message. Confirm the enquiry reaches the correct inbox or CRM.

The visitor should know the submission worked and what will happen next.

Where relevant, check cart, checkout, payment, confirmation email, tax, shipping, booking availability and account flows.

Protect forms without creating unnecessary friction for genuine visitors.

Make sure someone is responsible for monitoring and responding to incoming enquiries after launch.

Important pages should have distinct intent instead of several URLs competing for the same topic.

Titles should accurately describe the page and remain distinct across important URLs.

The main topic should be obvious and supporting sections should help users scan the page logically.

Canonical tags should reference the intended production URLs, not a staging environment or obsolete domain.

Production should not inherit development controls that prevent indexing.

Make sure important resources are not unintentionally blocked.

The sitemap should contain canonical, indexable production URLs you actually want search engines to discover.

Important service and conversion pages should receive useful contextual links and not be buried several clicks deep.

Schema should match visible page content and real business entities. Validate relevant markup before relying on it in production.

Prioritise high-value templates and mobile performance rather than chasing one perfect score on a single page.

A new site should not ship with oversized hero images and unnecessary media weight.

Analytics, chat, ads, videos and marketing tools can materially affect page responsiveness and loading.

Check certificates, forced HTTPS behaviour and mixed-content warnings.

Crawl the production-ready site for broken internal links, missing assets and incorrect navigation destinations.

Before launch, know how the site can be restored if a deployment causes a serious issue.

Confirm the live domain is sending data and that internal/test traffic is understood.

Track the business actions that matter: form submissions, calls, WhatsApp, checkout, booking or other meaningful actions.

Add the correct property and make sure the business controls access.

Submission does not guarantee immediate indexing, but it helps Google discover the URLs you want crawled.

Save initial traffic, impressions, conversions and performance so future changes can be measured against something real.

Check the production domain in a fresh browser session and on mobile data where practical.

Test the most commercially important journeys after launch—not only in staging.

Confirm they return 200, use the intended canonical, are indexable and load the correct metadata.

Make sure live visits and conversion events are arriving as expected.

A launch can expose capacity, PHP, database or integration problems that did not appear during lower-traffic testing.

Keep one list of what needs correction, who owns the fix and whether the issue blocks marketing activity.