TS40International
InternationalDo your hreflang methods tell the same story?
The hreflang methods in use are complete and consistent.
Prepare evidence
- In the app
- Evidence import
- You provide
- HTML, HTTP or sitemap annotations
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
Several methods. The same languages.
The hreflang methods in use are complete and consistent.
According to Google
HTML, HTTP headers and sitemaps are three ways to indicate variants. Google does not require using all of them; if you use several, keep them consistent.
Check
HTML, HTTP, sitemap. One consistent group?
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 toolsExtract annotations from channels actually in use: HTML, HTTP headers and sitemap. Compare groups, languages, destinations and return links across those datasets.
Evidence to retain
Equivalent reciprocal clusters; when sitemaps are used, valid xhtml namespace and entries per URL.
What this result covers
Combining HTML, headers and sitemaps offers no search benefit and increases divergence risk.
Act
Align the methods. To the same variants.
Align groups and destinations across the methods used, then check completeness.
Recheck
An annotation changes. Reread every method.
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
- Align groups and destinations across the methods used, then check completeness.
- 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
Identify all published methods, verify clusters and compare annotations when methods coexist.
Acceptance criteria
Each used method covers the cluster; if several are published, their annotations are consistent; no single-method requirement is imposed.
Non-applicability
No hreflang annotations in scope.
Detailed rules
TS40-A01 · Independent completeness of published methods
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS40 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, intent. Conditional native evidence follows declared methods.
Method
Inventory methods before capture; read every method/page independently and check the complete expected group including self-reference. A secondary method does not complete a partial primary one.
Acceptance criteria
Each complete method contains the expected mappings. Demonstrated omission on a complete surface or a conflicting destination fails; one chosen method is allowed.
When the result remains inconclusive
Missing capture/method, truncated/index XML, published method omitted from plan, outside-group mapping 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.
TS40-A02 · Consistency across methods and cluster pages
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Explicitly selected TS40 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, intent. Conditional native evidence follows declared methods.
Method
Compare qualified mappings across methods/pages without merging their sets. Retain independent destination conflicts even when a third method is missing; compare set equality when both are complete.
Acceptance criteria
Complete methods and pages agree. One complete method is allowed. A native conflict or differing complete sets fails.
When the result remains inconclusive
Comparison without a qualified surface, partial capture, missing method or absent review: inconclusive unless an independent contradiction is established.
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
Selected HTML, HTTP or sitemap annotations.