Rich Result Monitor
Monitor rich-result eligibility and impressions over time.
Source
Fetch a page; we identify which rich-result types it's eligible for.
Start here · What does rich result monitoring mean here?
Rich results are enhanced search features driven by structured data. Google’s eligibility rules expect certain properties for each schema type.
This tool fetches HTML, finds application/ld+json blocks, and matches supported @type values against a built-in checklist of required properties.
Eligibility in the UI means required fields are present on the parsed object. Google still validates in production, so treat this as a fast preflight, not a guarantee.
When to use this tool
- Before you request a recrawl
Catch missing
image,author, ordatePublishedon Article markup before you rely on a snippet change. - FAQ or HowTo launches
Confirm
mainEntityexists for FAQPage andstepexists for HowTo before publishing help content. - Product detail QA
Verify Product blocks at least carry
nameandimageso you know the JSON-LD layer is not empty. - Template comparisons
Fetch two templates—old theme versus new—and compare which types flip from partial to eligible.
Examples
Walk through these with the form above — they are practice scenarios, not live data.
Blog article URL
Try this
Fetch an article that uses BlogPosting or Article JSON-LD in the head or body.
What to look for
Expand the card to see missing headline, publisher, or image fields called out in red badges.
Paste HTML instead
Try this
Copy view-source HTML into the textarea if you cannot fetch from staging.
What to look for
The parser runs the same way. Use this for password-protected environments.
Short tutorial
Follow in order the first time you use the tool; later you can skip to the step you need.
- Step 1 — Fetch or paste HTML
Use Fetch a page for public URLs or paste raw HTML when access is restricted.
- Step 2 — Read the summary counts
Eligible means zero missing required fields. Partial means at least one required property failed.
- Step 3 — Open each type card
Required properties list with check or X icons shows exactly what to fix in the JSON-LD.
- Step 4 — Fix in your CMS or tag manager
Update the template, deploy, and rerun the same URL until the type shows eligible.
- Step 5 — Validate in Google’s tools
Use Rich Results Test or URL Inspection after major changes. This page does not call Google APIs.
More detail
New here? Skim Start here first, then run one Examples scenario in the form above.
Rich Result Monitor does one job: monitor rich-result eligibility and impressions over time. It lives under SERP & Rankings on SEOToolkits, where the beginner idea is simple: SERP SEO studies the search results page itself: rankings, snippets, features, and what Google is rewarding.
FAQ
- Why is my type missing entirely?
- Only
@typevalues in this tool’s map are evaluated. Other types are ignored until support expands. - Does eligible mean I will get a rich snippet?
- No. Search engines decide presentation. Eligible only means required fields exist in the parsed block.
- What about microdata or RDFa?
- This parser looks at JSON-LD script tags only. Convert or duplicate critical markup into JSON-LD if needed.
- Can nested objects satisfy required fields?
- The check tests top-level keys on each item after
JSON.parse. Very deep graphs may need manual review.
Related tools
Same workflow cluster on SEOToolkits — open another module without leaving context.
Structured Data Validator
Validate JSON-LD against schema.org and Google rich-result rules.
FAQ Schema Generator
Generate FAQPage JSON-LD from question/answer pairs.
Product Schema Generator
Generate Product/Offer JSON-LD with reviews and pricing.
Schema Extractor
Pull all JSON-LD/Microdata/RDFa blocks from any URL.