Toolkit capability
Astro production checklist
Use a strict Astro production checklist covering builds, browsers, native Safari, staging, PageSpeed, deployment identity, and canonical verification.
Astro production checklist
A release process matters most when it stops an incomplete candidate. The Go for Launch checklist defines required evidence, promotion order, and explicit stop conditions.
What the process produces
06 concrete deliverablesCapability and requirements
Required inputs apply to this workflow. Conditional tools apply only when the project, platform, or chosen service needs them. A missing optional integration does not block unrelated Go for Launch checks.
Toolkit capability
Use a strict Astro production checklist covering builds, browsers, native Safari, staging, PageSpeed, deployment identity, and canonical verification.
Required for this workflow
Only when applicable
Generate the XML sitemap during every production build and compare it with the canonical URL of every indexable built page. A missing sitemap, missing route, duplicate URL, wrong host, or robots mismatch fails the build before staging.
Preserve the candidate identifier, source revision, test results, Simulator environment, PageSpeed scores, deployment ID, public-host checks, and remaining risks.
Block production on diagnostics, sitemap completeness, browser behavior, native Safari, route completeness, forms, overflow, staging identity, or any PageSpeed score below 100. Fix and retest rather than waiving the result.