Technical eligibility · Branch T.B, Canonical, discovery and URL management
T-10 Language and region versions must be managed consistently
On international or multilingual URLs, the language of the content, the canonical, hreflang and the navigation must all support the same region and language model.
- Scope
- All public content
- Priority
- High priority.
- Quality bucket
- Technical eligibility
- Legacy coverage
- SEO-40
Why it matters
If the page language, canonical, hreflang and navigation disagree, users can be sent to the wrong language or region version. Search engines may also treat versions as duplicates or pick the wrong one to show. Low-quality automatic translation adds a content quality problem, which Google's spam policies take seriously.
How to implement
- Set a self-referencing canonical on each language URL.
- Add reciprocal hreflang annotations between the matching versions where appropriate.
- Check that each page's actual language matches its declared language and region.
- Replace or withhold low-quality automatic translations before publishing.
- Make the language switcher use crawlable links.
Checklist
- Give every language URL a self-referencing canonical.
- Add reciprocal hreflang where appropriate.
- Do not publish low-quality automatic translations.
- Make the language switcher crawlable.
How to audit
- Validate hreflang, detect the page language and cross-check it against the canonical.
How UltimateSEO checks this automatically
Automated. Checked automatically: hreflang reciprocity and lang attributes across crawled language versions; marked not applicable when the site has a single language and no hreflang.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.