A launch checklist is most useful when it follows the path a visitor and a crawler will take: reach the site, understand the page, complete a task, and recover if something goes wrong.
Check public access first
A successful local build proves the code compiles, but it does not prove the public domain is reachable. Test from a browser outside the deployment environment. Check that redirects end at one preferred hostname, especially if both www and non-www resolve.
Open the production domain over HTTPS and check the home page, a guide, and each tool.
Test a missing URL and confirm it returns a helpful 404 page.
Check robots.txt and sitemap.xml on the production domain.
Confirm the sitemap lists only pages that are actually published.
Review each important page
Read the title and description as they appear in the page source.
Check that the H1 describes the page and that links use meaningful labels.
Use every control with a keyboard and on a narrow phone screen.
Submit invalid and empty tool inputs and verify the feedback is understandable.
Check contact information and policy pages against the services actually in use.
After launch
Add the site to Search Console, submit the sitemap, and inspect representative URLs. Watch for broken links, mobile layout problems, and confusing tool output. Fix errors before expanding the content library. Search Console submission is a discovery step, not a promise of ranking or indexing.
Sources and further reading
Primary documentation and references used to support this guide.