A successful deployment is one part of launch. Use this checklist to establish that visitors can read the website, complete its main task, and get useful answers.
Confirm the intended release#
Ask your agent to inspect the deployment's final status, warnings, environment, and returned public URLs. Confirm that the content is live at the destination you intended. A staging URL showing a change does not prove that production has been updated.
Record the site slug and deployment sequence so you can identify this release later. For an established site, keep a known good deployment available for rollback.
Read and use the website#
- Open the homepage and every important landing page at the actual public address.
- Check business facts, product descriptions, contact details, and any prices or claims against approved information.
- Follow navigation, calls to action, downloads, and internal links. Verify that removed pages do not unexpectedly return unrelated content.
- Submit a non-sensitive test through important forms and confirm the expected result.
- Check images and the site's social preview image; a successful HTML response does not establish that image URLs work.
Inspect raw page content as well as the interactive view. Essential information should be present in HTML rather than appear only after client-side JavaScript runs.
Check mobile and accessibility#
Use a narrow mobile viewport and a desktop viewport. Confirm readable headings, natural line wrapping, usable menus, visible buttons, and no horizontal page overflow. Navigate important controls with the keyboard. Check visible focus and reduced-motion behavior if the site includes animation.
For chat, open and close the panel, send a message, scroll a longer answer, and confirm the composer remains usable on a phone.
Verify the answer-engine layer#
Inspect generated /llms.txt, the sitemap, and relevant Markdown page mirrors on the correct host. Check that links use the current public origin and that a known page can be retrieved.
Ask chat a question that is directly answered by the site, such as what service the organization provides or how to contact it. Compare the response with the published facts and follow any cited links. An iframe loading or a generic greeting is insufficient evidence.
If a search helper returns no results immediately after publication, investigate indexing and test the public content directly before concluding that the deployment failed.
Finish the handoff#
Keep editable source and build instructions, complete account setup, and confirm your agent can access the same site. Report any unresolved check plainly before sharing the site widely. Use maintenance to keep these checks current after launch.