TS36Performance and deployment
Performance and deploymentAre your decisions connected to dated observations?
Monitoring connects Search Console, logs and deployments to decision dates.
Prepare evidence
- In the app
- History · evidence import
- You provide
- Deployments, logs and Search Console
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
A decision. Its evidence and context.
Monitoring connects Search Console, logs and deployments to decision dates.
TSEP protocol criterion
This TSEP check links decisions with dated changes and observations. Proximity in time alone does not demonstrate causality.
The rules and limits of this check are detailed at the bottom of this guide.
Check
Before and after. And the evidence between.
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
With your own toolsMaintain a decision and deployment log. Link dated Search Console observations and logs, with scope and hypothesis; temporal sequence does not prove causality.
Evidence to retain
Deployment log, crawl/indexing anomalies and signed decisions.
What this result covers
Temporal correlation is not sufficient to attribute a traffic change.
Act
Connect the decision. To what was observed.
Connect each decision to its observations and to the date of the relevant change.
Recheck
A new decision. The history grows.
At each decision or deployment, add dated observations to the record. Connect before, after and the same expectations: this history is the evidence for the control.
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
- Connect each decision to its observations and to the date of the relevant change.
- 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 rules3 rules
Control method and criteria
Method
Create a pre-change baseline, then verify at D+1, D+7 and D+30 according to risk.
Acceptance criteria
Baseline, deployment and risk-based follow-up observations are dated; anomalies and decisions are linked without automatic causal attribution.
Non-applicability
No change subject to follow-up within the declared period.
Detailed rules
TS36-A01 · Prior plan and release chronology.
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Selected release whose dated follow-up is assessed.
Evidence
Bound plan/reviews, deployment receipt, native API and supplied normalized logs; release-monitoring-v1 contract.
Method
Qualify the bound plan before baseline, receipt identities and baseline/deployment order.
Acceptance criteria
Supported plan, matching identity and baseline recorded before deployment; explicit contradiction fails, gaps remain inconclusive.
When the result remains inconclusive
Future stage, missing evidence, errors, unknown values, incomplete logs or invalid bindings; preserve independent contradictions.
Non-applicability
No atomic exemption; absence or delay never establishes NA.
Assumptions
Supplied scope, dates, layer and judgments; hashes alone authenticate nothing.
Limitations
Documentary C for selected baseline/D+1/D+7/D+30; no causality, authenticated Google visit, indexing or global coverage.
TS36-A02 · Observations attributed to follow-up stages.
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Selected release whose dated follow-up is assessed.
Evidence
Bound plan/reviews, deployment receipt, native API and supplied normalized logs; release-monitoring-v1 contract.
Method
Read baseline/d1/d7/d30, qualify TS08-A02 API and exact-window log inventories.
Acceptance criteria
All four stages reached, complete attributed evidence within bounds; future/absence/error remains inconclusive.
When the result remains inconclusive
Future stage, missing evidence, errors, unknown values, incomplete logs or invalid bindings; preserve independent contradictions.
Non-applicability
No atomic exemption; absence or delay never establishes NA.
Assumptions
Supplied scope, dates, layer and judgments; hashes alone authenticate nothing.
Limitations
Documentary C for selected baseline/D+1/D+7/D+30; no causality, authenticated Google visit, indexing or global coverage.
TS36-A03 · Interpretation, decisions and closure bound to evidence.
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Selected release whose dated follow-up is assessed.
Evidence
Bound plan/reviews, deployment receipt, native API and supplied normalized logs; release-monitoring-v1 contract.
Method
Compare claims to known values, retain changes without causality and qualify supplied reviews/decisions.
Acceptance criteria
Faithful claims, supported reviews and complete cycle; false known claim or closure before a future stage fails; other gaps inconclusive.
When the result remains inconclusive
Future stage, missing evidence, errors, unknown values, incomplete logs or invalid bindings; preserve independent contradictions.
Non-applicability
No atomic exemption; absence or delay never establishes NA.
Assumptions
Supplied scope, dates, layer and judgments; hashes alone authenticate nothing.
Limitations
Documentary C for selected baseline/D+1/D+7/D+30; no causality, authenticated Google visit, indexing or global coverage.
Rule version 0.2.0-rc.1 · Public protocol reference · Versioned source
Put it into practice
Deployments, logs and Search Console observations.