A business website is ready to launch when its important journeys work and the responsible people know how to operate it. A design approval is useful, but it does not verify enquiry delivery, redirects, access ownership or recovery.
Use this QA checklist as a structured sign-off for your own project. Add tests for specialist features and document any accepted limitation instead of assuming a generic checklist covers every system.
1. Agree the launch scope and owners
List the pages, templates and features included in the release. Identify who approves content, tests technical work and makes the final launch decision. Keep a clear route for reporting a blocking issue.
Separate genuine blockers from improvements that can follow later. A broken enquiry route should not be treated like an optional visual refinement. Record remaining tasks with an owner and an agreed priority.
2. Review content and brand accuracy
- Correct business name, contact details and service coverage.
- Approved headings, descriptions and calls to action.
- Licensed media with useful alternative text.
- Accurate project examples and attributed reviews.
- Current policies and no placeholder content.
- Checked translations where applicable.
Review the live-style page rather than only a text document. Long names, real photographs and translated headings can reveal layout issues hidden by placeholders.
3. Follow the main customer journeys
Arrive on a landing page, navigate to the relevant information and complete the intended action. Check menus, search, internal links, downloads and external destinations. Test any mobile drawer, accordion or gallery used in that journey.
For a store, include product selection, cart changes and supported test-payment outcomes. For a service business, include enquiry delivery, booking links and the staff handover. Test the route a customer will actually use rather than only the homepage.

4. Test forms and backend delivery
Try missing required fields, invalid entries and successful correction. Check telephone formats and the mobile keyboard layout. Verify that a valid submission reaches the correct inbox, CRM or other destination with useful context.
A success message alone is not delivery evidence. Confirm the receiving record and notification. Avoid sending real personal or sensitive information in test submissions; use an approved test process.
5. Review mobile use and accessibility basics
Check representative phone and tablet widths for readable text, usable controls and horizontal overflow. Test keyboard access, visible focus, form labels and error feedback. Ensure sticky elements do not cover important information.
The W3C accessibility Easy Checks provide a useful starting review, while a complete assessment may require further expertise. Do not present a quick visual check as accessibility certification.
6. Verify SEO and launch configuration
Review descriptive page titles, useful headings, internal links and intended public URLs. Check canonical destinations and any temporary staging restrictions before launch. Confirm important pages and resources can be accessed as intended.
For an existing site, test the URL mapping and redirects. Use our redesign launch guide for that workflow. Do not remove useful content or change addresses without checking their purpose.
7. Check performance, accounts and recovery
Review key pages for excessive media, unstable layouts and unresponsive interactions. Verify HTTPS, account ownership and appropriate staff permissions. Record who manages updates and renewal dates.
Take an appropriate backup and confirm the recovery process. For transactional sites, plan how new orders or enquiries during a rollback would be reconciled. A recovery plan should protect business records as well as the visual website.
8. Prepare the launch and handover note
- Record the approved release and launch window.
- Complete final content and operational checks.
- Apply the agreed deployment process.
- Repeat essential tests on the actual public domain.
- Confirm monitoring and staff access.
- Assign the first post-launch review.
Store useful documentation where the business can retrieve it. Include editing guidance, support boundaries and ownership details without placing passwords in a broadly shared handover document.
A final release checklist with evidence
Mark each item pass, fail or not applicable; attach the tested URL, device, expected result, evidence and owner. Resolve blocking failures before sign-off.
- Responsive layout: phone, tablet and desktop; long headings, galleries, menus and no sideways page overflow.
- Contacts: form validation, accepted test submission, backend receipt, WhatsApp, telephone and booking destinations.
- Navigation: live internal links, working downloads and relevant redirects where URLs changed.
- SEO: descriptive metadata, clear headings, approved canonical URLs and accurate structured data.
- Indexing: intended robots rules and public sitemap; no accidental staging-domain links or indexing blocks.
- Analytics: intended property, consent behaviour, successful-enquiry signal and duplicate-event checks.
- Performance: appropriately sized media and representative tests of LCP, INP and CLS; distinguish field data from one laboratory run.
- Accessibility: keyboard access, focus, labels, errors, contrast and zoom; basic checks do not certify full conformance.
- Recovery: HTTPS, account ownership, supported updates, tested backup and a transaction-aware rollback plan.
- Public validation: repeat critical journeys on the production domain and assign a post-launch review owner.
Use a recorded sign-off rather than assuming a visual approval proves launch readiness. For ongoing ownership, scope website maintenance alongside the release.
Download the business website launch QA checklist (TXT). Save a copy, add your project details and record the result and owner for each item.
Frequently asked questions
Can I launch with a few unfinished tasks?
It depends on their impact. Document accepted non-critical items, but resolve failures that prevent customers or staff completing essential tasks.
Should testing stop after launch?
No. Recheck the public environment and monitor real issues, especially after changes to forms, payments or integrations.
Does passing this checklist guarantee rankings?
No. It helps verify readiness and reduce avoidable problems; search visibility depends on more than launch QA.
Read website accessibility basics and planning a clear website brief. Explore website maintenance or request a scoped launch review.