Browse sections
What does this check look at?
At least one <script type="application/ld+json"> block parses as JSON and declares at least one @-keyword (@context, @type, @graph or @id). A block containing only {} parses but declares nothing, so it does not count.
The first twenty JSON-LD blocks in the document are the ones examined, so a page that emits a block per component is read only as far as its twentieth. A block that fails to parse does not stop the ones after it from being read, because each is parsed on its own.
How do I fix it?
- Add a JSON-LD @graph with Organization and WebSite nodes.
Why is it worth 5 points?
Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:
| Dimension | Machine Readability — 12% of the total score |
| Points for this check | 5 of 12 in this dimension |
| Worth at most | 5.0 of the 100 points |
Second highest. It is deterministic and fully in your control, and it is what makes entity disambiguation possible.
Which dimension does this belong to?
Machine Readability — 12% of the total score, decided by 3 published rules.
JSON-LD is how a model binds your brand name, domain and product into one entity instead of inferring three unrelated strings.
The fix for this rule is walked through step by step in the schema org jsonld guide.
What else is measured in this dimension?
- An entity node is declared — 4 points
- Content-type schema is present — 3 points
How do I see my own result?
Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.
Run a free GEO audit on your own site →
The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.
Questions about this rule
What does this check look at?
At least one <script type="application/ld+json"> block parses as JSON and declares at least one @-keyword (@context, @type, @graph or @id). A block containing only {} parses but declares nothing, so it does not count.
Why does this dimension carry 12% of the score?
It is deterministic and fully in your control, and it is what makes entity disambiguation possible.
Evidence and sources
GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024
This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.
Primary sources
- Generative Engine Optimization (KDD 2024) — the measured gains the citability weight follows
- What Generative Search Engines Like — what generative engines prefer in retrieved content
- What Gets Cited: Competitive GEO — which of two competing sources is cited first
- The rule set and its weights — every check, its weight and its pass condition