Structured data: distinguish valid JSON-LD from rich results

At a glance

JSON-LD describes information using a structured vocabulary. Valid syntax guarantees neither Google feature eligibility, rich display nor citation by an AI system.

Empty intelligence archive with dossiers and maps Illustration · fictional scene
In this article

Four levels of checking

Choose a type describing the page’s actual content. Google recommends JSON-LD among its accepted formats, but only certain uses have documented search features. The table separates frequently confused checks.

LevelQuestion checkedWhat it does not establish
JSON syntaxDoes the text decode correctly?Factual accuracy.
Schema.org vocabularyAre types and properties suitable?Support by a Google search feature.
Google eligibilityAre the intended feature’s rules met?Actual display in searches.
Actual observationWas an appearance observed?Permanent display or display for every query.

Keep data aligned with the page

  • Connect each property to accurate, visible and current information. Do not invent reviews, qualifications or prices to fill markup.
  • Check required properties and rules for the intended feature. An existing Schema.org type does not automatically mean a Google rich result is available.
  • Use consistent entity identifiers and avoid conflicting blocks from different components. Also check language versions and URLs.

Monitor without promising visibility

Test rendered markup, then follow diagnostics and actual appearances in Search Console. Correct stale information alongside visible content. A successful test means a check passed, not a promise of positions, clicks or inclusion in generated answers.

Primary references

Test JSON-LD after a business-data change

Fictional example: these inputs describe no customer or observed result.

The displayed price changes, but a JSON-LD object built by another module retains the old value.

  • Check a published page and its variants against visible price and the authorised business source.
  • Restore consistency and check future data changes. Valid JSON does not establish that its values are true.

Primary reference: Google Search Central — General structured data guidelines. Related method: read the practical guide.