10 Must-Check Items Before Launching Your Business Website
Sources, AI assistance & corrections
A website launch needs evidence that customer journeys, permissions, and recovery work in production. This checklist helps teams record tested behavior and remaining checks.
Reviewed and updated: October 13, 2026.
1. Verify the production URL and HTTPS
Open production rather than staging. Check certificates, HTTP redirects, and one preferred www or non-www address. Test legacy redirects. A ZIP upload or local lint result alone does not prove deployment; inspect public URLs and behavior.
2. Test actual mobile interactions
Use real devices and browser responsive tools. Inspect menus, long headings, tables, buttons, forms, and horizontal overflow. Google retired its Mobile-Friendly Test in December 2023. Lighthouse and PageSpeed Insights help diagnose issues, but customer journeys still need device testing.
3. Exercise the primary customer journey
Define scenarios first: discover a service, submit an enquiry, receive confirmation, and follow its progress. Use clearly identified test data and authorized recipients. If email or WhatsApp delivery has not been checked at the recipient, record it as unverified. Test validation and error messages as well as buttons.
4. Check access and recovery
Ordinary accounts must not reach administration or other users' data. Grant permissions by role. Maintain recoverable backups and a named recovery owner. A backup file does not prove restoration; test recovery safely with approved data.
5. Verify metadata and crawlability
Check one main heading, title, description, canonical, and consistent language for each URL. Sitemaps should contain final destinations intended for indexing. Search Console URL Inspection can verify fetchability and indexing restrictions. Crawl requests do not guarantee inclusion.
6. Verify Analytics and performance
Confirm page_view reaches the intended Analytics property without duplicate collection. Do not place names, emails, or user messages in event parameters. Review images, scripts, and response times that affect the experience. Performance scores diagnose issues rather than promise rankings.
7. Record handover evidence
Document URLs, devices, accounts, test times, results, and outstanding problems. A booking journey such as TD Travelindo needs enquiries distinguished from confirmed orders. Role-based systems such as EPN ATRACK need appropriate test accounts. These examples illustrate different scenarios; this article does not claim every feature has been tested.
Sources and practical references
The cover is an illustration. Implementation advice is SWY editorial analysis; examples do not establish a client location or guarantee an outcome.
