Launching a website is a coordinated change, not simply a file upload. Pages, assets, forms, domain settings and receiving services all need to work together. A reviewable checklist helps the business and development team agree on what is ready and who owns the next step. Test real visitor journeys instead of relying only on a visual approval.
Read the content as a new visitor
Review main pages without assuming background knowledge. Confirm service details, contacts, prices and calls to action. Remove draft text, placeholders and unsupported claims. Check the context of examples and photographs. A visitor may arrive directly on a service page from search, so each important page should explain its purpose without relying on a previous visit to the homepage.
Test delivery, not just the submit button
Use approved test enquiries to confirm that the intended receiver accepts the message. Check required fields, invalid input, verification and failures. The thank-you page should follow a confirmed success. Identify who receives the request and how it is handled. A browser animation alone does not prove that the business received the customer’s details or that the receiving integration is configured correctly.
Review screens and images
Check representative pages at small and large widths. Test menus, long headings, tables and forms, including keyboard access and enlarged text. Verify that content images and backgrounds load from the deployed paths. Check responsive variants as well as originals. Cached styles may hide an incorrect reference until someone opens the page on another device, so inspect what the browser actually requests.
Protect familiar page addresses
Map changed URLs to relevant new destinations and verify their redirects. Do not send every retired page to the homepage. Review internal navigation and important external links. Check canonical URLs, sitemap entries and indexing instructions. Public information and utility pages such as confirmations have different purposes; their settings should reflect those differences without accidentally hiding the pages customers need.
Confirm control and recovery responsibilities
Record who manages the domain, hosting, administrator accounts and connected services. Agree on ordinary content updates and larger change requests. Define backup responsibilities and test how restoration works. A backup no one knows how to restore is an incomplete plan. Store access details privately rather than adding them to a public archive, and ensure the business can recover access when a team member changes.
Plan the days after launch
Nominate someone to review enquiries, errors and unexpected questions. Recheck the public site after deployment, even when staging tests passed. Keep an issue list with an owner and priority, separating defects from future ideas. A clear handover supports operation long after the launch announcement. Use early feedback to decide the next improvements while resolving any interruptions to essential visitor journeys promptly.
Your practical checklist
- Approved content and contacts
- Confirmed enquiry delivery
- Responsive layouts and correct assets
- Tested redirects and indexing settings
- Access, backups and post-launch ownership
