Hreflang implementation that concentrates authority — instead of cannibalizing it.
Done right, hreflang signals to Google which language and region version to serve. Done wrong, it splits your rankings and cannibalizes traffic. We do it right at scale.
What is hreflang implementation?
Hreflang implementation is the technical work of declaring, on every page, which language and region version is appropriate for each user — so Google serves the right version to the right audience. Hreflang declarations can live in HTML head tags, HTTP headers, or XML sitemaps; for large sites, XML sitemaps are preferred. Done correctly, hreflang concentrates authority across variants. Done incorrectly, it cannibalizes rankings.
— Resocial Technical SEO Auditor · Updated 2026-05-09Hreflang is one of the most common technical SEO failures.
Sites have hreflang tags but missing reciprocal references. They use wrong language codes (zh instead of zh-CN). They mix HTML head and XML sitemap declarations and produce conflicts. They forget x-default. They reset canonical tags during platform migrations and break the system.
We audit, fix, and implement at scale. For sites with 100+ language/region URLs, XML sitemap-based hreflang is the only sustainable approach — and we automate it.
Hreflang done at scale.
Hreflang audit
Comprehensive review of current implementation. Identification of missing reciprocals, wrong codes, conflicting signals.
Implementation strategy
Decision on HTML vs HTTP header vs XML sitemap based on site scale and CMS capability.
Code mapping
Correct ISO 639-1 language codes plus optional ISO 3166-1 region codes. Documented per audience.
x-default handling
Proper fallback declaration for users in markets not explicitly targeted.
Reciprocal validation
Every hreflang declaration confirmed bidirectionally. Automated validation in CI to prevent regression.
Migration-resistant architecture
Hreflang preserved during replatforming. Built into the migration playbook.
Hreflang questions.
HTML head, HTTP headers, or XML sitemap?
For sites under 1000 URLs: HTML head is fine. For larger sites: XML sitemap is essentially required — cleaner to maintain, less prone to bugs, easier to update at scale.
What's the most common hreflang mistake?
Missing reciprocal references. If the German page declares hreflang to the English page, the English page must declare hreflang back. Even 5% wrong breaks the system for those pages.
Do hreflang signals replace ccTLDs?
They solve different problems. ccTLDs signal country-of-origin. Hreflang signals which version to serve. We typically recommend subdirectories with strong hreflang for most enterprises.
What about canonical tags with hreflang?
Each language/region URL should have a self-referencing canonical (NOT canonical to a "primary" version). Mixing canonical-to-master with hreflang-to-variants is a common source of cannibalization.