The 44 controls / TS23
TS23 · Internationalisation
hreflang annotations are reciprocal and include the current page.
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)
- hreflang, intent
- When it applies
- Declared hreflang clusters.
- How to check
- Build variant clusters and verify return links and self-references.
- Expectation
- All pairs in the declared cluster are reciprocal and every variant includes itself; cluster boundaries are retained.
- Evidence to retain
- Complete reciprocal cluster with no conflicting URL.
- Non-applicability
- No hreflang cluster in scope.
- Limitations
- A valid cluster does not prove the engine will always serve the expected variant.
- 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.