How to implement hreflang tags if you target multiple regions

Why hreflang tags are critical for multiregional SEO

When you create content that is similar—or even identical—for different countries or regions, such as the US and UK, you’re walking a fine line in SEO. To search engines, this may look like duplicate content. For example, a product page for "running shoes" might have the same layout, images, and description, but the UK version uses pounds and British spelling (“trainers”), while the US version shows prices in dollars and uses American spelling.

Without clear signals, Google can get confused. It may:

Index only one version and ignore the rest.
Display the wrong version in search results.
Choose arbitrarily which version ranks, regardless of where the search comes from.

This leads to a frustrating user experience and, worse, lost conversions. Imagine a Canadian shopper landing on your US page, seeing US dollar prices, and abandoning the site due to shipping or currency concerns—even though you had a perfectly localized Canadian page available.

How hreflang tags work

Hreflang tags are snippets of HTML code that live in the <head> section of your page (or within your XML sitemaps). They communicate to search engines like Google what language and regional version of a webpage should be shown to users based on their location and browser language settings.

The structure of a hreflang tag

Here’s a simple example of a hreflang tag in HTML:

Let’s break down what each part means:

rel="alternate": This tells Google that the linked page is an alternate version of the current one. It’s not a duplicate or separate piece of content—it’s meant for a different audience.
hreflang="en-us": This is the language-region combination. In this case:
- en stands for English (ISO 639-1 language code).
- us stands for the United States (ISO 3166-1 Alpha 2 country code).
This tells Google that the linked page is in English and intended for users in the United States.
href="https://example.com/us/": This is the actual URL for the page that serves that language and region combination. It must be the fully qualified (absolute) URL, not a relative path.

Include all variations and ensure reciprocity

When you implement hreflang tags, it's not enough to just declare them on one page. Every regional version of a page must list all other versions—including itself. This creates a reciprocal relationship that Google uses to verify the intent and reduce confusion.

For example, on https://example.com/us/, you might include:

And the UK version (https://example.com/uk/) would have the same list, but with URLs corresponding to the appropriate regional pages.

Step-by-step: How to implement hreflang for multiple regions

There are three main ways to structure your website for international or multiregional audiences: using subdirectories, subdomains, or completely separate domains. Each method is valid, and the best choice depends on your technical setup, SEO strategy, and available resources. Here's how to apply hreflang tags in each case.

Step 1: Set up subdirectories for each region or language

What you need to do:

Create folders under your main domain for each target market. For example:
- example.com/us/ → for United States
- example.com/uk/ → for United Kingdom
- example.com/fr/ → for France
- example.com/es/ → for Spain

How to do it:

If using WordPress: Use a plugin like WPML or Polylang to generate and manage language-specific subdirectories.
If using a static or custom site: Manually create folder structures on your server or codebase, e.g., /us/, /fr/, etc.

Important notes:

Ensure your web server or CMS routes traffic properly to each folder.
Don’t use vague slugs like /en/ if you're targeting countries—be specific (/us/, /uk/, etc.).

Step 2: Create regionally optimized versions of each page

What you need to do:

For every core page (e.g., your homepage or product pages), create a version within each subdirectory that’s tailored to that country.

How to do it:

Copy the base page into each subdirectory and localize the content:
- Translate language correctly (e.g., “trousers” in UK English vs. “pants” in US English).
- Adjust currencies (e.g., EUR, USD, GBP).
- Update shipping, taxes, phone numbers, date formats, etc.
- Swap out location-specific images or testimonials if relevant.

Pro tip: You can use translation services or AI tools to get initial translations, but have a native speaker review them for accuracy.

Step 3: Add hreflang tags to the of each page

What you need to do:

Insert a <link rel="alternate" hreflang="..."> tag for each version of the page into the <head> section of every localized page.

How to do it:

On example.com/us/product-name/, add:

Do the same for each country version, swapping the hreflang and href values accordingly.

Every version must list all other versions, including itself (this is called reciprocity).

Avoid this mistake: Don’t forget x-default. It catches users whose language or country doesn't match your specified tags.

Step 4: Set canonical tags correctly on each version

What you need to do:

Ensure each localized page has a <link rel="canonical" ...> tag pointing to itself, not to another regional version.

How to do it:

On example.com/fr/product-name/, use:

Why it matters:

If you point the canonical tag to a different region (e.g., all pages canonicalizing to the US version), you’re telling Google that version is the only “valid” one—negating the value of your hreflang tags.

Pro tip: Use relative canonicals only if your CMS fully supports them. Absolute URLs are safest.

Step 5: Use Google Search Console to check your international targeting

What you need to do:

Tell Google what you’ve done and validate it.

How to do it:

1. Go to Google Search Console (https://search.google.com/search-console).

2. dd your entire domain as a property if you haven’t already.

Navigate to:

Legacy tools and reports

→ International Targeting

Use the Language tab to verify that Google is detecting your hreflang tags correctly.
The Country tab is optional—but use it only if a subdirectory is strictly for users in one specific country.

Bonus tip: Use tools like Screaming Frog, Ahrefs, or Chrome extensions like "Hreflang Tag Checker" to audit for missing, broken, or inconsistent tags.

Step 1: Set up subdirectories for each region or language

What you need to do:

Create folders under your main domain for each target market. For example:
- example.com/us/ → for United States
- example.com/uk/ → for United Kingdom
- example.com/fr/ → for France
- example.com/es/ → for Spain

How to do it:

If using WordPress: Use a plugin like WPML or Polylang to generate and manage language-specific subdirectories.
If using a static or custom site: Manually create folder structures on your server or codebase, e.g., /us/, /fr/, etc.

Important notes:

Ensure your web server or CMS routes traffic properly to each folder.
Don’t use vague slugs like /en/ if you're targeting countries—be specific (/us/, /uk/, etc.).

Step 2: Create regionally optimized versions of each page

What you need to do:

For every core page (e.g., your homepage or product pages), create a version within each subdirectory that’s tailored to that country.

How to do it:

Copy the base page into each subdirectory and localize the content:
- Translate language correctly (e.g., “trousers” in UK English vs. “pants” in US English).
- Adjust currencies (e.g., EUR, USD, GBP).
- Update shipping, taxes, phone numbers, date formats, etc.
- Swap out location-specific images or testimonials if relevant.

Pro tip: You can use translation services or AI tools to get initial translations, but have a native speaker review them for accuracy.

Step 3: Add hreflang tags to the of each page

What you need to do:

Insert a <link rel="alternate" hreflang="..."> tag for each version of the page into the <head> section of every localized page.

How to do it:

On example.com/us/product-name/, add:

Do the same for each country version, swapping the hreflang and href values accordingly.

Every version must list all other versions, including itself (this is called reciprocity).

Avoid this mistake: Don’t forget x-default. It catches users whose language or country doesn't match your specified tags.

Step 4: Set canonical tags correctly on each version

What you need to do:

Ensure each localized page has a <link rel="canonical" ...> tag pointing to itself, not to another regional version.

How to do it:

On example.com/fr/product-name/, use:

Why it matters:

If you point the canonical tag to a different region (e.g., all pages canonicalizing to the US version), you’re telling Google that version is the only “valid” one—negating the value of your hreflang tags.

Pro tip: Use relative canonicals only if your CMS fully supports them. Absolute URLs are safest.

Step 5: Use Google Search Console to check your international targeting

What you need to do:

Tell Google what you’ve done and validate it.

How to do it:

1. Go to Google Search Console (https://search.google.com/search-console).

2. dd your entire domain as a property if you haven’t already.

Navigate to:

Legacy tools and reports

→ International Targeting

Use the Language tab to verify that Google is detecting your hreflang tags correctly.
The Country tab is optional—but use it only if a subdirectory is strictly for users in one specific country.

Bonus tip: Use tools like Screaming Frog, Ahrefs, or Chrome extensions like "Hreflang Tag Checker" to audit for missing, broken, or inconsistent tags.

Avoid these common hreflang mistakes

Implementing hreflang tags correctly is critical but it’s surprisingly easy to mess up. These five mistakes are among the most common and can seriously disrupt your international SEO strategy.

What it means:
Each localized page must include a hreflang tag that points to itself, not just to the other versions.

Why it matters:
Google uses hreflang to map all the regional versions of the same content. If a page doesn't reference itself, it breaks that "chain," and Google may ignore the entire hreflang setup for that group of URLs.

Correct example for a French page (/fr/):

What it means:
Some sites incorrectly set all localized pages to use the same canonical tag (often pointing to the main language or homepage), which contradicts what hreflang is trying to do.

Why it matters:
Hreflang tells Google that multiple pages are alternate versions of each other. But a canonical tag pointing to another version tells Google, “Ignore this page and index that one instead.” These mixed signals can lead Google to skip indexing or displaying the correct version.

Correct example for a UK product page:

What it means:
Hreflang values must follow ISO standards:

Language: ISO 639-1 (e.g., en for English, fr for French)
Country: ISO 3166-1 alpha-2 (e.g., GB for United Kingdom, US for United States)

Using unofficial codes like en-UK is invalid and will be ignored.

Correct:

Incorrect:

What it means:
Each version of a page must list all other versions, including itself. These are called reciprocal hreflang links.

Why it matters:
Google needs to see the same hreflang structure across all variations. If one page links to three alternates, but another only links to two, Google may ignore the hreflang signals entirely.

Correct:
All pages reference the full set:

What it means:
The x-default hreflang tag is used to define a "default" version of the page for users whose language or location doesn’t match any specified tag.

Why it matters:
Without an x-default, Google may show an unintended version of your site to users in unlisted regions. For instance, someone in Singapore might see your US page instead of a neutral or international one.

Correct usage:

Testing and Maintaining Hreflang Tags

Setting up hreflang tags is just the beginning. Without regular testing and upkeep, errors can easily creep in ,especially on large or frequently updated sites. Here’s how to properly test your setup and maintain it long-term.

How to test your hreflang tags

Start with Google Search Console, which provides a built-in “International Targeting” report. This tool helps you identify errors like missing return tags, invalid language-region codes, or broken links. It’s essential to check this after initial implementation and periodically afterward, especially when launching new regions.

Another quick and useful tool is the Hreflang Tag Checker Chrome extension. By navigating to a page and activating the extension, you can instantly see whether your hreflang tags are present, correctly structured, and pointing to the right URLs. This is especially handy when doing spot checks during development or after a deployment.

For a full-scale audit, use advanced SEO tools like Screaming Frog or Ahrefs. These platforms can crawl your entire site, detect missing or incorrect hreflang tags, and even report mismatches between canonical and hreflang URLs. For larger sites or ecommerce platforms with thousands of pages, these audits are crucial.

Maintaining hreflang accuracy over time

Keeping your hreflang setup healthy requires regular attention. Ideally, you should run an audit every quarter to catch any issues early. Websites evolve pages are added, removed, or redirected and those changes can silently break your hreflang configuration.

If you’re using XML sitemaps to manage hreflang, automating sitemap updates is a smart move. Tools like Yoast SEO (for WordPress) or custom scripts can regenerate your sitemaps every time new content is added. Be sure to resubmit them to Google Search Console after major updates to ensure search engines stay up to date.

Finally, remember that hreflang works best when paired with true localization. That means not only translating your content but also adapting it for regional preferences think local currency, cultural references, and market-specific promotions. By keeping your content fresh and relevant in each region, you reinforce the signals your hreflang tags are sending and improve both user experience and rankings.

How to implement hreflang tags if you target multiple regions

Why hreflang tags are critical for multiregional SEO

How hreflang tags work

The structure of a hreflang tag

Include all variations and ensure reciprocity

Include all variations and ensure reciprocity

Step-by-step: How to implement hreflang for multiple regions

Step 1: Set up subdirectories for each region or language

Step 2: Create regionally optimized versions of each page

Step 3: Add hreflang tags to the of each page

Step 4: Set canonical tags correctly on each version

Step 5: Use Google Search Console to check your international targeting

Step 1: Set up subdirectories for each region or language

Step 2: Create regionally optimized versions of each page

Step 3: Add hreflang tags to the of each page

Step 4: Set canonical tags correctly on each version

Step 5: Use Google Search Console to check your international targeting

Avoid these common hreflang mistakes

Testing and Maintaining Hreflang Tags

How to test your hreflang tags

Maintaining hreflang accuracy over time

Aron van Gilst Rodríguez

Ready to start scaling your business?