Render every template in a headless browser before release and check it in URL Inspection right after

The rendered HTML in Google's testing tools shows what Google can index, and the live test also shows page resources, JavaScript console messages and a screenshot. A valid live test only confirms that Google can access the page; indexing still depends on other conditions, and the live result can differ from the indexed version. URL Inspection tests only public URLs of a verified property, so it cannot test a staging host that answers 401 or 403 (DEV-CAN-07).

Keep a list of one representative URL per template (home, category, product, article, landing pages, each language version). Before release, render each template on staging with headless Chrome (Puppeteer or Playwright): compare the raw and rendered DOM, find the main content, prices and internal links, collect console errors, and run the structured data through the Rich Results Test's code input. Right after release, run the URL Inspection live test on one production URL per template and check the rendered HTML, resources and console messages. Request indexing for key URLs after fixing signals calculated at indexing time, such as language or robots rules.

Regensbot proposes a verdict with the evidence; a person on your team confirms it.

The evidence comes from the GitHub Action on each release.

On every release the GitHub Action renders your staging templates, runs the checks and fails the build on hard errors. Each release record schedules a re-check.

How verdicts workWhat you connect