The 44 controls / TS31
TS31 · Structured data
JSON-LD describes entities that are visible and appropriate to the content.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.19
Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier
Expectations and evidence
- Required inputs (protocol identifiers)
- structured-data, content, intent
- When it applies
- Documents publishing structured data.
- How to check
- Compare each important property with visible content and type-specific guidance.
- Expectation
- Examined syntax and properties match visible facts and the selected type; no fabricated data is observed.
- Evidence to retain
- Valid, consistent graph with no invented entity or rating.
- Non-applicability
- No structured data published in scope.
- Limitations
- Valid markup guarantees neither a rich result nor higher rankings.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- Technical reference; the TSEP acceptance rule remains an editorial proposal.
Atomic rules
This control is documented in the protocol. This version does not yet attach executable atomic rules to it.