Schema Validator
Extract the JSON-LD, microdata and RDFa of a page or snippet, check it against the schema.org vocabulary, and see whether it meets the requirements of the rich results Google still shows. How it Works
Every Format
JSON-LD, microdata and RDFa, from a URL (raw or rendered), many URLs, or pasted code.
schema.org
Types and properties checked against the schema.org vocabulary.
Rich Results
Google's required and recommended properties for each rich result type.
A Real Example
Checked 17 November 2026https://yoast.com/product/yoast-seo-premium-wordpress/
- What the tool found
- 13 JSON-LD items, no schema.org errors and 7 eligible rich results, but FAQ (the WebPage is also typed FAQPage) and Sitelinks search box (a SearchAction on the WebSite) are listed as Retired. Software apps is not eligible: offers.price is missing, because a second block for the same #product gives its Offer's price only inside priceSpecification.
- What to do
- Put price and priceCurrency directly on every Offer, or merge the two product blocks into one. The FAQ and search box markup can stay, but they no longer earn a rich result.
Reading the Result
Errors
The markup can't be read, or breaks the schema.org vocabulary. Fix these first: nothing else counts until the item parses.
Eligible
The item has every property Google requires for that rich result. Eligible isn't a promise: Google decides per search whether to show it.
Missing Recommended
Optional properties that can make the result richer. Add the ones that are true of the page.
Retired
Valid schema.org that Google no longer shows as a rich result, such as FAQ (since May 2026) and How-to (since 2023). Harmless to keep.
What it Can't Tell You
- It checks markup against Google's documented requirements, not against the page: markup that describes things visitors can't see breaks Google's guidelines even when it validates.
- Manual actions and site-wide quality signals that suppress rich results aren't visible from outside.