The 44 controls / TS12
TS12 · Canonicalisation
Google’s selected canonical is compared with the declared canonical.
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)
- search-console, html, intent
- When it applies
- URLs whose Google canonical must be compared with the declared canonical.
- How to check
- Inspect priority URLs and record the user-declared and Google-selected canonicals.
- Expectation
- Both values are timestamped and compared; each discrepancy has an assessment and a decision.
- Evidence to retain
- Agreement or a qualified, addressed divergence.
- Non-applicability
- Google explicitly out of scope; missing access is NT.
- Limitations
- Google’s selected canonical can change after recrawling.
- 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.