Hreflang Implementation Guide with Auditite
Step-by-step guide to implementing hreflang tags correctly for multi-language and multi-regional websites. Avoid common mistakes.
Overview
Hreflang tags tell search engines which language and regional version of a page to show to users in different locations. Incorrect hreflang implementation is one of the most common causes of international SEO problems — from serving the wrong language to cannibalizing your own pages across regions.
Step 1: Plan Your Hreflang Strategy
- List every language and region combination your site supports.
- Decide your URL structure: subdirectories (
/en/,/de/), subdomains (en.example.com), or separate domains (example.de). - Map every page to its equivalents across all language/region versions.
- Identify pages that exist in some languages but not others.
Language and Region Codes
Use ISO 639-1 for language codes and ISO 3166-1 Alpha-2 for region codes:
| Target | Code |
|---|---|
| English (any region) | en |
| English (US) | en-US |
| English (UK) | en-GB |
| German (Germany) | de-DE |
| German (Austria) | de-AT |
| Spanish (Spain) | es-ES |
| Spanish (Mexico) | es-MX |
| French (France) | fr-FR |
Step 2: Choose an Implementation Method
HTML Link Tags (Recommended for Most Sites)
Place hreflang link elements in the <head> of each page. Every page must reference all its language/region variants, including itself.
XML Sitemap (Recommended for Large Sites)
Add hreflang annotations to your XML sitemap using xhtml:link elements. This avoids bloating your HTML and is easier to manage at scale.
HTTP Headers (For Non-HTML Files)
Use HTTP Link headers for PDFs and other non-HTML documents that have multiple language versions.
Step 3: Implementation Rules
- Every hreflang set must be reciprocal. If page A references page B, page B must reference page A. Missing return links cause hreflang to be ignored.
- Every page must include a self-referencing hreflang tag. The English version must reference itself as
hreflang="en". - Include an x-default tag. The x-default tells search engines which page to show when no other hreflang matches the user’s language/region.
- Use fully qualified URLs. Include the protocol and domain in every hreflang URL.
- Canonical and hreflang must be consistent. The canonical URL of each page must match the URL used in hreflang annotations. If a page’s canonical points elsewhere, its hreflang is ignored.
Step 4: Common Scenarios
Same Content, Different Languages
Each translated page references all other translations. The x-default points to the English version or a language selector page.
Same Language, Different Regions
Use region-specific codes (en-US, en-GB) to differentiate content tailored for different markets even when the language is the same.
Pages Without Translations
If a page only exists in one language, it does not need hreflang tags. Only implement hreflang on pages that have equivalents.
Step 5: Validate Your Implementation
- Run Auditite’s hreflang audit across all site versions to check for missing return links and invalid codes.
- Verify that every hreflang URL returns a 200 status code (not a redirect or 404).
- Check that language codes are valid ISO 639-1 and region codes are valid ISO 3166-1.
- Confirm no page has conflicting hreflang and canonical signals.
- Test from different geographic locations using a VPN to verify Google serves the correct version.
Step 6: Monitor and Maintain
- Check Google Search Console’s International Targeting report for hreflang errors.
- Review the “Alternate page with proper canonical tag” status in the URL Inspection tool.
- Audit hreflang whenever new pages are added or URL structures change.
- Monitor organic traffic by country/language to detect serving issues.
- Update hreflang annotations whenever you launch a new language or regional version.
Common Hreflang Mistakes
- Using incorrect language or region codes (e.g.,
ukinstead ofen-GBfor United Kingdom English) - Forgetting self-referencing hreflang tags
- Non-reciprocal annotations (page A references B, but B does not reference A)
- Pointing hreflang URLs to redirects instead of final destination URLs
- Using relative URLs instead of absolute URLs
Related playbooks
International SEO and Hreflang Playbook
Master hreflang implementation and international SEO strategy to rank across multiple languages and regional markets.
PlaybookAI Agent SEO Workflows Playbook with Auditite
Set up AI-powered automated workflows for continuous SEO monitoring, issue detection, and auto-remediation at scale.
PlaybookAI-Assisted SEO Content Optimization Playbook
Leverage AI tools effectively for SEO content creation, optimization, and scaling while maintaining quality standards.
Stop copy-pasting. Start automating.
Auditite turns playbooks into live audit workflows. Get started to see how.