The 44 controls / TS39
TS39 · Performance and monitoring
The CDN, Vary and geolocation do not serve contradictory SEO signals.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.28
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)
- http, configuration, intent
- When it applies
- Delivery varying by region, cache, device or negotiation.
- How to check
- 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.
- Expectation
- All three rules pass over declared cells: reviewed policy, consistent signals and attributed mechanisms; legitimate variations, independent defects and unqualified cells remain distinct.
- 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.
- Non-applicability
- Configuration attests to the absence of variation mechanisms.
- 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.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- RFC 9110 defines Vary and HTTP response semantics. Google separately documents locale-adaptive page behavior.
Atomic rules
TS39-A01 — Reviewed prior matrix and configuration
- Required inputs (protocol identifiers)
- configuration, intent
- When it applies
- Delivery varying by region, cache, device or negotiation.
- How to check
- Check window, cells, mechanisms, retained configuration and bound prior review, including representativeness and Googlebot access policy.
- Expectation
- Configuration and matrix qualified by supported review; documented rejection = fail.
- 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.
- Assumptions
- Supplied intent, context and source/review qualifications; their truth remains to verify.
- Inconclusive outcome
- Missing, late or unbound configuration/review; unqualified matrix minimum or mechanism.
- Non-applicability
- No automatic atomic exemption.
- 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
- Required inputs (protocol identifiers)
- http, content, intent
- When it applies
- Delivery varying by region, cache, device or negotiation.
- How to check
- Compare status/final URL, recalculate TS07-A01/A02/A03 and TS10-A01, then compare language/content/accessibility through bound reviews; retain each unknown.
- Expectation
- All cells follow policy; positive rendering exemption retained. Any attributable contradiction fails despite other unknowns.
- 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.
- Assumptions
- Supplied intent, context and source/review qualifications; their truth remains to verify.
- Inconclusive outcome
- Missing cell, source, rendering, review or profile; incomplete body, unbound context or unknown semantics.
- Non-applicability
- No automatic atomic exemption.
- 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-A03 — Context and cache attribution
- Required inputs (protocol identifiers)
- configuration, http, logs, intent
- When it applies
- Delivery varying by region, cache, device or negotiation.
- How to check
- Qualify contexts/mechanisms through bound sources; for cache, link stored entry, served request, layer, clock, Vary and freshness review.
- Expectation
- Consistent attribution and policy over all cells/checks; attributed reuse incompatible with Vary or policy fails. A test is not an operator visit.
- 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.
- Assumptions
- Supplied intent, context and source/review qualifications; their truth remains to verify.
- Inconclusive outcome
- Unqualified region, source, journal, linkage or freshness; Age/HIT, User-Agent, sequence or ETag alone are insufficient.
- Non-applicability
- No automatic atomic exemption.
- 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.