A website is ready to launch when its main tasks work for a real visitor and you can maintain it afterwards. Start with the activity you want people to complete: read a guide, use a calculator or contact your business. Test that activity on a small screen as well as a desktop.
Content and usability
Check every navigation link and button. Read headings and introductions aloud: they should tell visitors what the page does without inflated promises. Label examples as examples, link factual claims to sources and remove draft placeholders. A calculator should explain its inputs, assumptions and limits, and return a useful result for zero and unusual values.
Trust and contact
Publish accurate information about who operates the site and how to reach them. Explain relevant data collection and commercial relationships. Do not invent testimonials, professional credentials, customer numbers or product-testing results. A contact form should show success only after the message has actually been accepted.
Technical checks
- Valid HTTPS and one preferred domain address.
- No private configuration or backup files exposed.
- Working page titles, descriptions and canonical URLs.
- A helpful 404 page for missing content.
- A sitemap containing public pages only.
- Protected admin routes and tested sign-out.
- A recent backup with a successful restore test.
Search is a process after launch
A sitemap helps describe your public URLs but does not guarantee crawling, indexing or rankings. Connect a verified Search Console property when the owner account is available. Review actual search performance and correct technical issues before producing large amounts of additional content.
Work through a real enquiry test
For a service website, start signed out on a phone. Find the service area, complete the enquiry form using a clearly labelled test message, and confirm the message reaches the actual destination. Next submit an incomplete form and check that the error identifies what needs correcting. The test passes only when the operator can retrieve the accepted message; a success banner alone is not enough. Record the date and remove test data when it is no longer needed.
Use our interactive launch checklist to record the checks on your device, then export the result for your project notes. It records your review rather than automatically certifying the site. For a failed check, write who will fix it and when it will be retested.
Establish a small maintenance routine
Check important forms and calculators after changes. Review dated prices before recommendations become stale. Read incoming questions to identify missing explanations. Your first release does not need every possible feature; it needs to be accurate, usable and recoverable, with a clear plan for the next improvement.