A launch-day SEO check is a check that the right pages can be found and understood. It is not a promise of a position in search results.
A small business site can start with a short, repeatable review. Do it on the published domain after deployment, because a working preview does not prove that the public site has the same content or settings.
Check the page the customer will see
Open the homepage, the important service pages and the contact page. Confirm that each loads correctly and describes the actual business. Look for draft copy, missing images and links that still point to a preview address.
Each page should have a clear purpose. A visitor looking for a specific service needs to know what it includes, where it is available when location matters, and how to take the next step. Repeating a broad company slogan across every page makes that harder.
Check search-facing details
Review the title and description for each important URL. They should describe the page honestly and help a person distinguish it from the other results they might see.
Check the canonical URL, the preferred version of a page when several addresses can return similar content. A production page should not name a localhost or staging address as its canonical. If an old address has moved, follow its redirect and confirm that the destination makes sense.
Google's SEO Starter Guide explains discovery, page organization and useful content. Those are foundations; a completed checklist does not guarantee indexing or rankings.
Separate crawl access from indexing choices
A crawler has to retrieve a page to read a page-level noindex directive. Blocking that URL in robots.txt can prevent it from seeing the instruction. Google's documentation on noindex explains this distinction.
Review public pages, private application areas and preview routes separately. Authentication protects private content. Search directives manage search behavior; they are not a substitute for access control.
Check the sitemap as well. It should list the public pages you intend to expose, with working addresses. Then inspect a few entries instead of treating a valid XML file as proof that every destination is correct.
Give images a job
Use images that support the nearby content. An actual product image, a permission-cleared project photograph or an explanatory diagram can help a visitor understand something a paragraph alone cannot show.
Provide descriptive alternative text when the image adds meaning. Decorative images can have empty alternative text so assistive technology does not announce unnecessary detail. Google's image guidance covers image context, discoverability and useful text alternatives.
Check image weight and layout on a phone. A large file should earn its place, and the page should reserve space for it so the text does not jump as it loads.
Keep a record after launch
Record the deployed version, the URLs checked, the problems found and the fixes made. Use Search Console to inspect indexing information where account access is available, and distinguish that evidence from a local code review.
Search behavior changes over time. New pages, changed services and retired offers can make a previously accurate site stale. A useful follow-up review checks the content and the customer journey along with technical settings.
If you are preparing a launch, combine this checklist with the website readiness guide and the ownership handoff checklist. They cover different parts of the same job: publish something clear, make it reachable, and keep control of it afterward.