What International SEO Actually Requires
International SEO is the practice of optimizing your website so that search engines correctly identify and serve the right language or regional version of your content to the right users. At its technical core, this means hreflang implementation—a frequently misunderstood HTML attribute that causes more SEO damage when done wrong than almost any other technical element.
This guide covers hreflang from first principles through advanced implementation, including common pitfalls that even experienced technical SEOs get wrong.
Understanding Hreflang: What It Does and What It Doesn’t
Hreflang is an HTML link attribute that signals to Google (and partially to Yandex) that your site has multiple language or regional variants of the same content. It does not determine your site’s language—that’s done by content and HTML lang attributes. Hreflang specifically tells Google: “This page and these other pages are equivalent for different audiences—serve each to the appropriate one.”
What hreflang prevents:
- The English-UK version of a page cannibalizing rankings for the English-US version
- Google treating translated pages as duplicate content
- Users in France landing on your German-language page because Google couldn’t determine the correct variant
What hreflang does not do:
- Guarantee that the correct version ranks—it’s a signal, not a directive
- Replace geo-targeting settings in Google Search Console
- Work with Bing (which uses its own geo-targeting signals)
Hreflang Syntax: Getting It Right
The standard HTML implementation goes in the <head> section of every page that has international variants:
<link rel="alternate" hreflang="en-us" href="https://example.com/en-us/page/" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page/" />Key syntax rules:
- Language codes: Use ISO 639-1 two-letter codes (en, fr, de, es, zh, ar, etc.)
- Region codes: Use ISO 3166-1 Alpha-2 codes (US, GB, FR, DE, AU, etc.)
- Case sensitivity: By convention, language codes are lowercase and region codes are uppercase (en-US), though Google accepts either
- x-default: Always include this tag pointing to your default/fallback page for users whose language isn’t matched
- Self-referential: Every page must include a hreflang tag pointing to itself
The Reciprocal Tag Requirement
The single most common hreflang mistake is failing to implement reciprocal tags. Every page referenced in a hreflang annotation must also reference back all other pages in the set. If your US English page lists your French page via hreflang, your French page must list your US English page back.
This means:
- If you have 5 language variants, each page needs 5 hreflang tags (including the self-referential one)
- If you have 10,000 pages in 5 languages, each page needs 5 tags—totaling 500,000 hreflang annotations across the site
- Missing even one reciprocal tag can cause Google to ignore the entire hreflang cluster for that page set
Validate reciprocal implementation using Screaming Frog’s hreflang audit or a dedicated tool like Aleyda Solis’s hreflang testing tool.
Three Implementation Methods
Method 1: HTML Head Tags
Best for: Small to medium sites with server-side rendering where page-level code changes are straightforward.
Advantages: Easy to validate, immediately visible to crawlers, supported by all hreflang-compatible search engines.
Disadvantages: Requires code changes per page, can become unwieldy at scale with many language variants.
Method 2: XML Sitemap
Best for: Large sites with many pages and language variants where page-level implementation would require thousands of individual changes.
Implementation:
<url>
<loc>https://example.com/en-us/page/</loc>
<xhtml:link rel="alternate" hreflang="en-us" href="https://example.com/en-us/page/"/>
<xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/page/"/>
</url>The sitemap must declare the xhtml namespace: xmlns:xhtml="http://www.w3.org/1999/xhtml"
Method 3: HTTP Response Headers
Best for: Non-HTML files (PDFs, etc.) that need hreflang signals. Rarely used for standard web pages.
Link: <https://example.com/fr/document.pdf>; rel="alternate"; hreflang="fr"URL Structure Strategy for International Sites
Before implementing hreflang, you need to decide on your URL structure. The three primary options:
Subdomain Structure
fr.example.com, de.example.com
Pros: Clear separation, easy to geo-target in GSC. Cons: Dilutes domain authority across subdomains, higher crawl budget requirements.
Subdirectory Structure (Recommended)
example.com/fr/, example.com/de/
Pros: Consolidates domain authority, simpler to manage. Cons: Requires more careful architecture to avoid internal canonicalization conflicts.
ccTLD Structure
example.fr, example.de
Pros: Strongest geo-targeting signal, builds local trust. Cons: Expensive to acquire/maintain, authority starts from zero on each ccTLD.
For most businesses, the subdirectory approach offers the best balance of SEO performance and operational simplicity.
Language-Only vs. Language-Region Targeting
Hreflang supports both language-only tags (hreflang=”fr”) and language-plus-region tags (hreflang=”fr-fr”, hreflang=”fr-be”). Understanding when to use each is critical:
- Use language-only (fr) when you have a single French version that serves all French-speaking regions
- Use language-region (fr-FR, fr-BE, fr-CA) when you have distinct versions for different regional markets with adapted content, currency, or legal information
- Don’t mix—if you use fr-FR for France, also use fr-BE for Belgium rather than a generic fr, or you’ll create conflicting signals
Canonical Tags and Hreflang Conflicts
Hreflang and canonical tags must be consistent. A page can be canonical and also reference alternate hreflang variants—that’s normal and correct. But hreflang tags should never point to non-canonical URLs. If your French page has a canonical pointing to the US English page (incorrectly), the hreflang referencing the French page will be invalidated.
The correct setup:
- Each page has a self-referencing canonical
- Hreflang tags on each page reference only canonical URLs of all variants
- No hreflang tag points to a redirected, paginated, or non-canonical URL
Hreflang and JavaScript Rendering
If your site uses client-side rendering (React, Vue, Angular), hreflang tags rendered by JavaScript may not be processed correctly by Google. Google’s rendering of JavaScript is delayed—hreflang signals delivered only through JavaScript may be missed during the initial crawl.
Solution: Implement hreflang via XML sitemap for JavaScript-rendered sites. The sitemap is processed separately from page rendering and doesn’t require JavaScript execution.
Validating Your Hreflang Implementation
After implementation, validate using:
- Screaming Frog: Full site crawl with hreflang validation and reciprocal check export
- Google Search Console: International Targeting report shows hreflang errors at scale
- Aleyda Solis’s Hreflang Testing Tool: Free tool for validating individual page sets
- Sitebulb: Visual hreflang cluster mapping for complex multi-language sites
- Manual spot check: Use
curl -I https://yourpage.comto verify HTTP header implementation if using that method
Common Hreflang Errors and Fixes
- Missing x-default: Add a fallback URL that applies to all users not matched by other tags
- Invalid language codes: Verify every code against the ISO 639-1 list—’uk’ is Ukrainian, not English-UK
- Pointing to redirected URLs: Update all hreflang references to the final destination URL
- Inconsistent coverage: Implement hreflang on ALL pages, not just the homepage—Google ignores partial implementations
- Mismatched content: Don’t hreflang to pages that aren’t genuine translations—Google may discount the entire cluster
International SEO requires precise technical execution. Contact Over The Top SEO for a comprehensive international SEO audit and hreflang implementation review.
Key Takeaways
- Hreflang tells Google which language/region variant to serve to which users—it’s a signal, not a directive, and must be implemented correctly to work
- Reciprocal tags are mandatory: every page in a hreflang set must reference all other pages in the set
- Choose subdirectory URL structure for most implementations—it consolidates authority while enabling clear language separation
- Hreflang tags must point only to canonical URLs, never to redirected or non-canonical pages
- JavaScript-rendered sites should implement hreflang via XML sitemap to avoid rendering delays
-
By Guy Sheetrit
- May 9, 2026
By Guy Sheetrit
