The 44 controls / TS27
TS27 · JavaScript and rendering
SPA states and routes produce shareable URLs and consistent server responses.
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)
- http, render, intent
- When it applies
- Application routes or SPA states intended for indexing.
- How to check
- Open routes directly and test refresh, history, canonical and HTTP status.
- Expectation
- Direct opening, refresh and history preserve the expected URL, content, status and signals for each selected route.
- Evidence to retain
- Each indexable view has its own URL, 200 response, content and signals.
- Non-applicability
- No relevant application or SPA route.
- Limitations
- Choosing SSR, CSR or SSG is not in itself an SEO guarantee.
- 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.