The 44 controls / TS40
TS40 · Internationalisation
The hreflang methods in use are complete and consistent.
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, sitemap, http, html, intent
- When it applies
- Clusters using at least one hreflang method.
- How to check
- Identify all published methods, verify clusters and compare annotations when methods coexist.
- Expectation
- Each used method covers the cluster; if several are published, their annotations are consistent; no single-method requirement is imposed.
- Evidence to retain
- Equivalent reciprocal clusters; when sitemaps are used, valid xhtml namespace and entries per URL.
- Non-applicability
- No hreflang annotations in scope.
- Limitations
- Combining HTML, headers and sitemaps offers no search benefit and increases divergence risk.
- 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.