Structured Data (schema.org/JSON-LD) Coverage
stableCategory: entity · Methodology v4.5
Think of it as the depth half of structured data.
Signal Source
- Source
https://{domain} (homepage HTML)- Kind
- html_dom
Score Bands
| Verdict | Condition |
|---|---|
| Pass | broad JSON-LD coverage: 3 or more distinct @type tokens, OR both WebSite and Organization types, OR 2+ JSON-LD blocks carrying 2+ types; rich commerce attributes (e.g. Product offers, price, availability) also reach the top tier |
| Partial | at least one valid JSON-LD block is present but coverage is limited — fewer than 3 distinct types and no WebSite + Organization pair |
| Fail | no valid JSON-LD structured data is detected on the page |
Description
Structured Data Coverage measures how broad and rich your homepage JSON-LD is, not just whether any exists at all. friendly4AI reads every <script type="application/ld+json"> block on the homepage, counts the distinct @type tokens it finds — Organization, WebSite, Product, BreadcrumbList, FAQPage, and so on — and checks commerce blocks for offers, price, and availability. Broad coverage scores 100, limited coverage 50, and no valid JSON-LD 0.
What does this parameter measure?
Think of it as the depth half of structured data. The structured-data parameter checks whether the core types show up; this one rewards how many distinct entities you describe. The signal comes from the rendered homepage HTML DOM. We score coverage by counting the valid, distinct @type tokens that survive JSON-LD parsing, then weigh in how complete any commerce (Product) block is.
Why does coverage matter for AI-readiness?
A lone Organization block tells an AI system who you are. A graph that spans Organization, WebSite, Product, and FAQPage tells it what you sell, how your site is laid out, and which questions you already answer. Expose more valid entity types and ChatGPT, Gemini, and Perplexity can describe your business more precisely — citing specific offerings instead of falling back on vague summaries. Commerce attributes go a step further: AI shopping and comparison features can pull your products with the right prices and availability. This is a Discovery parameter weighted for Bing, the engine that reads schema.org markup most directly.
How is Structured Data Coverage scored?
This parameter has been stable since v4.0. Under the v4.5 methodology it runs through the coverage branch of the structured-data processor and lands in one of three tiers:
- Pass (100) — coverage is broad. That means 3 or more distinct
@typetokens, OR bothWebSiteandOrganizationpresent, OR at least 2 JSON-LD blocks carrying 2 or more types between them. A commerce block that clears the full-score completeness threshold also reaches 100, even when the type count alone would not. - Partial (50) — at least one valid JSON-LD block exists, but coverage stays under those thresholds: fewer than 3 distinct types, and no
WebSite+Organizationpair. - Fail (0) — no valid JSON-LD structured data is detected on the page.
Malformed blocks get tracked, but they do not produce a partial on their own. What matters is whether any valid types survive parsing.
How do you fix low coverage?
- Add
OrganizationandWebSiteJSON-LD to your homepage<head>. That pair alone reaches the pass tier. - Layer on the entity types that fit your business —
ProductorService,BreadcrumbList,FAQPage— to push past 3 distinct types. - Running a commerce site? Populate
offers,price,priceCurrency, andavailabilityso the commerce-completeness path can earn full credit. - Validate every block at search.google.com/test/rich-results. A block that fails to parse adds nothing to the type count.
- Keep each block well-formed JSON with a correct
@contextand@type. Seestructured-datafor the presence baseline andcontent-type-schema-matchfor matching schema to page intent. - Re-scan after publishing to confirm the new types are detected.
Version History
- Introduced
- v4.0
- Last changed
- v4.5
Key takeaways
- Signal: https://{domain} (homepage HTML)
- Category: Entity & Schema
- Passes when: broad JSON-LD coverage: 3 or more distinct @type tokens, OR both WebSite and …