TS31Structured data

Do structured data describe visible content?

JSON-LD describes entities that are visible and appropriate to the content.

Prepare evidence

In the app: Evidence import
You provide: JSON-LD and matching content
Allow for: Depends on evidence needed

Prepare evidence

Understand

What the markup says. What visitors see.

JSON-LD describes entities that are visible and appropriate to the content.

According to Google

Markup should represent visible page content. Following the guidelines can enable a rich result but does not guarantee its display.

General structured data guidelines Source accessed on 2026-10-26

Check

Data makes claims. Does content confirm them?

In TSEP Control

You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.

Your contribution

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

With your own tools

Compare every structured property with visible content. Use the Rich Results Test for supported types and read the guidelines for the relevant type.

Evidence to retain

Valid, consistent graph with no invented entity or rating.

What this result covers

Valid markup guarantees neither a rich result nor higher rankings.

Act

Faithful data. Matching visible facts.

Fix properties and remove entities or claims absent from visible content.

Recheck

Content changes. Does the markup follow?

After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.

Your reference points

To go further.

Statuses, sources and method.

Understand the statusesC · NC · NT · NA

The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.

C · Verified: The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
NC · To correct: Fix properties and remove entities or claims absent from visible content.
NT · Not established: Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
NA · Not applicable: The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.

Sources and references1 reference

General structured data guidelinesdevelopers.google.com · new tab

Detailed method and rules3 rules

Control method and criteria

Method
Compare each important property with visible content and type-specific guidance.

Acceptance criteria
Examined syntax and properties match visible facts and the selected type; no fabricated data is observed.

Non-applicability
No structured data published in scope.

Detailed rules

TS31-A01 · Reviewed prior scope and hypotheses.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Selected page with JSON-LD; planned source and DOM profile.

Evidence
Native HTTP, attributed trees, supplied contexts/guidance, recomputed graphs and bound reviews; jsonld-visible-content-v1 contract.

Method
Qualify the plan, dated guidance and bound prior scope/source-base/guidance review.

Acceptance criteria
Three supported judgments; bound contradiction fails, missing or unknown review is inconclusive.

When the result remains inconclusive
Gaps, bounds, missing context/runtime, ambiguous reading, empty graph, notice or unknown review; independent contradictions preserved.

Non-applicability
No atomic exemption; absence in a bounded profile does not establish NA.

Assumptions
Supplied scope, bases, dates, visible content and judgments; hashes do not authenticate.

Limitations
JSON-LD and documentary review of the selected page; no Schema.org vocabulary validation, authenticated truth/visibility, rich result, indexing or ranking.

TS31-A02 · Attributed source and rendered JSON-LD reading.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Selected page with JSON-LD; planned source and DOM profile.

Evidence
Native HTTP, attributed trees, supplied contexts/guidance, recomputed graphs and bound reviews; jsonld-visible-content-v1 contract.

Method
Recompute exact scripts under both source hypotheses and all planned DOM states using supplied contexts.

Acceptance criteria
Complete readings and at least one nonempty graph without notices; attributed invalid JSON fails, other limits are inconclusive.

When the result remains inconclusive
Gaps, bounds, missing context/runtime, ambiguous reading, empty graph, notice or unknown review; independent contradictions preserved.

Non-applicability
No atomic exemption; absence in a bounded profile does not establish NA.

Assumptions
Supplied scope, bases, dates, visible content and judgments; hashes do not authenticate.

Limitations
JSON-LD and documentary review of the selected page; no Schema.org vocabulary validation, authenticated truth/visibility, rich result, indexing or ranking.

TS31-A03 · Content and type consistency reviewed per entity.

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Selected page with JSON-LD; planned source and DOM profile.

Evidence
Native HTTP, attributed trees, supplied contexts/guidance, recomputed graphs and bound reviews; jsonld-visible-content-v1 contract.

Method
Bind supplied content and every flattened node to complete reviews covering visibility, type, all properties and absence of fabrication.

Acceptance criteria
Exact population and supported qualifications; bound supplied contradiction fails, gaps or unknowns are inconclusive.

When the result remains inconclusive
Gaps, bounds, missing context/runtime, ambiguous reading, empty graph, notice or unknown review; independent contradictions preserved.

Non-applicability
No atomic exemption; absence in a bounded profile does not establish NA.

Assumptions
Supplied scope, bases, dates, visible content and judgments; hashes do not authenticate.

Limitations
JSON-LD and documentary review of the selected page; no Schema.org vocabulary validation, authenticated truth/visibility, rich result, indexing or ranking.

Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source

Put it into practice

← Back to controls