What does this data show?
It shows how many different domains use a Schema.org type or property, grouped by bucket.
I turn Schema.org usage data into a readable, comparable and decision-support radar.
Schema Radar makes the official Schema.org usage dataset more usable. You can filter terms, see the freshest data, read period-over-period comparison and quickly interpret your own schema list.
TechnicalContentMeasurement
Consultant note
For me, schema usage data is not about asking 'which code should we add?' but 'which markup actually makes sense for this page type?'
That is why I do not read these buckets as a standalone priority list. First comes page intent, then visible content, then Google support, then implementation effort. The tool exists to move the discussion from checklist thinking to better questions.
What does it not show?
It does not predict ranking impact, rich result eligibility or traffic potential on its own.
How should it be used?
Read it with page intent, visible content, Google support and technical correctness.
Live data
The latest monthly file is fetched from the official GitHub folder and the data period is shown clearly.
Filter-aware
Search, class and bucket filters update the table, summary cards and chart reading together.
Mini analysis
Paste your own schema list for a quick first reading. It is a lightweight pre-audit, not a full audit.
Schema Radar
Filter, compare and interpret.
Date, source, comparison and interpretation areas are intentionally transparent. The goal is to make it obvious what the user is looking at.
Waiting for data.
Data period
—
Last check
—
Source status
—
Free mini analysis
Get a quick first reading for your own schema list.
Add types and properties line by line. The system first applies rules; if a Gemini key is connected, it also adds a short AI note.
URL mini preview
This is a quick demo check. Enter a URL and it extracts JSON-LD, Microdata and RDFa traces from the server-returned HTML. JavaScript-rendered schema belongs to a full crawl/render audit.
Term table
First 50 results
This shows Schema.org types and properties matching the selected filters with concise reading notes, not as a raw data dump. The first 50 rows are shown by default; you can load more when needed.
| Term | Class | Bucket | Previous status | Reading note |
|---|---|---|---|---|
| Loading data. If the table does not populate in a few seconds, use Refresh data. | ||||
Monthly comparison
When a new period arrives, the change needs to be interpreted, not just listed.
Here you get a compact view of new, rising and falling terms. Use it together with the table for deeper reading.
Next step
This page is the reading layer; the real value starts with site-specific interpretation, prioritization and implementation planning.
You can use Schema Radar for free. The next layer reviews page types, rich result eligibility, GSC enhancement reports and information architecture together.
Source
This page is based on the public usage dataset published by Schema.org in collaboration with Google. The tool reads adoption buckets; it does not predict rankings or traffic.
FAQ
Frequently asked questions
What does Schema Radar do?
It filters and interprets Schema.org type and property adoption buckets from the public usage dataset.
Does it predict rankings?
No. Adoption is not a ranking effect or rich result guarantee.
Is a low bucket bad?
No. A low bucket can represent a new, niche or industry-specific term.
Which websites are a better fit for SEO consulting?
Websites with technical, content and reporting needs with engineering support, many URLs and a need for structured organic visibility tracking are a better fit.
Which data is needed before starting?
Google Search Console, GA4, crawl data, key page types, technical workflow context and current goals are usually needed.
Is AI Search readiness separate from classic SEO?
No. Crawlability, content quality, entity clarity and trust signals still form the foundation.
Related pages