TSEPCONTROL FREE BETA
Menu

Where would you like to go?

Navigation only · no analysis is started

TS44Content and rendering

Can the intended agents access the content?

Critical content and evidence remain accessible without undocumented JavaScript execution.

Prepare evidence
In the app
Evidence import
You provide
Critical content, responses and rendering
Allow for
Depends on evidence needed
Prepare evidence

Understand

Every agent. Its own reading capabilities.

Critical content and evidence remain accessible without undocumented JavaScript execution.

TSEP protocol criterion

The TSEP check compares critical content with the declared consumer’s capabilities and conditions. Browser rendering does not prove every agent can access it.

The rules and limits of this check are detailed at the bottom of this guide.

Check

What the agent reads. What the page requires.

In TSEP Control

From an analysis, “Investigate further” lets you prepare available supplementary observations. This guide’s workflow also lets you gather and import the evidence required by the rules.

Your contribution

Define the scope and expectations before collection. Gather the items below and supply the requested reviews.

With your own tools

List essential content, then compare the HTTP response with rendered content. Consult documented capabilities of the target agent and record dependencies on scripts, interaction or authentication.

Evidence to retain

Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.

What this result covers

First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.

Act

Essential content. At the right stage.

Expose the expected content at the intended stage and document any JavaScript dependency.

Recheck

Same agent. Same conditions.

After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.

Your reference points

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
Expose the expected content at the intended stage and document any JavaScript dependency.
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 references3 references

  1. Understand the JavaScript SEO basicsdevelopers.google.com · new tab
  2. OpenAI — Overview of crawlersdevelopers.openai.com · new tab
  3. Anthropic — Web crawling and crawler controlssupport.claude.com · new tab
Detailed method and rules3 rules

Control method and criteria

Method
Declare critical facts and paths before collection; verify no-JS access, values and exact representation reviews under critical-content-nojs-v1.

Acceptance criteria
All three rules pass for the no-JavaScript reference client, with qualified delivery, coherent values and bound reviews; no actual consumption inferred.

Non-applicability
No content intended for these consumers in scope.

Detailed rules

TS44-A01 · Prior critical scope

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Content intended for declared automated consumers.

Evidence
Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.

Method
Check inventory, no-JS client, planned states/resources and bound review predating captures.

Acceptance criteria
Complete scope supported by review; bound rejection = fail.

When the result remains inconclusive
Missing, late, unbound or incomplete plan/review, or different reference capability.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.

Limitations
First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.

TS44-A02 · Delivery path without JavaScript

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Content intended for declared automated consumers.

Evidence
Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.

Method
Check the prior path, explicit resource link if needed, anonymous HTTP and all critical elements.

Acceptance criteria
Expected destination/response and present elements; any qualified denial, wrong path or absence fails.

When the result remains inconclusive
Missing capture, unsupported format/runtime/link/context or incomplete unqualified reading.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.

Limitations
First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.

TS44-A03 · Value and context coherence

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Content intended for declared automated consumers.

Evidence
Prior plan/review, complete HTTP chains, raw HTML/JSON, attributed rendered tree and bound context reviews.

Method
Compare qualified values from each representation/rendered state to the plan; review whole critical context with representation-specific bindings.

Acceptance criteria
Coherent values and reviews; qualified contradiction retained despite other missing evidence.

When the result remains inconclusive
Missing/unknown review, rendering, value or attribution; unplanned supplied state or unsupported context.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied inventory, expected references, context and reviews; scope fixed before capture, unauthenticated evidence.

Limitations
First bounded HTML/JSON profile, optional Node and supplied rendered evidence; no authenticated CSS visibility, truth, reviewer identity, ingestion or citation. Authored DOM explicitly synthetic.

Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source

Put it into practice

Your next check starts here.

Critical content, responses and rendering.

Prepare evidence
← Back to controls

30 readings available today

Renews:

Your daily limit: 30 readings

How it works

One reading checks your page and a few public sources. The allowance applies to your visitor workspace; additional protections apply to the shared network and the service as a whole.

Answering questions, viewing saved work and exporting results do not consume readings. These steps remain available when the allowance is used.