TS08Access and indexing

What does Google report for this URL?

Understand Google-reported status and decide what to do.

Open Search Console

In the app: Search Console connection
You provide: Search Console, URL and goal
Allow for: Reading and confirmation

Open Search Console

Understand

Your page. As Google sees it.

Understand Google-reported status and decide what to do.

According to Google

The inspection API provides the state of the version known to the index. It does not test live URL indexability; the TSEP documentation result remains separate from Google’s state.

URL Inspection API: index.inspect Source accessed on 2026-10-26

Check

Google’s response. With its date.

In TSEP Control

The Google response, your decision and a TS08 documentation result. The API is not a test of the current page.

Your contribution

An authorized Search Console account, one URL and a prior goal.

With your own tools

Inspect the URL in the appropriate Search Console property. Record the last crawl date, indexing status and canonicals; keep the “Test live URL” result separate.

See what Google knows about your URL using your Search Console data.

Connect Google Search Console · Read-only · New tab. The inspection creates a dossier separate from this analysis.

What this result covers

Inspection shows what Google reports for this URL; it is not a live test. The documentation result validates neither the whole page nor the whole site.

Act

An observed gap. A decision to make.

Assess the difference from your goal and record a decision based on Google’s response.

Recheck

A fresh observation. When was the last crawl?

After correction, inspect again while checking Google’s last crawl date. The API describes the indexed version, not a live test: a new observation does not mean Google has already revisited the page.

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: Assess the difference from your goal and record a decision based on Google’s response.
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

Detailed method and rules3 rules

Control method and criteria

Method
Declare selection, objectives, sources and prior knowledge before acquisition; retain native API JSON, limitations and supplied reviews under google-inspection-evidence-v1.

Acceptance criteria
All three rules pass for the entire selected set. C qualifies documentation of Google-reported status, never an indexing promise or current site state.

Non-applicability
Google is explicitly out of scope; lack of access alone is insufficient.

Detailed rules

TS08-A01 · Qualified prior scope and objectives.

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

Scope
Explicit selected URL set whose Google-reported state must be documented.

Evidence
Dated sourced plan, native request/response JSON and hashes, actual metadata, supplied evidence-bound reviews; inspection-evidence-v1 contract.

Method
Declare members, objectives/sources, selection reasons, prior knowledge and freshness policy; retain the bound prior plan review.

Acceptance criteria
Supported selection/objective review, plan and review before acquisition, no omitted member. Supplied contradiction or acquisition preceding the plan fails; absence alone is inconclusive.

When the result remains inconclusive
Missing, invalid or ambiguous evidence, review or binding; retain limitations, unknowns and API errors.

Non-applicability
No atomic exemption; lack of access is not NA.

Assumptions
Dates, authorship, provenance, access and attribution are supplied, never authenticated by hashes alone.

Limitations
Selected-set documentation only; non-live API and crawl time distinct from field timestamps. No current state, causality, TS12 or SEO outcome inferred.

TS08-A02 · Attributed and readable native inspections.

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

Scope
Explicit selected URL set whose Google-reported state must be documented.

Evidence
Dated sourced plan, native request/response JSON and hashes, actual metadata, supplied evidence-bound reviews; inspection-evidence-v1 contract.

Method
Read native bytes using diagnostic1, compare URL/property attribution, retain fields and check dates against prior policy.

Acceptance criteria
Every member has a usable response with known required fields and dates within policy. Explicitly allowed absent API fields stay visible; API errors and unknown values never become C.

When the result remains inconclusive
Missing, invalid or ambiguous evidence, review or binding; retain limitations, unknowns and API errors.

Non-applicability
No atomic exemption; lack of access is not NA.

Assumptions
Dates, authorship, provenance, access and attribution are supplied, never authenticated by hashes alone.

Limitations
Selected-set documentation only; non-live API and crawl time distinct from field timestamps. No current state, causality, TS12 or SEO outcome inferred.

TS08-A03 · Evidence-bound interpretation and decision.

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

Scope
Explicit selected URL set whose Google-reported state must be documented.

Evidence
Dated sourced plan, native request/response JSON and hashes, actual metadata, supplied evidence-bound reviews; inspection-evidence-v1 contract.

Method
Read supplied review: exact API verdict claim, interpretation, relation to prior objective, temporal scope, typed explanation and operational decision.

Acceptance criteria
All facets are qualified; a documented discrepancy may pass. Explicit verdict/scope contradiction or contradiction judgment fails and survives independent unknowns. Missing review or unsupported cause remains inconclusive.

When the result remains inconclusive
Missing, invalid or ambiguous evidence, review or binding; retain limitations, unknowns and API errors.

Non-applicability
No atomic exemption; lack of access is not NA.

Assumptions
Dates, authorship, provenance, access and attribution are supplied, never authenticated by hashes alone.

Limitations
Selected-set documentation only; non-live API and crawl time distinct from field timestamps. No current state, causality, TS12 or SEO outcome inferred.

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

Put it into practice

← Back to controls