A website launch checklist helps you catch problems before customers encounter them. A page can look finished while its contact form sends messages nowhere, its mobile menu is difficult to use, or its live domain still blocks search engines. The safest launch is not just a design approval. It is a short, documented test of the things visitors need to do.
Decide who approves each part of the launch
Give every check a named owner and a clear pass or fail result. The business owner should approve wording, offers, contact details and legal information. The developer should verify hosting, forms, redirects and technical settings. Whoever manages marketing should confirm tracking and search setup. One person can hold several roles, but no critical check should be assumed complete because someone else probably handled it.
Use a shared document with four columns: check, owner, result and evidence. A screenshot or test submission is more useful than a vague “looks good.”
Check the content and customer journey first
Make the offer understandable
Read the homepage as a new visitor. Can someone tell what the business does, who it serves and what action to take? Confirm prices, service descriptions, opening information and contact details against the approved source. Remove placeholder text, sample testimonials and unfinished sections.
Test the actions that bring in business
Submit every contact and enquiry form using a safe test address. Confirm that the message reaches the intended inbox, that validation works, and that the visitor sees a useful confirmation. Test telephone and email links on a phone. For an online store, use a permitted test payment method to verify the cart, shipping charges, checkout, confirmation and order notifications. Do not place a real charge merely to test a launch.
Check accessibility and mobile usability
Navigate important pages using a keyboard. Make sure focus is visible, buttons have clear names, images have meaningful alternatives where needed, and text is readable. Test the navigation and primary forms on a real small-screen device as well as a desktop browser. A responsive preview alone does not catch every problem.
Verify the live domain, security and recovery plan
Confirm the domain registration and DNS are managed by an authorized account, and check the expected hosting records before switching traffic. Test the preferred domain and its www version over HTTPS. Make sure certificates cover the required hostnames and no page loads insecure resources.
Take a restorable backup of the current site and database where applicable, record the existing DNS and deployment settings, and agree who can roll back a failed release. Keep credentials out of shared launch checklists. If you are replacing an existing website, preserve its working version until the new site has passed essential live checks.
Protect important pages and search visibility
Before launch, check page titles, descriptions, headings, canonical URLs, internal links and the XML sitemap. A private staging site should not be indexed, but the public site must not accidentally inherit a staging noindex rule. Check the live robots configuration after deployment.
If any URLs change, map old pages to the most relevant new destinations. Google's site migration guidance recommends permanent server-side redirects where possible and warns against redirecting unrelated pages to a single destination. Keep old URLs that still serve a purpose, and test each important redirect after the change.
For a completely new website without previous URLs, a redirect migration may not be necessary. Focus instead on making public pages accessible and submitting the correct sitemap to your verified search tools.
Test speed, tracking and privacy choices
Open your most important pages on a slower connection and check that images, fonts and interactive elements load without major disruption. Use PageSpeed Insights to identify performance concerns, but combine its recommendations with real device testing rather than chasing a score alone.
Confirm analytics records page views and meaningful events such as successful enquiries or purchases, where configured. Review consent requirements and make sure tracking behavior matches the site's privacy notice and applicable obligations. A tracking tag being installed is not the same as a conversion event being recorded correctly.
Run a simple launch-day sequence
- Freeze avoidable changes: confirm approved content, outstanding defects and launch contacts.
- Prepare recovery: verify backups, deployment access and rollback steps.
- Deploy carefully: update hosting or DNS settings only as required by the plan.
- Test the live domain: check HTTPS, key pages, redirects and mobile navigation.
- Complete a real journey: submit a form or complete a safe test checkout and verify its result.
- Confirm visibility: review indexing settings, analytics and monitoring alerts.
- Approve the announcement: promote the new website only after critical checks pass.
If a critical form, payment, security or access check fails, delay the announcement and fix the issue before inviting visitors.
What to monitor during the first week
Watch for failed enquiries, broken links, server errors and unexpected customer questions. Check that search tools can access important pages and that tracking records the intended actions. Review support messages for problems that automated tests missed. Keep a short issue log with an owner and resolution status.
A website launch checklist is most valuable when it becomes part of your handover process, not a one-time document. For help planning a build and its launch checks, explore DesDevSol's website development service.