Google Search Central: Internationalization & hreflang Best Practices

Google Search Central's episode on internationalization and hreflang digs into one of the most misunderstood areas of technical SEO. The Search Off the Record team discusses how hreflang annotations work, why they break so often, and what Google actually does with them when crawling and indexing multi-language or multi-region sites.

Watch the full video: Internationalization & hreflang

What the Episode Covers

The conversation starts with the basics: hreflang is an annotation that tells Google which language and regional variant of a page to show users in different locations. If you have an English page for the US and a Spanish page for Mexico, hreflang helps Google serve the right version to the right audience.

There are three ways to implement hreflang: HTML link elements in the head, HTTP headers, or XML sitemaps. Each method has trade-offs. HTML link elements are the most common but can bloat page size when you have dozens of language variants. HTTP headers work for non-HTML files like PDFs. Sitemaps are often the cleanest approach for large sites because they keep the annotations separate from the page markup.

The team spends significant time on the most common mistakes they see. The biggest one is asymmetric annotations. If page A points to page B as its Spanish equivalent, page B must also point back to page A as its English equivalent. When this bidirectional confirmation is missing, Google ignores the annotations entirely. This is the single most frequent cause of hreflang failures.

Another common issue is using incorrect language or region codes. hreflang uses ISO 639-1 language codes and ISO 3166-1 Alpha-2 region codes. Using "en-UK" instead of "en-GB" is a mistake that breaks the annotation silently. Google will not flag this as an error in Search Console, making it harder to detect.

Key Takeaways

1. hreflang is a signal, not a directive. Google treats hreflang annotations as hints rather than hard rules. If the page content does not match the declared language, Google may ignore the annotation and use its own language detection instead.

2. Self-referencing hreflang is required. Every page in a set of language variants must include an hreflang tag pointing to itself, not just to its alternatives. Omitting the self-reference is a common oversight that weakens the signal.

3. x-default is your fallback. The x-default value tells Google which page to show users who do not match any of your specified language-region combinations. Typically this points to your main English page or a language selector page.

4. Canonicalization interacts with hreflang. If you have canonical tags pointing to a different URL, they can conflict with hreflang annotations. The canonical URL should be consistent with what your hreflang tags declare. Conflicting signals cause Google to make its own decisions, which may not be what you intended.

5. Validate with the International Targeting report. Search Console provides an international targeting report that flags hreflang errors. The team recommends checking this report regularly, especially after deployments that touch URL structure or template markup.

Beyond the Basics

One nuance the episode highlights is the difference between language targeting and region targeting. A site can target Spanish speakers globally with es or specifically target Spanish speakers in Mexico with es-MX. Using region codes when you do not actually have region-specific content creates unnecessary complexity and maintenance burden.

The team also discusses content duplication concerns. Pages in the same language targeting different regions (English for the US vs. English for Australia) need enough content differentiation to justify separate URLs. If the content is identical, Google may consolidate them regardless of hreflang signals.

For sites using subdirectories (/en/, /es/, /fr/), the URL structure must be consistent and crawlable. If Google cannot discover and crawl all language variants, the hreflang annotations become meaningless. Internal linking between language versions and proper sitemap inclusion are essential.

What This Means for Your Business

If you serve customers in multiple countries or languages, hreflang implementation directly affects whether the right audience sees the right content. Poor implementation means your US page might show up for Mexican users, or your Spanish content might never surface for Spanish-speaking searchers.

For businesses expanding internationally, getting this right from the start is significantly easier than fixing it after the fact. Retrofitting hreflang across an existing site with hundreds of pages is one of the more tedious technical SEO projects.

At Demand Signals, our WordPress Development and React / Next.js teams build internationalization support into the architecture from day one. Combined with our LLM Optimization work, we ensure your content surfaces correctly across both traditional search and AI-driven discovery, regardless of language or region.