The 9 Hreflang Mistakes Killing International Ecommerce SEO
Hreflang is unforgiving — one bad tag and Google ignores your entire international setup. Here are the 9 mistakes we see on almost every multi-region store, and how to fix them.
Hreflang tags are how you tell Google which version of a page to show in which country. In theory, it's simple: a tag per region, pointing to the localized URL. In practice, it's a minefield — and Google's behavior when you get it wrong is to silently ignore all of it, which means most stores don't realize their international SEO setup is broken until they wonder why their French site never ranks in France.
Mistake 1: Missing Return Tags
Every hreflang link must be reciprocated. If page A says "the French version is at /fr/page", then /fr/page must also include an hreflang tag pointing back to page A. If the relationship isn't mutual, Google treats it as invalid and ignores your hreflang setup entirely for those URLs.
Fix: Export all hreflang tags from your site and build a matrix. Every A→B link needs a corresponding B→A link.
Mistake 2: Wrong Language Codes
Hreflang uses ISO 639-1 language codes and optional ISO 3166-1 Alpha 2 region codes. Common mistakes:
en-uk— wrong. UK is not an ISO country code. Useen-gb.en-eu— wrong. EU isn't a valid country code. Usex-defaultfor Europe-wide content.spa— wrong. Usees, not the 3-letter code.zhalone — ambiguous. Usezh-cnfor Mainland China (Simplified) orzh-twfor Taiwan (Traditional).
Mistake 3: Hreflang on Pages with Different Content
Hreflang is for same content, different language or region. It's not a general "these pages are related" signal. If your /en page sells shoes and your /fr page sells dresses, they shouldn't link to each other via hreflang — they're different pages, not translations.
Mistake 4: Missing x-default
The x-default hreflang tag tells Google which version to show when no specific match is found (for example, a user in a country you don't serve specifically). Most stores omit this. Always include:
<link rel="alternate" hreflang="x-default" href="https://yourstore.com/en/product" />Typically this points to your default (usually English) version.
Mistake 5: Hreflang Points to Redirecting URLs
If an hreflang tag points to a URL that 301s somewhere else, Google ignores it. Audit every hreflang target for direct 200 responses — no redirect chains, no 404s.
Mistake 6: Canonical vs Hreflang Conflict
If /fr/page has rel="canonical" pointing to /en/page, you're telling Google "these are duplicates, use the English one." Then also telling Google via hreflang "show the French version to French users." Google resolves this conflict by ignoring hreflang.
Fix: Each language version should have a self-referential canonical. The canonical URL for /fr/page is /fr/page itself.
Mistake 7: Blocking Translated Pages in Robots.txt
Any hreflang target that's blocked in robots.txt is treated as invalid. If your /fr/ directory is blocked for crawling while you also have hreflang tags pointing there, Google can't validate the relationship.
Mistake 8: Hreflang Only on Homepage
Hreflang needs to be implemented on every page with localized versions, not just the homepage. Most ecommerce stores we audit have hreflang on the homepage but not on product pages, which is where most search traffic actually lands.
Product pages, category pages, and blog posts all need their own hreflang tags pointing to their own localized equivalents.
Mistake 9: Using Language Detection Redirects
This isn't strictly an hreflang mistake, but it undermines your international SEO. Auto-redirecting users based on IP-detected language (/ → /fr/ for French visitors) causes problems:
- Googlebot crawls from US IPs and only sees the English version
- VPN users get incorrect language versions
- Users who want a different language can't easily access it
Fix: Let users choose their language, remember the choice (cookie or account setting), and respect hreflang for search engine results. Never force-redirect based on IP without a clear opt-out.
Implementation: HTML vs Sitemap vs HTTP Headers
You can implement hreflang three ways:
- HTML
<link>tags in the<head>— simplest for most stores - XML sitemap entries — cleanest for large sites with many language versions
- HTTP headers — useful for PDFs and non-HTML resources
Pick one and stick with it. Mixing implementations causes conflicts and inconsistencies.
Validation Tools
Free tools that catch hreflang errors:
- Google Search Console — International Targeting report shows hreflang errors
- Merkle Hreflang Testing Tool — validates any URL's hreflang
- Ahrefs Site Audit — flags hreflang conflicts at scale
- Screaming Frog — crawl-level hreflang validation
The 5-Minute Hreflang Audit
- Pick your top 10 traffic pages across all regions
- View source and extract all hreflang tags
- Verify return links exist on each target
- Verify language codes are valid ISO codes
- Verify canonicals are self-referential (not cross-language)
- Verify an x-default exists
- Verify no target URL is blocked or redirecting
If any of these fail on your top 10 pages, Google is almost certainly ignoring your hreflang setup. Fix the top 10 first — then scale to category and blog pages.
Beyond Hreflang
International SEO also depends on technical fundamentals working across regions: SSL certificates valid in every market, page speed acceptable on local connections, structured data localized correctly. A StoreVitals scan catches the technical issues that compound with hreflang mistakes on multi-region stores.