The 44 controls / TS22
TS22 · Internationalisation
Each hreflang variant points to an indexable canonical URL.
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, http, html, intent
- When it applies
- Localized variant clusters using hreflang.
- How to check
- Parse HTML, HTTP or sitemap annotations and resolve every URL.
- Expectation
- Each cluster target is accessible, intended for indexing and consistent with its canonical; language/region codes are checked.
- Evidence to retain
- Valid language/region, 200 response and consistent canonical.
- Non-applicability
- No hreflang cluster in scope, with an inventory provided.
- Limitations
- hreflang helps targeting; it does not replace genuinely localized content.
- 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.