Use the Google Rich Results Test API to submit a URL or HTML snippet; send a POST or GET request to the Rich Results Test endpoint with the URL or code parameter
Alternatively, use the Schema.org validator at validator.schema.org by sending a POST request with the HTML body or structured data JSON-LD to validate against the Schema.org vocabulary
Parse the response for detectedItems, which lists found structured data types, and richResultsItems, which lists items eligible for rich results along with any associated errors or warnings
Automate validation in CI by extracting JSON-LD from rendered HTML using a DOM parser, then submitting each block to the validator endpoint and asserting zero errors
Cross-reference required and recommended properties for the target schema type (Product requires name and offers; Article requires headline, author, datePublished) against the detected properties in the response
Known gotchas
The Rich Results Test evaluates eligibility for Google's specific rich result features, which is stricter than Schema.org validity; a schema can be valid per Schema.org but still not qualify for rich results due to missing recommended properties
Testing a URL with the Rich Results Test API fetches and renders the page as Googlebot would; pages behind authentication or with bot-blocking measures will not return accurate results
JSON-LD is strongly preferred by Google over Microdata or RDFa; mixing formats on the same page does not cause errors but can lead to unpredictable parser behavior
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp