TS21URLs and canonicals
URLs and canonicalsWhy is this page family outside the index?
Discovered but unindexed URLs are investigated by family.
Prepare evidence
- In the app
- Evidence import
- You provide
- Search Console sample and hypothesis
- Allow for
- Depends on evidence needed
In the app
Allow forUnderstand
A missing page family. Evidence to understand why.
Discovered but unindexed URLs are investigated by family.
According to Google
The indexing report helps identify exclusion reasons; its examples are not a complete inventory. Inspection lets you examine a specific URL.
Check
The overall report. The individual evidence.
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 toolsIsolate a page family in the Page indexing report and inspect several examples. Compare reasons with current responses, logs and recent changes; the report’s URL list is not exhaustive.
Evidence to retain
Hypothesis per family, URL sample and post-fix result.
What this result covers
A Search Console label describes a state, not always its cause.
Act
One hypothesis. One documented action.
Address one hypothesis per family and observe its effect on a dated sample.
Recheck
The same examples. New crawls.
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
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
- Address one hypothesis per family and observe its effect on a dated sample.
- 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 rules2 rules
Control method and criteria
Method
Segment the Pages report by template and compare it with sitemaps and logs.
Acceptance criteria
Each selected family has a documented diagnosis, a testable hypothesis and a decision; unproven causality is disclosed.
Non-applicability
A dated report contains no relevant family, or Google is explicitly excluded.
Detailed rules
TS21-A01 · Attribution of nonindexed families
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS21 families or clusters; indexing-locale-v1, docs/indexing-locale-evidence.md.
Evidence
Prior plan, exact originals, fingerprints, dates/context, observations and reasoned review bound to the whole dossier. Minimum kinds: search-console, logs, sitemap, intent. Conditional native evidence follows declared methods.
Method
Read supplied Google URL Inspection requests/responses for each selected URL, compare property, URL and family label; reconcile native urlset and TSV log export in their declared window. Require segmentation/attribution review.
Acceptance criteria
Native pieces are available and attributed to the selected family; sitemap membership agrees with the plan. Request, family-label or sitemap disagreement fails. Logs describe only their supplied window and client.
When the result remains inconclusive
Missing evidence, absent/error API result, unsupported label, uninterpretable logs or absent review: inconclusive.
Non-applicability
No atomic exemption. Empty population, unassessed Google or an unobserved cluster remains NT in this profile.
Assumptions
Supplied unauthenticated scope, provenance, segmentation and reviews. Two static HTML hypotheses are not two navigations. Frozen codes do not predict engine processing.
Limitations
Offline reading of supplied evidence; no authenticated Google origin, human identity or crawler visit; no current index state, causality, translation quality, targeting or global conformity established.
TS21-A02 · Testable hypothesis and decision without invented causality
Protocol assessment mode : manual. App availability is shown on the control card.
Scope
Explicitly selected TS21 families or clusters; indexing-locale-v1, docs/indexing-locale-evidence.md.
Evidence
Prior plan, exact originals, fingerprints, dates/context, observations and reasoned review bound to the whole dossier. Minimum kinds: content, intent. Conditional native evidence follows declared methods.
Method
Read family-diagnosis-v1: diagnosis, hypothesis, prediction, falsification, measurement, decision, owner and due date for the same URL list. Check planned-versus-observed follow-up and bound review.
Acceptance criteria
Diagnostic axes are supplied and reviewed; causality=unproven and follow_up=planned-not-observed. Declaring causality from a label or correlation fails this profile.
When the result remains inconclusive
Hypothesis without falsification, misattributed family, claimed observed follow-up outside a separate method or missing judgment: inconclusive.
Non-applicability
No atomic exemption. Empty population, unassessed Google or an unobserved cluster remains NT in this profile.
Assumptions
Supplied unauthenticated scope, provenance, segmentation and reviews. Two static HTML hypotheses are not two navigations. Frozen codes do not predict engine processing.
Limitations
Offline reading of supplied evidence; no authenticated Google origin, human identity or crawler visit; no current index state, causality, translation quality, targeting or global conformity established.
Rule version 0.3.0-draft.3 · Public protocol reference · Versioned source
Put it into practice
A Search Console sample and a hypothesis.