Schema Inventory

Crawls your site and records the structured data on every page, then reports it as an inventory rather than a per-page verdict. Finds blocks that silently fail to parse, pages carrying nothing, and the types that stop partway through a template. Exports to Excel.

How to use it

  1. Enter your domain. It reads robots.txt and your sitemap, then fetches each page listed.
  2. Every page is parsed for JSON-LD, Microdata and RDFa. Nested entities count too: a WebPage whose publisher is an Organization declares both, and a counter that reads only the top level reports one type on a page carrying six.
  3. Results are rolled up two ways, by page and by type, because "what does this page declare" and "where does this type appear" are different questions and only the second finds a broken template.
  4. Start with anything that fails to parse. An invalid block is discarded whole and in silence, so a single trailing comma can remove every type on the page while the markup still looks right in the source.

What the numbers mean

Coverage
The share of scanned pages carrying a type. A site-wide type at 100% is a template doing its job. The same type at 94% is more interesting: it usually means one route was added later and never picked the pattern up, and that gap is invisible from any single page.
Nested entities
Structured data is a graph, not a list. Organization, Person and ImageObject usually appear as properties of something else rather than as blocks of their own. Counting only the outermost object undercounts almost every real page.
A parse error
Invalid JSON-LD is not partially read, it is ignored entirely. Nothing warns you, the page looks fine, and every type in that block simply stops existing as far as a search engine is concerned.

Questions

Is this a validator, or an inventory?

Both, but the inventory is the point. Google's Rich Results Test already validates one URL at a time and does it better. What it cannot tell you is that 3 of your 60 product pages lost their Product block, which is the thing that actually costs traffic and the thing nobody checks.

Does it check whether my schema is eligible for rich results?

No, and it deliberately does not pretend to. Eligibility depends on required properties per type and changes without notice. This tells you what exists and where, then you take the specific pages it flags to Google's own tester.

Does it see schema added by JavaScript?

No. It reads the HTML as served, which is what a crawler sees first. If your structured data is injected client-side it will not appear here, and that gap is itself the finding.

Where does the Excel file come from?

It is built in your browser and never uploaded. The site does not have a copy of your crawl, because it never had one: the pages are fetched, read and discarded.

Guides that use this tool

Other free tools