How To Use Hreflang Tags For International SEO?
Hreflang is one of the most misunderstood technical implementations in international SEO. Get it right, and Google serves the correct version of your site to the right audience in the right country.
Hreflang is one of the most misunderstood technical implementations in international SEO. Get it right, and Google serves the correct version of your site to the right audience in the right country.
Get it wrong, and you end up with ranking cannibalisation, duplicate content issues, and organic traffic going to pages that were never meant to rank in that market.
Correct hreflang implementation is one of the foundational requirements for scalable international SEO. This guide covers what hreflang tags actually do, how to implement them correctly, and the mistakes that quietly undermine international organic visibility.
Incorrect hreflang implementation can lead to indexation confusion, duplicate regional variants competing against each other, and users landing on the wrong country or language version of your site.
Hreflang tags are HTML attributes that tell Google which language and regional version of a page to serve to users in specific locations. They sit in the <head> of your page or in your XML sitemap and signal to search engines: “this page is for users who speak this language in this region.”
A basic hreflang tag looks like this:
<link rel=”alternate” hreflang=”en-gb” href=”https://www.example.com/uk/product/” />
The hreflang attribute contains a language code (en, fr, de) and optionally a country code (GB, FR, DE). Together, they define the target audience for that URL. Without hreflang, Google has to guess which version of your content to serve. It often guesses wrong.
Not every international site needs hreflang. You need it when:
If your site only targets one language in one country, hreflang is not necessary. Adding it incorrectly in that scenario creates more problems than it solves.
There are three ways to implement hreflang tags. Each has its use case.
Place hreflang tags in the <head> section of each page. Every language and regional variant of the page must be included, and each page must reference all other variants, including itself.
<link rel=”alternate” hreflang=”en-gb” href=”https://www.example.com/uk/trainers/” />
<link rel=”alternate” hreflang=”en-us” href=”https://www.example.com/us/trainers/” />
<link rel=”alternate” hreflang=”de” href=”https://www.example.com/de/trainers/” />
<link rel=”alternate” hreflang=”x-default” href=”https://www.example.com/trainers/” />
The x-default tag is used to specify the fallback page for users who do not match any of your defined hreflang targets. While not mandatory, it is strongly recommended for international sites targeting multiple regions or languages.
For large ecommerce catalogues with thousands of pages, implementing hreflang in the HTML of every single page is impractical. Including it in your XML sitemap is a cleaner, more scalable approach.
Each URL entry in the sitemap should reference all its alternate versions using <xhtml:link> tags.
For non-HTML files such as PDFs, hreflang can be implemented via HTTP response headers. This is rarely needed for standard ecommerce SEO stores.
These are the errors we find most frequently when auditing international ecommerce sites as part of our international SEO services.
Hreflang must be reciprocal. If your UK page references your US page, your US page must reference your UK page. Missing return tags mean Google cannot confirm the relationship and ignores the implementation entirely.
Language codes must follow ISO 639-1 format (en, fr, de). Country codes must follow ISO 3166-1 Alpha-2 format (GB, US, FR). Using “uk” instead of “GB” for the country code is one of the most common errors and renders the tag invalid.
If any URL referenced in your hreflang implementation returns a redirect, a 404, or is set to no-index, Google will disregard the entire cluster. Every URL in the hreflang set must be indexable and return a 200 status.
Many stores implement hreflang on the homepage and collection pages but neglect product pages. For ecommerce, product pages carry the highest commercial intent. An incomplete hreflang implementation at the product level leaves your most important pages exposed to cannibalisation.
Without an x-default tag, Google has no fallback for users who do not match any of your defined language or country targets. This leads to inconsistent serving, particularly in markets you have not explicitly targeted.
Hreflang does not work in isolation. It needs to be matched to a coherent international site structure. The three main options are:
ccTLDs (country-code top-level domains): Separate domains per country (example.co.uk, example.de). Strongest geotargeting signal. Highest maintenance overhead.
Subdirectories: A single domain with country-specific folders (example.com/uk/, example.com/de/). Easier to maintain, simpler from a technical SEO perspective, and effective at consolidating domain authority. This is the preferred structure for most growing ecommerce SEO brands.
Subdomains: Separate subdomains per country (uk.example.com, de.example.com). Can be treated as separate sites by Google. Less common for ecommerce.
Hreflang works across all three structures, but your implementation must match your chosen architecture. A mismatch between site structure and hreflang signals is one of the fastest ways to create indexation problems at scale.
If you already have hreflang in place, auditing it regularly is essential. Crawl your site with tools such as Screaming Frog, Sitebulb, or Ahrefs to surface missing return tags, invalid hreflang codes, and broken URLs within hreflang clusters. Google Search Console can still help identify indexation inconsistencies across international page variants, but hreflang auditing typically requires dedicated crawling tools.
For ecommerce SEO brands managing thousands of product URLs across multiple markets, this audit should be part of a regular technical SEO review rather than a one-off check.
Hreflang is one component of a broader ecommerce SEO and international SEO search strategy. Correct implementation ensures Google understands your site structure and serves the right content to the right audience. But it needs to sit alongside localised content, market-specific keyword research, and technically sound crawl architecture to drive real organic revenue across markets.
If your international organic performance is underdelivering, the problem is rarely a single missing tag. It is usually a combination of structural issues that compound over time. Searchflex’s international SEO services are built to diagnose and resolve these issues across complex, multi-market ecommerce catalogues.
Searchflex helps ecommerce brands build an international SEO infrastructure that scales. From hreflang implementation to full multi-market strategy, we identify what is holding your organic performance back and fix it. Book a free consultation today.