Use the Schema Markup Validator at validator.schema.org to check all schema.org types for spec conformance — it validates against the schema.org vocabulary without Google-specific eligibility rules
Use the Rich Results Test (search.google.com/test/rich-results) to check Google-specific eligibility for rich result features like product snippets, review stars, and event markup
Run the Schema Markup Validator in CI by POSTing raw HTML to its API or by using the 'structured-data-testing-tool' npm package as a proxy
Treat Schema Markup Validator errors as structural bugs; treat Rich Results Test warnings as Google eligibility gaps that may suppress rich results
For non-Google engines (Bing, Yandex), the Schema Markup Validator is the authoritative reference since Rich Results Test only covers Google's interpretation
Document which schema types on your site are expected to generate rich results and create a test matrix linking URL templates to expected validator outcomes
Known gotchas
Schema Markup Validator passing does not guarantee Rich Results eligibility — Google applies additional policy rules (e.g., review content must be genuine, prices must be accurate) that no automated validator can check
The two tools can give conflicting guidance: Schema Markup Validator may accept a property that Rich Results Test rejects because Google uses a stricter subset of the schema.org spec
Neither tool evaluates structured data injected by client-side JavaScript unless the page is rendered; test with server-rendered HTML or use a headless browser to capture the full DOM
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