What the Rich Result Eligibility Checker does
This checker reads a page's JSON-LD and tests each item against the properties Google documents as required and recommended for its rich result features - product snippets, merchant listings, review snippets, articles, breadcrumbs, events, recipes, organisations, videos, job postings and local businesses. It also checks that key values in the markup, such as a product's name and price, actually appear in the visible page text.
The result is a statement about documentation, not a forecast. Meeting the requirements makes a page eligible to be considered; Google decides whether to show a rich result, and it has stopped showing some altogether - FAQ results since May 2026 and HowTo results before that - which the checker reports rather than scores.
How to use it
- Enter a public URL, or paste the page's HTML (or just the JSON-LD). A URL is fetched once through a2z.tools; pasted content is checked in your browser.
- Select Check structured data. Every typed JSON-LD node is found, including items inside @graph arrays and nested objects, and local @id references are followed.
- Read each feature's verdict. Fix anything listed as missing required first, then visible-content mismatches, then the recommended properties that apply to your content.
- Follow the Google doc link for each feature to read the full guidelines, and confirm with Google's own Rich Results Test and Search Console before relying on a change.
Reading the results
Meets documented requirements: every property Google marks as required for that feature is present with a non-empty value. It does not mean the values are correct, that the page follows the content guidelines, or that a rich result will appear.
Missing required data: at least one required property is absent, or a documented rule is broken - for example a merchant listing whose offer is an AggregateOffer or whose price is zero. Google will not use that item for the feature.
Visible-content mismatch: a marked-up value, such as a price of 89.99, could not be found in the page text. Google's guidelines require structured data to describe what users see; a price that differs from the page is a common reason for merchant listing problems.
Google no longer shows this: the markup is valid schema.org, but Google has retired the rich result. It does no harm, and it may still help other consumers of structured data.
Worked example: the product page example
The example page marks up Trail Runner 2 running shoes with name, image, brand, SKU, GTIN, an aggregate rating of 4.6 from 212 reviews, and an Offer at 89.99 USD in stock. Every required property is present for both product snippets (name plus one of review, aggregateRating or offers) and merchant listings (name, image, an Offer with a price above zero and a currency).
But the visible page says Now $79.99, with $99.99 struck through. 89.99 appears nowhere in the text, so both product features are flagged with a visible-content mismatch on offers.price. The fix is to update the markup to 79.99 - and to describe the struck-through price with a priceSpecification if it matters.
Merchant listing also lists recommended properties that are absent, such as hasMerchantReturnPolicy and shippingDetails. They are not required, but they are how return and delivery details reach Google.
Which parts are documented and which are this tool's
The required and recommended property lists, the Offer versus AggregateOffer rule, the price above zero for merchant listings, the breadcrumb rule that only the last item may omit its URL, and the FAQ and HowTo status all come from Google Search Central's feature pages and changelog, stored in a dated catalogue with a link per feature.
The visible-content comparison is an A2Z heuristic. Google requires markup to match visible content but does not publish a test for it; this tool looks for the marked-up name, headline or price in the page text, allowing common price formats such as 1,299.00 and 12,50. A miss can be a real mismatch or text that is rendered by JavaScript, split across elements or formatted unusually.
Limitations: what the result does not prove
- Only JSON-LD is read. Microdata and RDFa are counted and mentioned but not checked.
- A URL is read as served, without running JavaScript. Structured data or prices injected by scripts are not seen; paste the rendered HTML from your browser's developer tools instead.
- Values are checked for presence, not correctness: a wrong GTIN, a stale rating or an invalid date format can still pass. Use Google's Rich Results Test for its own validation.
- No tool can say a page will get a rich result. Google applies quality and policy checks and chooses per query.
Privacy: where your data goes
The analysis runs in your browser. If you choose to load a public URL instead of pasting, a2z.tools fetches that address read-only and returns the text to your tab; private and internal addresses are refused and nothing is stored. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- Google Search Gallery - supported structured data - checked 19 Sep 2026
- schema.org vocabulary - checked 19 Sep 2026
- Google Search Central - General structured data guidelines
- Google Search Central - Merchant listing structured data
- Google Search Central - Documentation updates
Frequently asked questions
What does it mean if my page meets the requirements but shows no rich result?
Only that nothing required is missing. Google decides per query whether to show a rich result and also applies quality and spam policies, site reputation and content guidelines. Check Search Console's enhancement reports to see whether Google has recognised the items.
Does FAQ markup still produce rich results?
No. Google restricted FAQ rich results to authoritative government and health sites in 2023, announced that the feature would stop appearing from 7 May 2026, and has since removed its documentation. The checker reports FAQPage items as no longer shown rather than as errors.
What is the difference between a product snippet and a merchant listing?
A product snippet can appear for any page about a product, including reviews, and needs a name plus a review, rating or offer. A merchant listing is for pages where you sell the product: it needs an image and an Offer with a price above zero and a currency, and AggregateOffer is not accepted.
Why does the checker say my price is not visible?
The price in your JSON-LD could not be found in the page text. Either the markup is out of date, the price shown is a sale or member price, or the price is drawn by JavaScript or split across elements. Compare them by hand; the markup must match what a shopper sees.
Can it check microdata?
No, only JSON-LD, which is the format Google recommends. If the page uses microdata or RDFa, the checker says how many such elements it found; use Google's Rich Results Test to validate those.
Are recommended properties worth adding?
When they describe real information on the page, yes: they give Google more to show, such as ratings, availability or return policies. Do not add recommended properties with invented or hidden values; that breaks the guidelines.
Last reviewed by the A2Z.Tools team against the sources listed above.
