TS22International
InternationalDo language variants point to the right pages?
Each hreflang variant points to an indexable canonical URL.
Prepare evidence
- In the app
- Evidence import
- You provide
- Hreflang groups and destinations
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
The right language. The right version.
Each hreflang variant points to an indexable canonical URL.
According to Google
Hreflang identifies language or regional versions of a page. Codes must be supported and destinations must match the declared variants.
Check
The declared codes. The target pages.
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 toolsRead hreflang annotations from the chosen channel, check language/region codes and open each destination. Confirm that the content consists of corresponding variants.
Evidence to retain
Valid language/region, 200 response and consistent canonical.
What this result covers
hreflang helps targeting; it does not replace genuinely localized content.
Act
The right region. The right destination.
Fix language or region codes and replace non-indexable destinations.
Recheck
Published variants. Rechecked links.
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
- Fix language or region codes and replace non-indexable destinations.
- 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
Parse HTML, HTTP or sitemap annotations and resolve every URL.
Acceptance criteria
Each cluster target is accessible, intended for indexing and consistent with its canonical; language/region codes are checked.
Non-applicability
No hreflang cluster in scope, with an inventory provided.
Detailed rules
TS22-A01 · Native annotations and registered codes
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS22 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: hreflang, http, html, intent. Conditional native evidence follows declared methods.
Method
Read declared HTML, Link headers and XHTML urlsets separately; retain agreement of both static HTML hypotheses. Check each observed code against the frozen IANA registry subset and attribution to its planned destination.
Acceptance criteria
Observed codes belong to the documented language/script/region profile and destinations agree. An explicitly invalid code or conflicting destination fails; x-default qualifies only the reserved token.
When the result remains inconclusive
Deprecated code, exceptional region outside the subset, missing method/page, ambiguous HTML, relative annotation 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.
TS22-A02 · Hreflang destinations and indexing-permission signals
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS22 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: hreflang, http, html, robots, intent. Conditional native evidence follows declared methods.
Method
For every selected destination compare indexing intent, direct HTTP200, HTTP/HTML directives, explicit self-canonical and same-origin robots.txt under the prior Google profile. Require source-scope review.
Acceptance criteria
Qualified signals permit and agree with the planned destination. A conflicting response, noindex, divergent canonical or evidenced robots denial fails despite other unknowns.
When the result remains inconclusive
Missing/unqualified robots, absent canonical, partial trace, required rendering or absent review: inconclusive. Indexing permission is not indexing.
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
Hreflang groups and their destinations.