TS26Content and rendering
Content and renderingDoes rendering have all the resources it needs?
Resources required for rendering are neither blocked nor failing.
Prepare evidence
- In the app
- Evidence import
- You provide
- Critical resources and responses
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
A resource is missing. Does the content survive?
Resources required for rendering are neither blocked nor failing.
According to Google
Google does not render pages or JavaScript files blocked from crawling. Inaccessible essential resources can therefore prevent the expected render.
Check
Requests fail. What is missing?
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
Reload the page in developer tools and examine failed requests, the console and required resources. Compare with resources shown by Google’s inspection test.
Evidence to retain
Critical resources accessible and no error removes essential content.
What this result covers
An error-free console does not prove indexing.
Act
Restore the resource. Recover the content.
Restore required scripts, styles or data and check the resulting content.
Recheck
Without the old cache. The expected rendering?
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
- Restore required scripts, styles or data and check the resulting content.
- 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
Inspect network activity, robots rules, CSP and console errors on priority templates.
Acceptance criteria
No tested critical resource is prevented by network error, robots policy or CSP; console and network evidence are retained.
Non-applicability
No dependent rendering resource, supported by an inventory.
Detailed rules
TS26-A01 · Resource access and native policies
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS26 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, robots, html, intent.
Method
For each selected critical resource compare direct HTTP200, same-origin robots and intersection of HTTP CSP policies from the HTTPS document. Retain complete source to exclude unqualified meta CSP.
Acceptance criteria
A qualified HTTP error, robots denial or CSP denial fails independently of other gaps.
When the result remains inconclusive
Absent inventory, missing robots, unsupported CSP directive, nonce, meta CSP, ambiguous source 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.
TS26-A02 · Traffic and console attributed to rendering
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS26 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: render, http, intent.
Method
Read a supplied bounded HAR export, bind its document response to native HTTP bytes, then check every critical resource. Retain dated HAR-bound console and criticality review.
Acceptance criteria
Selected resources have2xx responses without supplied network error. Unclassified console errors remain NT; native network failure remains NC.
When the result remains inconclusive
Incomplete HAR, omitted body, unattributed context/session, missing console or unqualified error: 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
Critical resources and their responses.