Before launching an AI-built website, turn “it seems to work” into a small set of outcomes you can verify. The checks should reflect what customers and staff will actually depend on. A public information website needs a different review from an application handling private accounts, bookings or payments.
This checklist provides a starting point, not a certification. Use our prototype-to-professional-website guide to define the project's stage, then assign each launch check to someone with the knowledge to assess it. An unresolved critical journey should remain a visible launch decision.
Confirm the message and real content
Read every public page as a first-time customer. Can you understand who the service is for, what is offered and what to do next? Replace demonstration testimonials, placeholder contact details and images you do not have permission to use. Check the business name, service area and languages against the actual offer.
Ask someone unfamiliar with the project to locate a service and contact the business. Observe where they hesitate. This exercise can reveal gaps that a creator no longer notices after repeatedly viewing the same screens.
Complete the journeys and verify their results
Use the real domain or a representative prelaunch environment, with safe test data. For an enquiry, look for the record in the destination system. For a booking, confirm the agreed reservation state. Check confirmation emails where included and explain any delay to the visitor.
- Submit a valid enquiry and confirm it reaches the responsible team.
- Try missing and invalid inputs; look for clear, recoverable errors.
- Repeat a submission and check how duplicate requests are handled.
- Test the journey on a real phone and with a slower connection.
- Verify the fallback contact route when a connected service fails.
Record the expected outcome and the actual result. If an integration only works with its creator's account, establish how staff will operate it before launch.
Check data access separately from login
Where accounts exist, test with distinct users and roles. Confirm that each can access only the appropriate records and actions. Public pages should not expose credentials or private demonstration data. Decide who can administer the system and how access is removed when someone leaves.
Our security guide beyond login expands these checks. Security tools can help, but the business needs clear access rules and someone responsible for reviewing their implementation. Apply the depth of review to the sensitivity of the information involved.
Verify search discovery and usable navigation
Open each important service page directly, rather than only through the homepage. Check meaningful titles, a sensible heading structure, internal links and the intended indexing settings. Preserve necessary redirects when replacing an existing website.
Google's SEO starter guide explains discovery and useful content. Our technical SEO guide turns that subject into business decisions. A sitemap can support discovery; neither it nor your framework guarantees indexing or rankings.
Test access and performance in practical conditions
Navigate the menu and form using a keyboard. Check visible focus, readable text, labels and understandable errors. Zoom the page and verify that content remains usable. Test long translations and realistic images rather than approving only a short English demonstration.
W3C's accessibility introduction explains why access involves more than fitting a screen. Our accessibility guide provides further examples. These first checks do not replace a fuller evaluation where needed.
Review the time it takes to reach useful content on mobile. Repeat performance measurements in suitable conditions and investigate significant delays instead of relying on one high score.
Assign the responsibilities after publication
Confirm account ownership, recurring costs, editing instructions and the person who handles incidents. Establish how faults are detected and how a working version or data can be restored. Where relevant, practise recovery before customers depend on the system.
For a Next.js project, the Next.js website and its production checklist provide technical context. Our website design and development service connects those checks to your project's agreed scope.
Discuss your launch readiness and remaining questions with Webility.
