Structured Data (schema.org/JSON-LD) Coverage
stableCategory: entity · Methodology v4.5
Where the structured-data parameter asks whether any JSON-LD exists, this one measures how broad and rich it is.
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
What this parameter measures
Where the structured-data parameter asks whether any JSON-LD exists, this one measures how broad and rich it is. friendly4AI parses every <script type="application/ld+json"> block on your homepage, collects the distinct @type tokens (such as Organization, WebSite, Product, BreadcrumbList, FAQPage), and inspects commerce blocks for attributes like offers, price, and availability. It is the coverage companion to the structured-data parameter: that one checks presence of the core types, this one rewards multi-entity depth.
Why it matters for AI-readiness
A single Organization block tells an AI system who you are; a rich graph spanning Organization, WebSite, Product, and FAQPage tells it what you sell, how your site is structured, and what questions you answer. The more valid entity types you expose, the more accurately ChatGPT, Gemini, and Perplexity can describe your business and cite specific offerings rather than vague summaries. Commerce attributes in particular let AI shopping and comparison features surface your products with correct prices and availability.
How we score it
Under the v4.4 methodology (v2.2 scoring), this Discovery parameter runs through the coverage branch of the structured-data processor and resolves to three tiers. It passes (100) when coverage is broad: 3 or more distinct @type tokens, OR both WebSite and Organization present, OR at least 2 JSON-LD blocks carrying 2 or more types between them; a commerce block whose completeness clears the full-score threshold also lifts the result to 100 even if the type count is lower. It scores partial (50) when at least one valid JSON-LD block is present but coverage stays below those thresholds. It fails (0) when no valid JSON-LD is detected at all. Malformed blocks are tracked but do not by themselves create a partial — the gate is whether any valid types survive parsing.
How to fix common issues
- Start with
OrganizationandWebSiteJSON-LD in your homepage<head>; that pair alone reaches the pass tier. - Add the entity types that match your business —
ProductorService,BreadcrumbList, andFAQPage— to broaden coverage past 3 distinct types. - For commerce sites, 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 contributes nothing to the type count.
- Keep each block well-formed JSON with a correct
@contextand@type; see the relatedstructured-dataparameter for the presence baseline. - Re-scan after publishing to confirm the new types are detected.
Version History
- Introduced
- v4.0
- Last changed
- v4.4
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 …