- Where do the required fields come from?
- From Google's own structured data documentation for each type, transcribed rather than guessed. Where Google says a type has no required properties, as it does for Article and Organization, this tool says so instead of inventing a rule.
- Which types does it check?
- FAQPage, Article and its subtypes BlogPosting and NewsArticle, BreadcrumbList, HowTo, Product, Offer, AggregateOffer, AggregateRating, Review, Recipe, Event, VideoObject and Organization. Any other type is reported as present and untracked, which means we have nothing to say about it, not that it is wrong.
- Why does it only read JSON-LD?
- Because JSON-LD is what Google recommends and what almost everything emits now. Microdata and RDFa are separate syntaxes with their own parsing rules; if a page uses them, this tool counts the elements and says so rather than pretending the page has no structured data.
- The URL check found nothing, but I can see my markup.
- Most likely the markup is injected by JavaScript, usually a tag manager, after the page loads. This tool reads the HTML the server sends, which is also what many crawlers see first. If your structured data only exists after a script runs, that is worth knowing on its own.
- Is this the same as Google's Rich Results Test?
- No, and it is not trying to be. Google's test is the authority on eligibility and you should finish there. This is the fast loop before it: paste a draft, see the missing fields, fix them, repeat, without a round trip per attempt.
- How many URL checks can I run?
- Ten an hour per address, which is enough for real work and low enough that our fetch bill stays a rounding error. Pasting JSON-LD has no limit at all, because it never leaves your browser.