TS27Content and rendering
Content and renderingDoes every application view have a usable URL?
SPA states and routes produce shareable URLs and consistent server responses.
Prepare evidence
- In the app
- Evidence import
- You provide
- Routes and direct-load responses
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
One view. An address to reach it.
SPA states and routes produce shareable URLs and consistent server responses.
According to Google
Google recommends examining rendered DOM, resources and JavaScript errors with its testing tools. TSEP also compares each view with its route and expected signals.
Check
Enter directly. Then reload.
In TSEP Control
You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.
Your contribution
Define the scope and expectations before collection. Gather the items below and supply the requested reviews.
With your own tools
Paste each view URL directly into a new tab and reload it. Record HTTP status, content, title and canonical; also test links between views.
Evidence to retain
Each indexable view has its own URL, 200 response, content and signals.
What this result covers
Choosing SSR, CSR or SSG is not in itself an SEO guarantee.
Act
Every view. Its consistent route.
Give each indexable view a shareable URL, response and consistent signals.
Recheck
Direct access. Navigation too.
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
To go further.
Statuses, sources and method.
Understand the statusesC · NC · NT · NA
The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.
- C · Verified
- The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
- NC · To correct
- Give each indexable view a shareable URL, response and consistent signals.
- NT · Not established
- Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
- NA · Not applicable
- The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.
Sources and references1 reference
Detailed method and rules2 rules
Control method and criteria
Method
Open routes directly and test refresh, history, canonical and HTTP status.
Acceptance criteria
Direct opening, refresh and history preserve the expected URL, content, status and signals for each selected route.
Non-applicability
No relevant application or SPA route.
Detailed rules
TS27-A01 · Attributed routes and history
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS27 population under render-transport-v1; see docs/render-transport-evidence.md.
Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: http, render, intent.
Method
Check four supplied states in direct, refresh, back, forward order: session, sequence, time, URL, server-response binding and status.
Acceptance criteria
Every state retains its route URL and intended200 source. A qualified conflicting URL or status fails.
When the result remains inconclusive
Missing/ambiguous state, action, binding, session or order; uncollected frame/shadow surface: NT.
Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.
Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.
Limitations
No real audit inferred from synthetic cases. No indexing, ranking, global conformity, accessibility certification, exhaustive security or universal browser trust. Reviews may be wrong and captures may omit states.
TS27-A02 · Content and canonical in each SPA state
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS27 population under render-transport-v1; see docs/render-transport-evidence.md.
Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: http, render, intent.
Method
Within the same qualified states compare literal IDs, essential text and link destinations with the plan, then one explicit head canonical. Require operation review.
Acceptance criteria
States retain their intended content and signals. Absence on a complete surface, differing content or conflicting canonical fails.
When the result remains inconclusive
Partial state, hidden context, ambiguous ID, differing HTML hypotheses or absent review: NT.
Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.
Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.
Limitations
No real audit inferred from synthetic cases. No indexing, ranking, global conformity, accessibility certification, exhaustive security or universal browser trust. Reviews may be wrong and captures may omit states.
Rule version 0.3.0-draft.4 · Public protocol reference · Versioned source
Put it into practice
Routes and their direct-load responses.