TS39Performance and deployment

Does delivery serve consistent signals to everyone?

The CDN, Vary and geolocation do not serve contradictory SEO signals.

Prepare evidence

In the app: Evidence import
You provide: Contexts, responses and cache traces
Allow for: Depends on evidence needed

Prepare evidence

Understand

A different context. Consistent signals.

The CDN, Vary and geolocation do not serve contradictory SEO signals.

According to Google

Google may not discover every content variant adapted to a visitor’s country or language. It recommends separate URLs with hreflang annotations.

How Google crawls locale-adaptive pages Source accessed on 2026-10-26

Check

The context varies. Does the response too?

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

Compare dated responses across languages, locations and cache states allowed by your plan. Record content, canonical, directives and variation headers without inferring location from a User-Agent alone.

Evidence to retain

Configuration, prior matrix, native HTTP, rendered states or positive exemptions, bound reviews and cache journals where tested. Googlebot access policy is qualified separately from test-client requests; no actual visit inferred.

What this result covers

First bounded profile with one canonical member per cell and reuse without transformation. Supplied reviews, sources, regions, clocks and logs are not authenticated; no general cache simulation. Two points do not cover all POPs/routes, and C does not establish actual Googlebot access.

Act

Caching and variation. In the right place.

Fix cache, Vary or geolocation rules that produce conflicting signals.

Recheck

Caches invalidated. Contexts replayed.

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: Fix cache, Vary or geolocation rules that produce conflicting 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 references2 references

Detailed method and rules3 rules

Control method and criteria

Method
Declare and review matrix, configuration and policy before collection; compare native signals, content and access per cell; qualify contexts and cache reuse through bound evidence under delivery-evidence-v1.

Acceptance criteria
All three rules pass over declared cells: reviewed policy, consistent signals and attributed mechanisms; legitimate variations, independent defects and unqualified cells remain distinct.

Non-applicability
Configuration attests to the absence of variation mechanisms.

Detailed rules

TS39-A01 · Reviewed prior matrix and configuration

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

Scope
Delivery varying by region, cache, device or negotiation.

Evidence
Configuration, prior matrix, native HTTP, rendered states or positive exemptions, bound reviews and cache journals where tested. Googlebot access policy is qualified separately from test-client requests; no actual visit inferred.

Method
Check window, cells, mechanisms, retained configuration and bound prior review, including representativeness and Googlebot access policy.

Acceptance criteria
Configuration and matrix qualified by supported review; documented rejection = fail.

When the result remains inconclusive
Missing, late or unbound configuration/review; unqualified matrix minimum or mechanism.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied intent, context and source/review qualifications; their truth remains to verify.

Limitations
First bounded profile with one canonical member per cell and reuse without transformation. Supplied reviews, sources, regions, clocks and logs are not authenticated; no general cache simulation. Two points do not cover all POPs/routes, and C does not establish actual Googlebot access.

TS39-A02 · Signal consistency in each context

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

Scope
Delivery varying by region, cache, device or negotiation.

Method
Compare status/final URL, recalculate TS07-A01/A02/A03 and TS10-A01, then compare language/content/accessibility through bound reviews; retain each unknown.

Acceptance criteria
All cells follow policy; positive rendering exemption retained. Any attributable contradiction fails despite other unknowns.

When the result remains inconclusive
Missing cell, source, rendering, review or profile; incomplete body, unbound context or unknown semantics.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied intent, context and source/review qualifications; their truth remains to verify.

TS39-A03 · Context and cache attribution

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

Scope
Delivery varying by region, cache, device or negotiation.

Method
Qualify contexts/mechanisms through bound sources; for cache, link stored entry, served request, layer, clock, Vary and freshness review.

Acceptance criteria
Consistent attribution and policy over all cells/checks; attributed reuse incompatible with Vary or policy fails. A test is not an operator visit.

When the result remains inconclusive
Unqualified region, source, journal, linkage or freshness; Age/HIT, User-Agent, sequence or ETag alone are insufficient.

Non-applicability
No automatic atomic exemption.

Assumptions
Supplied intent, context and source/review qualifications; their truth remains to verify.

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

Put it into practice

← Back to controls