The 44 controls / TS33
TS33 · Structured data
Errors, warnings and unsupported uses are distinguished.
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, validator-output, intent
- When it applies
- Markup whose validity and eligibility are assessed.
- How to check
- Test Schema.org syntax and Google eligibility separately; record both results.
- Expectation
- Syntax, vocabulary, engine eligibility and warnings are separated; each result has a tool, version/date and decision.
- Evidence to retain
- Report with no blocking error and qualified warnings.
- Non-applicability
- No structured markup in scope.
- Limitations
- Rich Results Test does not validate the whole Schema.org vocabulary.
- 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.