Hreflang is an HTML attribute and XML sitemap directive that tells Google the language and optionally the regional targeting of each page version, enabling correct language/country variant selection in international search results.
Quick Answer
Hreflang is an HTML attribute and XML sitemap directive that tells Google the language and optionally the regional targeting of each page version, enabling correct language/country variant selection in international search results.
Hreflang must be reciprocal — every page in a cluster must reference all others, including itself.
Use XML sitemap implementation for 1,000+ international pages — HTML tags don't scale.
60-70% of enterprise international sites have at least one hreflang error category suppressing market rankings.
Key Takeaways
Hreflang must be reciprocal — every page in a cluster must reference all others, including itself.
Use XML sitemap implementation for 1,000+ international pages — HTML tags don't scale.
60-70% of enterprise international sites have at least one hreflang error category suppressing market rankings.
How Hreflang Implementation Works
Hreflang annotations use ISO 639-1 language codes (en, de, fr, es) optionally combined with ISO 3166-1 Alpha-2 country codes (en-us, en-gb, de-at) to specify language-region combinations. The annotation must be reciprocal — every page in an hreflang cluster must reference all other pages in the cluster, including itself (self-referencing hreflang). A missing self-reference or broken reciprocal link causes Google to ignore the entire hreflang set. For a site with 10 language versions, each page needs 10 hreflang annotations (9 for other variants + 1 for self).
Why Hreflang Implementation Matters for B2B Marketing
Hreflang implementation errors are among the most common and impactful technical SEO issues on international B2B sites. Google's Search Console International Targeting report frequently shows hreflang errors that suppress country-specific rankings without triggering obvious traffic drops — the site still ranks, just not in the intended market. Studies of enterprise international sites find that 60-70% have at least one category of hreflang error, typically non-reciprocal annotations or language codes using the wrong ISO standard (e.g., "zh" instead of "zh-hans" for Simplified Chinese).
Hreflang Implementation: Best Practices & Strategic Application
Best practices: implement hreflang via XML sitemap for sites with more than 1,000 international pages — the alternative (HTML <link> tags in the <head>) becomes unmanageable at scale and creates significant page bloat. Always use lowercase language and country codes. Include x-default pointing to your primary global version for users in non-targeted countries. Validate with hreflang.org's testing tool and Screaming Frog's hreflang auditor after implementation. Re-audit hreflang after any URL structure changes.
Agency Perspective: Hreflang Implementation in Practice
A critical implementation mistake is using hreflang to target multiple countries with the same language code without differentiation — e.g., using "en" for both US and UK versions. This should be "en-us" and "en-gb" respectively. Another common error is implementing hreflang only in HTML tags while also having an XML sitemap — the two sources must be consistent or Google ignores both. When URLs are migrated or changed, hreflang annotations must be updated simultaneously or the broken references will cause the entire cluster to be discarded.
Hreflang is an HTML attribute and XML sitemap directive that tells Google the language and optionally the regional targeting of each page version, enabling correct language/country variant selection in international search results.
x-default is an hreflang value that designates the fallback page for users in countries not explicitly targeted by other hreflang annotations. Always include it pointing to your primary homepage or a language-selector page. Without x-default, users in untargeted countries receive a language version Google selects arbitrarily.
Hreflang can consolidate ranking signals in your primary market by clarifying which version is canonical for each country. Incorrectly implemented hreflang can dilute rankings by creating perceived duplicate content across language variants. Correct implementation generally improves ranking stability across all target markets.
Use three tools: Google Search Console's International Targeting report (shows errors in your submitted hreflang), Screaming Frog's hreflang auditor (crawls all variants to verify reciprocal links), and hreflang.org's testing tool (checks individual URL clusters). Run all three quarterly and after any site structure changes.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes technical seo audit for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked