Structured Data Benchmark 2026: JSON-LD in the URL sample
Structured data makes content more explicit: organization, website, breadcrumbs, articles, products or local company data become easier to read for machines.
Structured data makes content more explicit: organization, website, breadcrumbs, articles, products or local company data become easier to read for machines.
Structured data available: 39 % (Average of domain values) from 68,464 evaluable domain values in the selected segment. The number describes the sample examined, not all websites or all URLs of these domains.
This metric recognizes JSON-LD script blocks in HTML. Microdata and RDFa are not included here. Also, an existing but invalid JSON-LD block can increase the presence value.
Many websites have visible content, but little additional semantic information. For rich results, knowledge graph signals and AI systems, this can make a difference, especially when competitors mark cleaner.
The benchmark shows whether a website has a basic level or a need to catch up when it comes to semantic markup. What matters is not only whether markup exists, but whether it fits the page type.
The benchmark alone does not yet say which measure should be implemented first. In the website audit, the value is combined with URL type, severity, priority and specific findings.
Compare your own domainstructured_data_present checks whether at least one script with type="application/ld+json" occurs. The indicator is not a passed schema or rich-result test.
A product page with JSON-LD and missing price can count as existing. Another page with complete microdata can still get 0 for this metric.
Compare product pages with product pages and articles with articles. Not every page type needs the same schema types or is suitable for the same search presentation.
Validate syntax, mandatory fields and match with visible content separately. A technically valid award does not guarantee a special search presentation.
A benchmark is a benchmark, not an absolute truth. Important is the deviation to the own website and the question of whether the signal for the affected pages is business relevant.
The baseline takes numerical metrics from the latest stored crawl per domain into account, if this was successful. Missing values do not enter as 0. Segments are only calculated from five available domain values. The selection is not a random sample and not a representative market share.
The current sampler selects up to ten URLs from sitemap or internal links; successful retrievals are combined into a domain mean for each metric. Older data sets can be based on a single page. In the case of shares, the page shows the mean value of the domain values, in the case of ALT coverage their median. Not all URLs of a website are examined.
Canonicals are a quiet but important indexing signal: they help search engines merge variants of a page cleanly.
SnippetsMeta descriptions are not a direct ranking lever, but they do influence how convincing a page is in the search result.
SecurityHSTS is not a classic content signal, but a clear sign of technical maturity: browsers should only retrieve the website encrypted.