A site with hreflang for 15 languages can still show English content to Spanish-speaking users — if the hreflang tags are correct but the content quality and signals for the Spanish version aren't strong enough for Google to trust them
The previous articles on this site covered hreflang basics, international SEO beyond hreflang, common implementation errors, geo-redirects, and the x-default value. This article addresses hreflang and content quality — why correctly implemented hreflang doesn't guarantee correct language targeting if the underlying content doesn't support it, and the signals Google uses alongside hreflang to determine which language version to serve.
Hreflang as a hint, not a command
As covered in the canonical tag context, Google treats many SEO directives as hints rather than absolute instructions. Hreflang is explicitly described by Google as a "strong hint" — it tells Google your preference for which language/locale version to serve to which users, but Google may override this if other signals conflict.
Why Google overrides hreflang: the goal is to serve the most relevant result to the user. If the Spanish version (es hreflang) has thin content, doesn't load reliably, or has very few quality signals compared to the English version, Google may determine that serving the English version — even to Spanish-speaking users — is a better user experience than serving a poorly-performing Spanish page.
The content quality requirement for hreflang to work correctly
A hreflang tag is a promise: "this URL at /es/ provides the Spanish-language equivalent of this content." Google verifies this promise against several signals:
Language signals in the content itself: the page at /es/ should contain Spanish-language text. If it has minimal text, or if the text is machine-translated but low quality, Google may determine it's not a genuine Spanish-language resource.
Backlinks and external signals: high-quality links from Spanish-language sites to the Spanish version signal to Google that the Spanish version is genuinely used by Spanish-speaking audiences. A Spanish version that receives all its links from English-speaking markets is less convincing.
User behavior signals: if Spanish-speaking users consistently click on the Spanish result and then immediately click back (a pogo-sticking signal), Google may infer the Spanish version isn't satisfying the user's need.
Crawl accessibility: the Spanish version must be crawlable and return 200 without errors consistently.
Machine translation and hreflang: the quality threshold problem
Many sites implement international versions through automated machine translation — the English content is translated programmatically, pages are created at /es/, /fr/, etc., and hreflang is configured. Google has become increasingly sophisticated at identifying low-quality machine-translated content.
Google's current position on machine translation: it's acceptable as a starting point, but content that reads like raw machine output (unnatural phrasing, grammatical errors, technical terms untranslated) may be seen as "thin content" — content that provides little additional value vs the original.
The practical threshold: if the translation is good enough that a native speaker can read it without difficulty, hreflang will generally work. If the translation is obviously automated and low-quality, hreflang may work inconsistently — Google might serve the English version or the translated version depending on query signals.
Post-edit machine translation: having human editors review and improve machine-translated content (MTPE — machine translation post-editing) significantly improves quality and hreflang effectiveness.
Partial hreflang implementation: what happens when you cover some but not all languages
A site might implement hreflang for English, French, and German but have a Chinese-speaking market segment that accesses the English version. Hreflang tells Google nothing about which language to serve users who aren't matched by any of the specified tags — the x-default tag (covered in the previous article) handles the "no match" case.
Without x-default: Google uses its own signals to determine which version to serve to users in languages without explicit coverage. For a Chinese user accessing an English/French/German site with no Chinese hreflang, Google may serve the English version (typically the default) or whichever version its signals suggest is most appropriate.
The consequence of partial implementation: it often works adequately because Google's own language detection is fairly good for major languages. The hreflang implementation just provides more explicit guidance where it's defined.
Country targeting without language differentiation: the en-US / en-GB example
A common hreflang use case: the same language, different regional content. US and UK versions of the same site both in English but with different pricing, spellings, product availability, or legal notices.
en-US vs en-GB targeting challenges:
- US and UK users both search in English
- Google can't determine from language alone which version is intended
- IP-based geolocation is the primary signal Google uses alongside hreflang for same-language country targeting
- A UK user using a VPN that routes through the US may receive the US version
This is one area where hreflang works better for language differentiation (serving Spanish to Spanish speakers) than for same-language country targeting — for the latter, IP-based server-side geo-detection plus hreflang in combination is more reliable than hreflang alone.
How to use the Hreflang Generator on sadiqbd.com
- Generate correct hreflang tags as the technical foundation — necessary but not sufficient for correct language targeting
- Verify content quality for each language version: is the translated content genuinely readable and useful in that language? Are there adequate backlinks from that language's web presence?
- Monitor Search Console's International Targeting report — this shows hreflang errors (missing reciprocal links, mismatched URLs) but also which country's traffic is landing on which language version; significant mismatches may indicate hreflang override
Frequently Asked Questions
If Google overrides my hreflang and shows the English version to Spanish speakers, will adding more Spanish hreflang pages fix it? Not necessarily — the issue is likely content quality or authority, not coverage. Adding more pages with Spanish hreflang won't improve the Spanish version's authority signals if the underlying Spanish content is thin or the pages have minimal Spanish-language backlinks. The fix is improving the Spanish content itself (better translation quality, more topical depth, increased Spanish-language external links) so Google's confidence in the Spanish version increases. Once Google trusts the Spanish version as a genuine, high-quality Spanish resource, hreflang will work as intended.
Is the Hreflang Generator free? Yes — completely free, no sign-up required.
Try the Hreflang Generator free at sadiqbd.com — generate correct hreflang tags for all your language and regional versions.
