The 44 controls / TS20
TS20 · URL spaces
The URL structure is readable, stable and correctly encoded.
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)
- crawl, configuration, intent
- When it applies
- Published URL patterns.
- How to check
- Identify spaces, fragments, encoded characters, case and volatile identifiers.
- Expectation
- Encoding, case, stability and variations match declared rules; no observed unintended variant is left without a decision.
- Evidence to retain
- Documented URL patterns and no unintended variants.
- Non-applicability
- No public URL in scope.
- Limitations
- A readable URL is not sufficient evidence of SEO performance.
- 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.