Does every built page honor the indexability contract?
We run the production source as the fixture, generate the static output, then compare canonical HTML, robots directives, sitemap membership, redirects, and the custom 404.
Astro generated the expected canonical HTML, kept the custom 404 out of search, and exposed the registry-backed search-eligible routes in the sitemap. This is a repository-specific publishing result, not a general Astro performance score.
Build first. Inspect the output, not the promise.
The runner executes the pinned Astro build in this repository. It walks every generated canonical HTML file, checks the index directive, compares the sitemap with the route registry, and verifies the custom noindex 404.
corepack pnpm exec astro build- All registry routes builtPASS
- Custom 404 existsPASS
- All canonical HTML is indexablePASS
- Custom 404 is noindexPASS
- Redirect alias not discoverablePASS
- Sitemap matches eligible routesPASS
- Error route not discoverablePASS
Useful for this release, not a universal benchmark.
- One warm local run on a Windows x64 workstation; no cross-platform comparison was made.
- This verifies generated artifacts and indexing controls, not Vercel edge behavior or search-engine processing.
- The result applies to the captured repository revision and becomes stale when routes or publishing controls change.
Clone the public repository, install the pinned dependencies, and run the capture command. The runner and saved JSON are versioned beside the site.
corepack pnpm install --frozen-lockfile
corepack pnpm field-test:astro:capture