What moved between datasets

A deployment band is a slow-moving thing. When a term crosses one, something real changed in how the web ships structured data. This is the monitoring surface for exactly that.

Armed, awaiting next dataset

The archive holds one month (May 2026). Movement needs two, and inventing it would be the opposite of the point. The moment Schema.org publishes the next file, a scheduled job commits it, the commit triggers a rebuild, and this view computes the first diff on its own, no dashboard to refresh.

The board we're watching

The notable terms and where they sit today. When the next dataset lands, the bars that move are the story.

  1. BreadcrumbList 10M+ Core
  2. ImageObject 10M+ Core
  3. ListItem 10M+ Core
  4. Organization 10M+ Core
  5. Person 10M+ Core
  6. SearchAction 10M+ Retired plumbing
  7. WebPage 10M+ Core
  8. WebSite 10M+ Core
  9. FAQPage 1M - 10M Migrated, not dead
  10. WPHeader 1M - 10M Legacy noise
  11. HowTo 100K - 1M Zombie

Where they sit

Deployment on one axis, usefulness on the other. The danger zone is the bottom-right: markup the whole web ships for a feature that no longer exists.

The gap: deployment × usefulness still does a job dead / retired
< 1Knegligible
1K - 10Krare
10K - 100Koccasional
100K - 1Mcommon
1M - 10Mwidely deployed
10M+ubiquitous
Live rich result still drives a Google feature
Comprehension / GEO parsed for meaning, no SERP feature
Dead feature the feature it fed is gone
Tap a term to read its verdict. The danger zone is bottom-right: high deployment, dead feature.