The 44 controls / TS25

TS25 · JavaScript and rendering

Critical content exists in source HTML or becomes observable after rendering.

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)
html, render, intent
When it applies
Templates whose critical elements are listed.
How to check
List critical elements, then compare source HTML and rendered DOM under declared conditions. Optional Google inspection is a separate additional observation.
Expectation
Every critical element is observed at the declared source or rendered stage; engine, version and conditions are retained; no equivalence with Google is inferred.
Evidence to retain
Title, content, links, canonical and structured data present at the right stage.
Non-applicability
No relevant HTML document in scope.
Limitations
A local browser does not reproduce Google’s rendering exactly.
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.

Control references