Implementation requirements
- Valid language or language-region values
- reciprocal references
- self-reference
- canonical alignment
- indexable alternate pages
- absolute URLs
- x-default when appropriate
Common failures
- Missing return links
- noncanonical targets
- redirects or errors
- language-only pages that are not equivalents
- mixed URL formats
- stale annotations after migration
Hreflang implementation sequence
- 01
Define the locale matrix
List each language or language-region version and the canonical URL that represents it.
- 02
Use valid language and region codes
Apply supported ISO language codes and optional region codes only when the page genuinely targets that locale.
- 03
Create reciprocal references
Each alternate should reference itself and the other equivalent versions.
- 04
Keep canonicals local
Each localized page normally canonicalizes to itself rather than collapsing into another language version.
- 05
Validate every cluster
Check missing return links, redirected URLs, errors, mixed protocols, and incomplete locale sets.
Content and operations cautions
- Hreflang does not translate the page.
- Country targeting does not make weak localization useful.
- Automatic redirects based only on IP or language can prevent access to alternatives.
- The locale inventory needs an owner when URLs, templates, or markets change.
Apply Hreflang and international targeting to a real website decision
Use hreflang and international targeting as a decision framework rather than a detached definition. Start with the user or business task, collect discovery paths, response codes, rendering, directives, canonicals, internal links, sitemaps, duplication, and selected URLs, document uncertainty, and decide what action is justified by the evidence.
Evidence
Page-template and url-pattern evidence rather than isolated examples.
Interpretation
Explain how the observed condition affects the intended outcome: make the intended pages discoverable, interpretable, internally connected, and maintainable.
Verification
Recrawl the affected patterns, inspect rendered output and directives, and monitor indexation and search behaviour over time.
Questions to answer about Hreflang and international targeting
- What user, search, commercial, compliance, or operational task does hreflang and international targeting affect?
- Which templates, URLs, entities, environments, or journeys are actually in scope?
- What evidence would distinguish a confirmed problem from the risk of changing directives or canonicals without understanding the intended URL model?
- Who owns the decision, implementation, approval, and follow-up?
- What measurement or retest will prove the change improved the intended outcome?
Turn hreflang and international targeting into an accountable record.
A documented decision or practice for hreflang and international targeting that can be applied to a real website.