Few technical SEO tasks generate more confusion — or more frustrated support tickets — than hreflang implementation. I’ve audited international sites for companies ranging from 20-person startups to Fortune 500 enterprises, and hreflang mistakes are nearly universal. Pages competing for the same keywords in different languages, wrong regions being served in search results, and ranking signals being split across duplicate pages instead of consolidating where they should.
The frustrating part: hreflang is actually not that complex. The implementation syntax is straightforward. The common mistakes are well-documented. The problem is that most teams implement hreflang once, never audit it, and then spend months wondering why their international SEO isn’t performing.
This guide gives you the complete, correct implementation — syntax, structure, common mistakes, and the validation workflow to ensure it’s actually working.
Hreflang Fundamentals: What It Does and Doesn’t Do
Before implementing, you need a clear mental model of what hreflang actually accomplishes.
What Hreflang Does
Hreflang is a signal — not a directive — that tells search engines:
- Language-variant relationships: “This page exists in these languages/regions”
- Target audience: “This version is intended for speakers of this language in this region”
- Signal consolidation: “Don’t split ranking signals across these variants — they’re serving different audiences”
When implemented correctly, hreflang means:
- A German user searching from Germany sees the German-language page in Google’s German results
- A US user searching in English sees the US English version
- Ranking signals for equivalent content don’t compete against each other
What Hreflang Doesn’t Do
Hreflang does not:
- Redirect users: Users still land on whatever version Google shows them. If you want automatic redirects, implement geolocation at the server level.
- Translate content: You must provide actual translated content. Hreflang just tells Google which version serves which audience.
- Force Google to serve a specific version: It’s a strong hint, not a guarantee. Google may still serve a different variant based on user behavior signals.
- Work without reciprocal tags: If page A links to page B with hreflang, page B must link back to page A. Unidirectional hreflang tags are ignored.
The Basic Syntax
A hreflang tag is an HTML element in your page’s <head> section:
<link rel="alternate" hreflang="en-US" href="https://www.example.com/us/page/" />
Break down the components:
- rel=”alternate”: Indicates this is an alternative version
- hreflang=”en-US”: The language and optional region code of this specific page’s audience (ISO 639-1 language code + optional ISO 3166-1 Alpha-2 country code)
- href: The full URL of this alternate version
Every page must include a self-referencing hreflang tag plus hreflang tags for all other language/region variants.
Language and Region Codes: The Complete Reference
The hreflang attribute accepts language codes in ISO 639-1 format and optionally adds region codes in ISO 3166-1 Alpha-2 format. Getting these wrong is the single most common hreflang implementation error.
Language Codes
Use the two-letter language code only (lowercase):
- English: en
- Spanish: es
- German: de
- French: fr
- Chinese: zh
- Japanese: ja
- Arabic: ar
- Portuguese: pt
- Dutch: nl
- Italian: it
Note: zh is used for all Chinese variants. For regional Chinese variants, use zh-CN (Simplified Chinese), zh-TW (Traditional Chinese), or zh-HK (Hong Kong Cantonese). Using just zh without regional qualifier applies to all Chinese speakers globally.
Language + Region Codes
When you need to specify both language and region:
- en-US: English for United States
- en-GB: English for United Kingdom
- es-ES: Spanish for Spain
- es-MX: Spanish for Mexico
- pt-BR: Portuguese for Brazil
- de-DE: German for Germany
- de-AT: German for Austria
- zh-CN: Chinese (Simplified) for China
- zh-TW: Chinese (Traditional) for Taiwan
Important: Country codes are ISO 3166-1 Alpha-2, not ISO 3166-1 Alpha-3. Use “DE” not “DEU” for Germany. Use “GB” not “UK” for United Kingdom.
The x-default Value
x-default is a special hreflang value that specifies the page to serve when no other variant matches the user’s preferences. Use it for your generic/default page:
<link rel="alternate" hreflang="x-default" href="https://www.example.com/page/" />
Every hreflang implementation must include an x-default entry. This is the catch-all that tells Google “if the user’s language/region doesn’t match any specific variant, show this page.”
Common Code Mistakes to Avoid
- Using “UK” instead of “GB” for United Kingdom (UK is not a valid ISO code)
- Using “EN” instead of “en” (codes are case-sensitive and lowercase)
- Using language codes like “zh-CHS” instead of “zh-Hans” (use IETF language tags, not locale identifiers)
- Adding regional specificity without a language code (you can’t have hreflang=”US” — you need a language, so “en-US”)
URL Structure and Hreflang
Your URL structure determines how hreflang gets implemented. There are three main approaches, each with tradeoffs.
Approach 1: Country-Code Top-Level Domains (ccTLDs)
Separate domains for each country/region:
- example.com (US)
- example.de (Germany)
- example.fr (France)
- example.co.uk (United Kingdom)
Pros: Clear regional signal to users and search engines. Local domain authority in each market. Automatic URL geo-targeting in Google Search Console.
Cons: Requires building domain authority from scratch in each market. More complex DNS and SSL management. Higher infrastructure costs.
Hreflang implementation: Each ccTLD page has self-referencing hreflang plus hreflang links to all other regional variants.
Approach 2: Subdirectories (gTLD with Path)
Single domain with subdirectories for each region:
- example.com/us/
- example.com/de/
- example.com/fr/
- example.com/uk/
Pros: Consolidates domain authority. Simpler infrastructure. Easier to manage from one domain.
Cons: Weaker regional signal to users. Requires explicit hreflang implementation. Google Search Console geo-targeting is directory-based (less automatic).
Hreflang implementation: Same as ccTLDs — each page links to all other regional variants.
Approach 3: Subdomains
Single domain with subdomains:
- us.example.com/
- de.example.com/
- fr.example.com/
Pros: Clear separation of regional content.
Cons: Subdomains are treated as separate sites by some signals. Generally not recommended over ccTLDs or subdirectories.
Recommendation: For most companies, subdirectories are the best balance of SEO effectiveness and operational simplicity. ccTLDs make sense when a specific regional market is your primary revenue driver and you have the resources to build local authority.
Implementing Hreflang in HTML
The standard implementation is in the <head> of each page. Here’s a complete example for a site with three regional variants:
US page (example.com/us/page/):
<link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />UK page (example.com/uk/page/):
<link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />German page (example.com/de/page/):
<link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />Key rules:
- Every page includes a self-referencing hreflang tag pointing to itself
- Every page includes hreflang tags for ALL other regional variants
- Every page includes an x-default tag
- All hreflang tags are in the
<head>, not the body - All URLs are absolute (full URL, not relative paths)
Enforcement in HTTP Headers
For non-HTML content (PDFs, videos, downloadable files), implement hreflang in HTTP headers using the Link response header:
Link: <https://example.com/us/document.pdf>; rel="alternate"; hreflang="en-US", <https://example.com/de/document.pdf>; rel="alternate"; hreflang="de-DE"
This follows the same logic as HTML implementation but applies to non-HTML files that still need language targeting.
Implementing Hreflang in XML Sitemaps
For large international sites, implementing hreflang in XML sitemaps is more scalable than HTML implementation. It allows you to define all hreflang relationships in a single location and keeps your HTML cleaner.
Sitemap Structure
Each URL in your sitemap can include multiple <xhtml:link> elements specifying all language variants:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://example.com/us/page/</loc>
<xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<xhtml:link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />
<lastmod>2026-05-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/uk/page/</loc>
<xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<xhtml:link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />
<lastmod>2026-05-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>https://example.com/de/page/</loc>
<xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<xhtml:link rel="alternate" hreflang="de-DE" href="https://example.com/de/page/" />
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/us/page/" />
<lastmod>2026-05-27</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
</urlset>Note: You don’t need to include hreflang tags in both HTML and sitemaps — pick one method. Sitemap implementation is preferred for large sites (100+ pages) because it’s more maintainable and gives Google a comprehensive overview of your international structure in one place.
Common Hreflang Mistakes and How to Fix Them
After auditing hundreds of international sites, these are the mistakes I see most consistently:
Mistake 1: Missing Reciprocal Hreflang Tags
If page A has hreflang pointing to page B, but page B doesn’t have hreflang pointing back to page A, Google ignores both tags.
Fix: Audit your entire site for bidirectional hreflang completeness. Every language variant must be referenced by all other variants. Use Screaming Frog’s hreflang report to find all missing reciprocal tags.
Mistake 2: Missing x-default
Pages without an x-default entry don’t have a fallback for unmatched users. Google may choose an arbitrary variant to show.
Fix: Add x-default to every page’s hreflang implementation. Point it to the most appropriate default page — typically the US or main English version.
Mistake 3: Inconsistent URLs
If your hreflang says one URL but the canonical says a different URL, you have a conflict. Google may resolve it by ignoring both.
Fix: Ensure hreflang and canonical tags are consistent. If your canonical points to the US version, your hreflang should reflect that same canonical relationship.
Mistake 4: HTTPS/HTTP Mismatch
If some hreflang URLs use HTTP and others use HTTPS, Google sees them as different URLs and may not match them correctly.
Fix: Audit all hreflang URLs for protocol consistency. Every URL should use your current preferred protocol. If you’ve migrated to HTTPS, all hreflang URLs must use HTTPS.
Mistake 5: Trailing Slash Inconsistencies
example.com/page/ and example.com/page are technically different URLs. If hreflang mixes them, signals won’t consolidate properly.
Fix: Standardize your URL structure (pick with or without trailing slash) and enforce it consistently across all hreflang tags. Use server-side redirects to canonicalize the preferred format.
Mistake 6: Wrong Language Codes
Using “zh-Hans” instead of “zh-CN” for Simplified Chinese, or using non-standard region codes. These are silently ignored.
Fix: Double-check all language and region codes against ISO 639-1 and ISO 3166-1 Alpha-2 standards. The most common error: using “UK” instead of “GB”.
Geo-Targeting with Google Search Console
Beyond hreflang, Google Search Console provides explicit geo-targeting settings for your international pages. For ccTLDs, this is automatic. For subdirectories and subdomains, you need to set it explicitly.
Setting Geo-Targeting by Directory
In Google Search Console:
- Select your property (the root domain, not a subdirectory)
- Go to Settings → International Targeting
- Under the “Languages” tab, review the detected hreflang implementations
- For subdirectories, you can specify which subdirectory targets which country
Note: Google explicitly states that Search Console geo-targeting settings reinforce (not replace) hreflang tags. The hreflang implementation in your HTML or sitemap is the primary signal. Search Console settings are secondary.
Monitoring for Issues
The International Targeting report in Search Console flags:
- Pages with missing or incorrect hreflang
- Unrecognized language codes
- Inconsistencies between your implementation and Google’s interpretation
Check this report monthly for any new issues — hreflang problems that develop silently can quietly damage your international rankings.
Troubleshooting Hreflang Problems
When international SEO isn’t working as expected, follow this systematic troubleshooting workflow:
Step 1: Validate Syntax
Use the Simo Ahava hreflang Tag Generator and Validator or Screaming Frog to check for:
- Syntax errors in hreflang attributes
- Invalid language or region codes
- Malformed URLs
- Duplicate hreflang tags on the same page
Step 2: Check Reciprocal Links
Use Screaming Frog’s hreflang report to identify all pages that are referenced by other pages but don’t reference back. Any asymmetry is a problem.
Step 3: Verify Index Coverage
In Google Search Console, check the Coverage report for your regional subdirectories or ccTLDs. Look for:
- Pages that are indexed vs. excluded
- Any hreflang-related exclusions
- Crawl errors for regional variants
Step 4: Test Live URLs
Use Google Search Console’s URL Inspection tool on your regional pages. Look at the “Indexed” status and any hreflang-related information Google reports. If Google shows different hreflang interpretation than what you implemented, dig into why.
Step 5: Check for Canonical/Hreflang Conflicts
In Screaming Frog, export all pages with both canonical and hreflang tags. Verify that canonical and hreflang relationships are consistent. Any page where canonical points to a different URL than its hreflang self-reference is a conflict that needs fixing.
International SEO Beyond Hreflang
Hreflang is one piece of a complete international SEO strategy. These complementary practices ensure your international pages actually rank:
Localized Content Quality
Hreflang only works if your content is genuinely localized, not just translated. Machine-translated content typically ranks poorly in local markets because:
- It reads awkwardly and fails user engagement signals
- It may contain incorrect terminology in specialized industries
- Google’s quality algorithms detect low-quality translated content
Invest in native-speaker review of all translated content. For high-value markets (Germany, France, Japan, Brazil), native-fluent content writers are essential.
Local Link Building
Backlinks from local sites in each market reinforce your regional authority signals. Hreflang tells Google your pages are related; local backlinks tell Google your pages are trusted in each market.
Build localized link acquisition strategies for each target market: local directories, industry publications, regional partners, and local media outreach.
Local Hosting and CDN
Page speed is a confirmed ranking factor globally. Using a CDN with regional points of presence ensures fast load times in each market. For European markets, having European server infrastructure (or CDN presence) can improve both speed and trust signals.
Frequently Asked Questions
What is hreflang and why do I need it for international SEO?
Hreflang is an HTML attribute and HTTP header that tells search engines which language and regional variant of a page is intended for which audience. Without hreflang, search engines may show the wrong language version in search results, dilute ranking signals across duplicate pages, or show mixed-language content that confuses users and hurts conversions.
Can I use hreflang tags and canonical tags on the same page?
Yes, and you often should. The key rule is consistency: your hreflang tags and canonical tags must point to the same URLs. If your canonical says page A points to page B, your hreflang must reflect that relationship. Never let canonicals and hreflang conflict — Google will default to ignoring both when they contradict.
What is the x-default hreflang value and when should I use it?
x-default tells search engines which page to show when no other hreflang variant matches the user’s language or region. Use x-default for your generic landing page (e.g., /page/) that redirects or serves content based on browser language detection. Every hreflang implementation should include an x-default entry.
Should I use country-code top-level domains (ccTLDs) or subdirectories for international SEO?
Both work equally well from an SEO perspective when implemented correctly. ccTLDs (.de, .fr, .co.uk) signal regional intent clearly to users and search engines but require more domain authority to build. Subdirectories (/de/, /fr/) consolidate domain authority but may signal less regional specificity. For most companies, subdirectories with proper hreflang are the most practical choice.
How do I validate that my hreflang implementation is correct?
Use multiple tools to cross-validate: (1) Screaming Frog or Sitebulb for comprehensive crawl analysis, (2) Google’s Rich Results Test for structured data, (3) Google Search Console’s URL Inspection to see how Google interprets your hreflang, (4) the hreflang Tag Generator/Validator by Simo Ahava for syntax checking. Run all validations after any hreflang change.
Canonical Tags: The Definitive Guide to Solving Duplicate Content
Canonical Tags: The Definitive Guide to Solving Duplicate Content Duplicate content is one of the…
Read More →
Schema Markup Guide: Every Type That Matters for SEO in 2026
Schema markup — also called structured data or JSON-LD — is the layer of information…
Read More →-
By Guy Sheetrit
- May 27, 2026
By Guy Sheetrit
