Fail incomplete builds
Generate the sitemap during every production build. Compare every indexable built page canonical with the XML, reject duplicates and wrong hosts, and fail when robots.txt does not advertise the exact canonical sitemap URL.
Astro sitemap and Google Search Console
Make sitemap completeness part of every Astro build.
A sitemap is not a best-effort SEO artifact. Go for Launch makes sitemap generation and route completeness part of the normal build, then verifies the public file and its Search Console submission state.
What the process produces
06 concrete deliverables- 01Build-blocking sitemap validation
- 02Indexable page and canonical comparison
- 03Conventional sitemap.xml entry point
- 04Exact robots.txt declaration
- 05Public staging and production checks
- 06Search Console verification and submission record
Verify the deployed discovery surface
Request sitemap.xml, every child sitemap, and robots.txt from staging and production. Confirm HTTP status, XML content, canonical origins, and intended page responses rather than trusting local output alone.
Keep ownership and submission distinct
When approved Google Search Console access exists, verify the property and permission first. Then inspect submitted sitemaps and submit the exact canonical URL when it is missing. A sitemap submission does not verify property ownership.
Current product references