Hreflang is an HTML attribute that tells search engines which language and regional version of a page to serve to users in specific locations — essential for multinational websites with country-specific or language-specific content variations to prevent duplicate content issues and serve the correct version to each audience.
Quick Answer
Hreflang is an HTML attribute that tells search engines which language and regional version of a page to serve to users in specific locations — essential for multinational websites with country-specific or language-specific content variations to prevent duplicate content issues and serve the correct version to each audience.
Hreflang requires full reciprocity — every page must include hreflang tags pointing to all variants, and all variants must link back. Non-reciprocal configurations are silently ignored by Google.
The self-referencing hreflang tag is mandatory — a page must include a hreflang tag pointing to itself, not just to other variants.
Validate hreflang with Screaming Frog's hreflang validation mode — manual checking of individual pages cannot detect non-reciprocal errors across a large site.
Key Takeaways
Hreflang requires full reciprocity — every page must include hreflang tags pointing to all variants, and all variants must link back. Non-reciprocal configurations are silently ignored by Google.
The self-referencing hreflang tag is mandatory — a page must include a hreflang tag pointing to itself, not just to other variants.
Validate hreflang with Screaming Frog's hreflang validation mode — manual checking of individual pages cannot detect non-reciprocal errors across a large site.
How Hreflang Works
Hreflang (rel="alternate" hreflang="x") tells Google and other search engines that multiple versions of a page exist for different languages or regions, and which version to serve to which user. Without hreflang, a search engine encountering similar pages in English (US), English (UK), and French may treat them as duplicate content or serve the wrong version to international searchers. Hreflang signals search engines to treat these as intentional country/language variants, not duplicates, and to serve the geographically appropriate version.
Why Hreflang Matters for B2B Marketing
Hreflang values combine language codes (ISO 639-1) and optional region codes (ISO 3166-1 alpha-2): "en" targets all English speakers; "en-US" targets English speakers in the United States; "en-GB" targets English speakers in the United Kingdom; "fr-FR" targets French speakers in France; "fr-CA" targets French speakers in Canada; "x-default" specifies the fallback page for users who don't match any specific hreflang target. Every page that uses hreflang must include a self-referencing hreflang tag (pointing to itself) plus hreflang tags for all other language/region variants — hreflang is only valid when implemented reciprocally across all variants.
Hreflang: Best Practices & Strategic Application
Three valid implementation methods exist: HTML link tags in the <head> section, HTTP response headers (for non-HTML files like PDFs), and XML sitemap annotations. Most websites use the HTML link tag method. The critical requirement is reciprocity: if page A links to page B via hreflang, page B must link back to page A. Google ignores hreflang configurations that are not fully reciprocal — this is the most common implementation error and the hardest to detect without systematic validation.
Agency Perspective: Hreflang in Practice
Validating hreflang implementation requires checking the full cross-site annotation graph, not just individual pages. Screaming Frog's hreflang validation mode crawls all URLs referenced in hreflang tags and verifies reciprocity, correct language/region codes, and consistent implementation across all variants. Google Search Console's International Targeting report surfaces hreflang errors site-wide. Common errors: missing self-referencing tags, non-reciprocal annotations, incorrect language codes (using "en-UK" instead of "en-GB"), and using hreflang on redirect URLs rather than canonical pages.
Frequently Asked Questions: Hreflang
Hreflang is an HTML attribute that tells search engines which language and regional version of a page to serve to users in specific locations — essential for multinational websites with country-specific or language-specific content variations to prevent duplicate content issues and serve the correct version to each audience.
Hreflang is needed when your site has similar content targeting different language or country audiences. Scenarios requiring hreflang: multiple language versions of the same page (English, Spanish, French); country-specific pages with same-language content (US vs. UK vs. Australia English); global e-commerce with local currency and product variation pages. Hreflang is not needed for completely distinct content across markets, or for sites that only serve one language and one country.
Canonical tags tell search engines "this is the preferred version of duplicate or near-duplicate content — consolidate all signals here." Hreflang tells search engines "these are all valid, distinct versions for different audiences — serve the appropriate one to each user." They serve opposite purposes: canonical consolidates; hreflang differentiates. Using canonical tags across international pages (pointing to one "master" version) instead of hreflang will cause Google to ignore all but the canonical version in international markets.
Hreflang doesn't directly improve rankings — it improves the accuracy of which page version is served to which audience. The indirect ranking benefit is significant: without hreflang, search engines may serve users the wrong language/country page, increasing bounce rates and reducing engagement signals. Additionally, hreflang prevents duplicate content dilution across language variants, preserving the authority of each localized page rather than having it split across variants.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes our services 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
