Schema.org's vocabulary hit 823 types with version 30.0 in 2026

Schema.org’s vocabulary is not a fixed list. It is versioned software with its own release notes, and as of version 30.0, released 19 March 2026, schema.org’s own count page puts it at 823 Types, 1,529 Properties, 19 Datatypes, 96 Enumerations and 535 Enumeration members. Three months later, Google and the Schema.org community published a second, separate dataset: real usage statistics for those terms across the live web, updated monthly. Together the two answer a question our Web Almanac piece on structured-data adoption does not: not how many pages carry structured data, but how large the vocabulary they draw from actually is, and how its real-world usage is now measured at the term level.

The vocabulary in numbers#

Schema.org’s schemas.html page stated the count directly for version 30.0: “The vocabulary currently consists of 823 Types, 1529 Properties 19 Datatypes, 96 Enumerations and 535 Enumeration members.” Version 30.1, released 16 September 2026, has since moved the live page to 826 Types, 1540 Properties and 544 Enumeration members. Version 30.0 shipped 19 March 2026 with equivalence annotations and EU Digital Product Passport examples added on top of the existing schema. The releases.html changelog shows a steady release cadence rather than one big jump: 29.0 in March 2025 added vocabulary for financial incentives, legislation and product shipping; 29.3 in September 2025 expanded recipe-ingredient and marketplace terms; 29.4 in December 2025 covered “many schema and infra updates” before 30.0 landed the following March. Schema.org’s public release notes do not publish a type-by-type historical count for older versions, so this piece reports the current, verified snapshot rather than inventing a growth percentage the source does not state.

The new usage-statistics dataset#

On 4 June 2026, Schema.org’s blog announced a dataset built in collaboration with Google: aggregate usage statistics for schema.org terms across the public web, “available on the official Schema.org GitHub repository in CSV and JSON formats.” The post states the dataset is “updated monthly” and “offers a high-level view of term usage across millions of domains,” with this first release contributed by Google. That is a term-level view, not a page-level one: it shows how widely a given type or property is used, in popularity range buckets aggregated at the domain level, not whether any single site carries valid markup. Schema.org’s own post names no specific domain-count figure beyond “millions of domains,” so a publisher using this dataset gets adoption signal at the vocabulary-term level, a different unit than the format-level presence counts a page-crawl study like the Web Almanac reports.

Why we care#

Vocabulary size and page adoption are different measurements, and conflating them misleads. The Web Almanac’s 41% JSON-LD figure counts pages carrying the format; this dataset counts how often specific schema.org terms appear across domains. A publisher deciding which types to implement needs the second number, not the first.

The dataset is new enough that the useful move right now is understanding its shape, not its trend. Schema.org has published no prior version of this usage data, so there is no year-over- year comparison to report yet. What is verifiable today is that Google backed a monthly-updated, publicly downloadable term-usage dataset, which is itself the news.

The 823-type figure is a snapshot, not a growth rate. Version 30.1 already lists 826. Without a comparable historical count from schema.org’s own documentation, any percentage claiming the vocabulary “grew by X%” since an earlier version would be invented. The honest claim is the current count, sourced directly, and the cadence of releases that produced it.