For websites targeting users in multiple countries or languages, hreflang tags are one of the most important — and most frequently misconfigured — technical SEO elements. Hreflang tells Google which version of a page to serve to users in specific geographic or linguistic contexts, preventing duplicate content issues and ensuring that the right audience sees the right content. Getting hreflang right is not trivial, but the reward is significant: correct implementation protects international rankings and eliminates a class of technical SEO problems that are otherwise very difficult to diagnose.
What Hreflang Is and When to Use It
The hreflang attribute was introduced by Google in 2011 specifically to handle pages with the same or similar content targeted at different countries or languages. It signals to Google: “This page serves users in [language/country]. Here are the equivalent pages for other language/country combinations.”
You should use hreflang when your site has:
- The same content in multiple languages (e.g., English and French versions of the same page)
- Different content for the same language in different countries (e.g., US English vs. UK English vs. Australian English)
- Any combination of the above in a structured multi-regional site architecture
If you have only one language and target only one country, hreflang is not needed. If you have translated pages that are not connected by hreflang, you likely have duplicate content issues that Google is resolving in ways you cannot control.
How to Implement Hreflang: Three Methods
There are three technically valid implementation methods, each suited to different site architectures:
- HTML <head> tags: Place hreflang link elements in the <head> section of each page. This is the most common method and works for most CMS platforms. Each page must include references to all language/region variants, including itself.
- XML sitemap: Add hreflang attributes within your XML sitemap using the <xhtml:link> element. This is ideal for large sites where editing individual page headers is impractical. The sitemap method keeps implementation centralized but requires the sitemap to be kept rigorously up to date.
- HTTP headers: For non-HTML files (such as PDFs), hreflang can be specified in the HTTP response header. This is the least common implementation and is only required for file types where HTML head tags cannot be used.
Common Hreflang Mistakes and How to Avoid Them
Hreflang is notorious for implementation errors that silently invalidate the entire tag set:
- Missing return tags: Every hreflang relationship must be reciprocal. If Page A references Page B as its French equivalent, Page B must reference Page A as its English equivalent. Missing return tags cause Google to ignore the entire hreflang annotation.
- Wrong language codes: Hreflang uses ISO 639-1 two-letter language codes (“en” for English, “fr” for French) optionally paired with ISO 3166-1 Alpha-2 country codes (“en-US,” “en-GB”). Using the wrong format — “ENG” instead of “en,” or “uk” for Ukrainian when you meant “gb” for Great Britain — invalidates the tag.
- Hreflang pointing to redirects or noindex pages: All hreflang URLs must resolve to canonical, indexable pages. If a URL in your hreflang set returns a 301 redirect or carries a noindex directive, it breaks the annotation.
- x-default omission: The x-default value specifies the fallback page for users who do not match any language/country combination. Omitting it means Google must guess which page to serve to unmatched users.
Validating Your Hreflang Implementation
After implementation, validation is non-negotiable. Tools specifically designed for hreflang validation include Ahrefs Site Audit, Screaming Frog (with hreflang tab), and dedicated tools like Merkle’s hreflang testing tool. Google Search Console’s International Targeting report also surfaces hreflang errors at the property level. Conduct a full validation pass after any site migration, CMS update, or URL structure change that could affect hreflang annotations.
Ready to grow your business online? Contact WebPresence today.