Wire Google's SHACL validation rules into the build once they are published

Said at Search Central Live: Google plans to publish downloadable SHACL rules on each structured data feature guide, to run inside a site's content generation so markup is checked before it is published. They will catch problems such as a missing required field but will not replace Search Console reports, and they were not yet available at the time of the event.

Plan a CI or CMS publishing step that runs a SHACL validator (for example pySHACL) against the generated JSON-LD, adopt the rules type by type as Google releases them, and keep the Rich Results Test and Search Console as the reference.

Regensbot guides you through your structured-data validation step, records your attestation and tracks when it expires. Attested is never shown as pass.

A weekly watch looks for Google's structured-data validation rules and turns this into a CI check once Google publishes them.

You verify the site by a DNS TXT record, a meta tag or a file. Regensbot then keeps a checklist item for this requirement, with a state, a guide, an evidence upload and reminders.

How verdicts workWhat you connect