TS03Access and indexing

Do missing pages respond as intended?

Put the responses of an existing page, a removed page and a nonexistent address side by side. This helps document an unexpected HTTP status before a correction.

Read responses

In the app: HTTP reading · no verdict
You provide: 2 or 3 URLs on the same site
Allow for: Reading and confirmation

Read responses

Understand

The page is missing. The response matters.

Put the responses of an existing page, a removed page and a nonexistent address side by side. This helps document an unexpected HTTP status before a correction.

According to Google

A missing page should signal its state. Error content returned with a success status can be classified as a soft 404 by Google.

How HTTP status codes affect Google’s crawlers Source accessed on 2026-10-26

Check

Present or missing. Which response?

In TSEP Control

After your confirmation: the initial HTTP response, its date, received bytes and a content excerpt when readable. You can copy the summary, download evidence and run a new observation while retaining history.

Your contribution

Two or three addresses on the same site, with their actual situation. The removed page is optional if you have no example. A removal with a replacement belongs in the TS02 workflow.

With your own tools

Open your sample addresses and record the HTTP status and displayed message. For a page without a replacement, check that a real error is not hidden behind a 200 response.

What this result covers

Real URL observations are available. A real-world TSEP verdict is not yet available: the current TS03-A01 rule only qualifies fictional .invalid matrices. This workflow does not classify Google soft 404s or check the entire site.

Act

A missing page. An explicit status.

Match the server response to the actual situation: existing, removed or nonexistent page.

Recheck

Same URLs. Corrected responses?

Repeat the workflow with the same scope after correction. Date the new observation and retain earlier evidence.

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: Match the server response to the actual situation: existing, removed or nonexistent page.
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 rules1 rule

Control method and criteria

Method
Before captures, bind the intent plan for the three route states and their content criteria into configuration. Compare a supplied HTTP GET matrix without DNS resolution or network collection.

Acceptance criteria
Pass qualifies only the complete supplied matrix: 200 and expected markers for an existing route; 404/410 and declared body criteria for removed/nonexistent routes. A 2xx for the latter, another complete status, or a marker contradiction is fail. Soft-404 classification is not measured.

Non-applicability
Scope contains no HTTP routing, with a justification.

Detailed rules

TS03-A01 · Synthetic HTTP responses compared with a prior plan

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

Scope
A route plan contains at least one existing, removed and nonexistent state in the synthetic scope.

Evidence
The plan and its fingerprint, content expectations, then for each route the GET request, raw HTTP response, status, time and complete body. Preserve contradictory observations and gaps separately.

Method
Verify the prior plan and its fingerprint; compare each attributable, complete GET/response for a .invalid route with the permitted statuses and literal UTF-8 markers fixed in the content expectations.

Acceptance criteria
Pass requires exactly one complete response per route and every required state: 200 for existing, 404/410 for removed or nonexistent, required markers present and forbidden markers absent. A complete contradiction remains fail despite a duplicate, another incomplete capture or a gap. 206/304, missing, ambiguous or unattributable data remain inconclusive.

When the result remains inconclusive
Missing/future/mismatched plan, missing route state, duplicate, incomplete HTTP, unattributable URL/client, 206/304, non-UTF-8 content, contradictory plan markers or incomplete matrix; an attributable contradiction remains fail.

Non-applicability
No atomic exemption. Whole-control NA requires a positive, complete, reasoned and dated inventory establishing that no HTTP routing is in scope.

Assumptions
The plan, classifications and criteria are supplied and unauthenticated. Any attached review is a synthetic exercise, not independent approval.

Limitations
A .invalid capture tests no server. Markers are searched literally in the decoded body, without DOM, rendering, semantic judgment or engine classification. C covers only the declared matrix, not a whole site, availability over time, indexing or ranking.

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

Put it into practice

← Back to controls