Rich-result eligibility

What this tool checks

A rich results test checks whether your JSON-LD structured data meets Google's per-type requirements — the required and recommended properties a type like FAQPage, Product, Article, or Recipe must carry to be eligible for a rich result. When fields are missing or malformed, Google shows a plain blue link instead of stars, prices, FAQs, or images, and AI engines that parse the same markup lose the explicit facts they would cite. Validating before you publish turns a silent eligibility failure into a fixable checklist.

What it looks at

Required properties per type

Each schema type has a fixed set of must-have fields (for example, Product needs name plus offers, review, or aggregateRating); missing one makes the whole item ineligible for its rich result.

Recommended properties

Fields Google does not require but rewards — like Product image, brand, and priceValidUntil — that widen the rich-result surface and clear 'partial' or incomplete warnings.

Correct @type value

The type string must be a real, currently-supported schema.org type that Google renders (Product, Recipe, Review); a typo or retired type silently disqualifies the block.

Valid value format

Values must match the expected shape — ISO 8601 dates, absolute URLs, a numeric price, an enum like InStock — because a malformed value fails validation even when the field is present.

Nested-object completeness

Sub-objects such as offers, author, or aggregateRating carry their own required fields; an offers block without price and priceCurrency breaks Product eligibility.

Type-to-rich-result match

Not every schema type earns a Google rich result; the check confirms your markup targets a type Google actually renders, so effort is not spent on non-eligible types.

How to use it

1. Paste your JSON-LD code or the page URL into the tool and run the check.
2. Review the flagged errors and warnings grouped by type — required-field errors block eligibility, recommended-field warnings only limit it.
3. Fix the missing or malformed fields in your markup and re-test until the type reports zero errors, then publish.

Frequently asked questions