Validate markup in the Rich Results Test before it reaches templates, and monitor it after release

Google recommends testing and previewing structured data in the Rich Results Test and testing manually before putting markup into templates. AI-generated markup can contain hallucinations, such as invented properties or broken nesting, and should be fact-checked and validated before publishing.

Prototype each type on one page, validate it, then put it in the template. The Rich Results Test takes a public URL, which Google fetches itself, or pasted code: for staging and other private pages paste the rendered HTML, as a community demo's script did at the event, and keep the resources it loads reachable anonymously, because the test cannot load resources behind a firewall or a password. Fix every error (a critical issue makes the item invalid and stops the rich result); warnings are non-critical and only limit how the item can appear. Add a CI step that extracts JSON-LD from rendered templates and checks syntax and required properties, and review the Search Console enhancement reports after each release.

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