Before releasing a website, check both what visitors can understand and what crawlers can access. A valid sitemap cannot repair unclear product copy, and a useful page cannot be indexed if an accidental noindex directive remains in place.

Check the pages that support a decision

Review the homepage, product pages, pricing, getting-started guidance and support information together. A visitor should understand who a product is for, what it does, what it requires, what the purchase includes and what happens after payment. Resolve contradictory delivery or compatibility claims before launch.

Remove unfinished placeholders from public pages and keep demonstration material clearly separated from real product claims. Do not invent testimonials or results to fill a design. Practical instructions and inspectable product information can be useful without those claims.

Verify titles, descriptions and canonical URLs

Give each important page a distinct, descriptive title and a concise summary of its actual content. Check the rendered HTML, including category and paginated views. Use a canonical URL on the production domain and keep internal links consistent with that URL. Test redirects from changed addresses.

Google describes how canonical signals work. They express a preference; they do not guarantee which URL will appear in results.

Check indexability and sitemap coverage

Public pages intended for search should return a successful response and should not accidentally carry noindex. Private orders, checkout, internal search and administrative pages should not appear in the public sitemap. Missing URLs should return an appropriate error status rather than a success page with no useful content.

Open the sitemap and test its entries. Include the canonical URLs you want discovered. Keep modification dates tied to real content changes. A submitted sitemap supports discovery, but submission does not guarantee indexing. Refer to Google's sitemap guidance for the supported format.

Follow a real visitor journey

Go from the homepage to a product, to its practical guide and to support or checkout. Test the same journey on a narrow screen. Read button labels, inspect keyboard focus and check that long headings and tables fit. Ensure useful articles have links from relevant pages instead of relying only on the sitemap.

Validate structured data against the page

Product prices, article titles, authors and breadcrumbs should match visible content. Do not add ratings or review counts without real evidence. Check JSON syntax locally, then use Google's testing tools on the deployed URL. Eligible markup does not guarantee a special search appearance.

After release, collect external evidence

Verify the production property in Search Console, submit the sitemap and inspect important URLs. Measure performance on the deployed site and monitor actual coverage and queries. Use a bounded technical preflight to reproduce individual findings. Indexing and ranking changes require observations after launch, not assumptions based on a local test.

Continue the SEO workflow

Choose a guide by task or review the on-page checklist before publishing your next change.