The 44 controls / TS11
TS11 · Canonicalisation
Genuine duplicate variants converge without hiding distinct pages.
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)
- content, html, intent
- When it applies
- Identified duplicate or variant families.
- How to check
- Sample parameters, pagination, filters and print versions; compare content and canonicals.
- Expectation
- Each mapping is justified by content comparison; no tested distinct page is unintentionally consolidated.
- Evidence to retain
- Documented mapping between each duplicate and its relevant canonical.
- Non-applicability
- No variants or duplication identified after a documented inventory.
- Limitations
- Computed similarity does not replace an editorial decision.
- 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.