Hreflang is an HTML attribute that helps search engines understand which language and regional version of a page to show users. For example, if your business has separate pages for the UK, US, and Ireland, hreflang tags help Google show the right version to each audience.
Without hreflang SEO, businesses can face three common problems:
- Wrong page, wrong audience: UK users may see a US page with dollar prices and US shipping details.
- Duplicate content confusion: Similar UK and US pages may look like duplicate content to search engines.
- Wasted localisation: Your localised content may not reach the right audience without clear regional signals.
Hreflang is not a ranking factor. It does not directly improve rankings. Instead, hreflang tags help search engines understand and serve the correct version of your content to the right users. For businesses targeting multiple countries or languages, proper hreflang SEO implementation is an important part of international SEO.
At Clickmasters SEO Agency UK, we work with UK businesses expanding into international markets on a regular basis, and hreflang is one of the technical issues that comes up most often during site audits. This guide is based on that hands-on implementation experience, not just documentation.
How Do Hreflang Tags Work?
An hreflang attribute is a signal, not an instruction. It sits in a page’s code, in the HTML <head>, an HTTP header, or an XML sitemap, and points to alternate versions of the same page for different languages or regions. Google uses these hreflang HTML signals to understand the relationship between localised pages.
A basic alternate hreflang tag looks like this:
<link rel=”alternate” hreflang=”en-gb” href=”https://example.com/uk/” />
This tells Google that a UK-specific version of the page is available at that URL. However, one tag alone is not enough.
Hreflang works in groups, not in isolation. Each page should reference the other pages in the same language or regional group, including itself. For example, your UK page should reference the US and French versions, while those pages should also reference the UK version and each other. This is known as a reciprocal or return link.
If one page does not link back correctly, Google may ignore the hreflang attribute. This is why hreflang errors can become difficult to find across large international websites.
It is also important to know what hreflang HTML does not do. It does not automatically redirect users, translate content, or force a specific language version. It simply helps Google understand which version of a page is intended for a particular language or region.
When Should You Use Hreflang Tags?
Hreflang is useful when your website has different URLs for different countries or languages. An hreflang HTML tag helps Google understand which version is intended for each audience.
When you should use hreflang HTML tags:
- You have separate URLs for different countries or languages, such as /uk/, /us/, or /fr/.
- Your pages have regional differences in currency, spelling, shipping, legal information, or product availability.
- You target multiple English-speaking markets, such as the UK, US, Canada, Ireland, or Australia.
- You run an international e-commerce store, SaaS website, or publishing site with localised content.
- Your analytics show that visitors are landing on the wrong regional page.
You may not need an hreflang meta tag if:
- You have one global English page with no regional differences.
- Your website only targets one local market.
- Your regional pages are essentially duplicates with no meaningful differences. In this case, consolidating them may be better.
How Google Uses Hreflang
Google hreflang signals help search engines understand which regional or language version of a page is most relevant to a searcher. They do not translate pages or automatically redirect visitors. Hreflang is normally implemented as an element in the HTML <head>, an HTTP header, or an XML sitemap—not as a traditional meta tag.
Understanding Hreflang Language and Country Codes
Hreflang values combine two international standards, joined by a hyphen: an ISO 639-1 language code and, optionally, an ISO 3166-1 Alpha-2 country code.
Format: hreflang=”language-COUNTRY”
| Feature | Canonical Tag | Hreflang Tag |
|---|---|---|
| Main purpose | Identifies the main version of similar pages | Identifies the correct language or regional version |
| Main goal | Consolidates duplicate or similar URLs | Helps serve the right page to the right audience |
| Example | The UK page points to the main UK URL. | The UK page points to US, French, and other versions. |
| Indexing | Can signal which version should be indexed | Helps keep different regional versions available |
| Use case | Duplicate or very similar pages | Different language or country versions |
Order matters—language always comes first.
Writing gb-en instead of en-gb is a common error, and search engines will simply ignore the malformed tag rather than trying to interpret it.
The UK’s country code is GB, not UK.
This trips up a surprising number of UK businesses, since the country’s own domain extension is .uk and “UK” is the everyday abbreviation used in speech and writing. But the ISO 3166-1 standard uses GB (Great Britain) as the official country code, so the correct hreflang value is always en-gb.
Language-only codes are valid but broader.
Using en alone targets all English speakers regardless of country, which is fine if you’re not differentiating by region but still want to separate English content from, say, French or German versions.
x-default isn’t a language or country—it’s a fallback.
It specifies which page to serve when a visitor’s language/location doesn’t match any of your defined hreflang values. This is typically your homepage, a global landing page, or a country/language selector. It’s optional but recommended, particularly for sites with several regional variants, since it prevents visitors outside your target markets from randomly landing on one specific regional version.
Region codes are not the same as top-level domains.
A common misconception is that if your domain is .uk, hreflang should say uk. Domain extensions and ISO country codes are separate systems that happen to overlap for many countries but not all.
Advantages of Hreflang
Hreflang helps international websites show the right version of a page to the right audience. Some key benefits include:
- Better international targeting: Helps Google understand which page is intended for a specific country or language.
- Improved user experience: Visitors see relevant currency, spelling, shipping details, and local information.
- Less wrong-page traffic: Reduces the chance of users landing on another country’s version of a page.
- Clearer page relationships: Helps search engines understand that similar pages are regional or language variations.
- Better visibility for local versions: Helps the appropriate regional page appear for relevant searches.
- Supports international growth: Makes it easier to manage websites targeting multiple countries and languages.
Hreflang Tags vs. Canonical Tags
| Feature | Canonical Tag | Hreflang Tag |
|---|---|---|
| Main purpose | Identifies the main version of similar pages | Identifies the correct language or regional version |
| Main goal | Consolidates duplicate or similar URLs | Helps serve the right page to the right audience |
| Example | The UK page points to the main UK URL. | The UK page points to US, French, and other versions. |
| Indexing | Can signal which version should be indexed | Helps keep different regional versions available |
| Use case | Duplicate or very similar pages | Different language or country versions |
A common mistake is pointing the canonical tag on every regional page to the main version, such as the US page, while also using hreflang to signal all versions. This can confuse search engines because the canonical tag indicates one page is the main version, while hreflang indicates that other versions should be shown to specific audiences.
Each regional page should normally have a self-referencing canonical tag. For example, the UK page should be canonical to the UK URL, while the US page should be canonical to the US URL. Then, hreflang tags should connect these pages as alternate regional versions.
How to Implement Hreflang Tags

Google supports three main methods for adding hreflang tags. You usually only need to choose one method and use it consistently across your website.
HTML Link Tags
This is the most common method for small and medium-sized websites. You add hreflang <link> tags inside the <head> section of each page. Each page should include links to all its language or regional versions, including itself.
HTTP Headers
HTTP headers are useful for files that do not have HTML <head>, such as PDFs and other downloadable files. In this method, hreflang information is added to the server response instead of the page code.
XML Sitemap
With this method, hreflang information is added to your XML sitemap instead of every individual page. It can make hreflang easier to manage and update, especially for large websites with hundreds or thousands of regional pages.
Hreflang Implementation Examples
HTML link tags (placed at the end of the <head> of every page in the group):
<link rel=”alternate” hreflang=”en-gb” href=”https://example.com/uk/product” />
<link rel=”alternate” hreflang=”en-us” href=”https://example.com/us/product” />
<link rel=”alternate” hreflang=”fr-fr” href=”https://example.com/fr/produit” />
<link rel=”alternate” hreflang=”x-default” href=”https://example.com/” />
Note that this exact block, or one equivalent to it, needs to appear on the UK page, the US page, and the French page each listing all the others (including itself).
HTTP header (for a non-HTML file like a PDF):
Link: <https://example.com/uk/file.pdf>; rel=”alternate”; hreflang=”en-gb”,
<https://example.com/us/file.pdf>; rel=”alternate”; hreflang=”en-us”
XML sitemap: xml
<url>
<loc>https://example.com/uk/product</loc>
<xhtml:link rel=”alternate” hreflang=”en-gb” href=”https://example.com/uk/product” /
<xhtml:link rel=”alternate” hreflang=”en-us” href=”https://example.com/us/product” />
<xhtml:link rel=”alternate” hreflang=”fr-fr” href=”https://example.com/fr/product” />
</url>
In the sitemap method, each <url> block needs its own complete set of alternate references, including a self-referencing entry—the same reciprocal rule applies; it’s just centralized in one file rather than spread across page templates.
Important Hreflang Rules
- Every page should reference itself.
- Each regional page should reference the other pages in its hreflang group.
- Use the final, canonical URLs in your hreflang tags.
- Avoid URLs that redirect or use different HTTP/HTTPS or trailing-slash versions.
- Keep language and country codes accurate.
If you want to create tags quickly, an hreflang tags generator can help produce the required code. Tools such as hreflang tags lite can also be useful for checking or generating hreflang implementations, but always review the generated URLs and language codes before publishing.
How to Implement Hreflang Tags in WordPress
WordPress has no native hreflang support, so UK businesses typically rely on plugins or manual development work.
Using an SEO plugin:
Yoast SEO Premium and Rank Math Pro both offer hreflang support, but they generally need to be paired with a multilingual/multiregional plugin to actually manage separate content versions, the SEO plugin handles the tag output, not the content structure itself.
Using a multilingual plugin:
WPML and Polylang are the two most established options for managing multiple language or region versions of WordPress content. Once you register pages as translations or regional variants of one another within the plugin, hreflang tags are generated automatically and kept in sync as you add or update content—including the reciprocal linking that’s otherwise easy to get wrong manually.
Manual implementation:
For developers who prefer not to add plugin overhead, hreflang tags can be output by hooking into WordPress’s wp_head action and dynamically generating link elements based on a custom mapping of pages to language/region codes. This gives full control but means you’re responsible for maintaining the reciprocal linking logic yourself as pages are added or removed.
Common Hreflang Mistakes to Avoid

Missing return links, Page A references Page B, but Page B doesn’t reference back to Page A, breaking the reciprocal requirement.
Wrong country codes
Using ‘uk‘ instead of the correct ‘GB‘
No self-referencing tag
Each page should list itself as one of its own hreflang alternates.
Non-canonical URLs in hreflang tags
Mismatched protocols, trailing slashes, or URLs that redirect elsewhere
Conflicting canonical tags
pointing all regional pages at one “master” canonical while hreflang tries to keep them separately indexed. This is where canonical hreflang implementation needs particular attention.
Hreflang on identical, undifferentiated content
adds ongoing maintenance without any real targeting benefit
Forgetting to update hreflang after site changes
URL restructuring, migrations, or new regional pages that aren’t added to the existing cluster
Using hreflang instead of proper redirects for legacy URLs
Hreflang is not a substitute for 301 redirects when a URL has permanently moved.
At Clickmasters SEO Agency UK, the single most frequent issue we find isn’t a coding error, it’s mismatched canonical and hreflang signals left over after a site migration or replatform. Businesses often fix hreflang tags correctly the first time, then break them months later during an unrelated redesign, without realizing the two are connected.
How to Test and Validate Hreflang Tags
Don’t assume an implementation works simply because the code is present in the page source, reciprocal errors are common and easy to miss visually. A hreflang tag checker or hreflang tags testing tool can also help identify implementation issues quickly.
Google Search Console
Under indexing and international targeting reports, Search Console flags hreflang issues, including missing return tags, unrecognized codes, and conflicting canonical signals.
Screaming Frog SEO Spider
Has a dedicated hreflang tab that crawls an entire site and highlights missing, non-reciprocal, or malformed tags across every page at once, this is usually the fastest way to audit a site with many regional URLs.
Ahrefs or Semrush site audit tools
Both flag common hreflang errors as part of a standard technical crawl, useful if you’re already running these tools for other hreflang SEO monitoring.
Manual inspection
View the page source (Ctrl+U) on a sample of pages to confirm tags are present and correctly formatted and that alternate references each other consistently.
Third-party hreflang validators
Several free online tools will check a single URL’s hreflang cluster and confirm whether return links resolve correctly, useful for spot-checking after a fix. These can also help you check hreflang tags after implementation.
It’s worth building hreflang re-checks into your standard process after any site migration, URL restructuring, redesign, or CMS/plugin update, since these are the most common points where previously working tags break silently without any obvious symptom beyond a gradual drop in the affected region’s traffic.
Hreflang Best Practices for International Websites

Use Correct Language and Country Codes
Use valid codes such as en-gb for the UK, en-us for the US, and fr-fr for France.
Make Each Page Self-Referencing
Every page should include an hreflang tag that points to its own URL.
Add Reciprocal Hreflang Links
Each regional or language page should reference all other relevant versions in the same group.
Use Canonical URLs
Make sure hreflang URLs match the final canonical URLs and do not point to redirected pages.
Keep Regional Content Localized
Adapt content for each market, including currency, spelling, pricing, shipping information, and local terms.
Use the x-default tag.
Use x-default for a fallback page when a user’s language or region does not match your targeted versions.
Choose the Right Implementation Method
You can implement hreflang through HTML, HTTP headers, or XML sitemaps. Choose a method that fits your website and use it consistently.
Check Hreflang Regularly
Use SEO crawlers and hreflang testing tools to find missing tags, incorrect URLs, and return-link errors.
Keep Hreflang Pages Indexable
Make sure your localized pages are accessible to search engines and are not blocked by robots.txt or noindex.
Why Choose Clickmasters for Your International SEO?
At Clickmasters, we work with UK businesses expanding into international markets regularly, and hreflang is one of the technical issues that comes up most often during site audits. Agencies like Clickmasters report the same pattern, hreflang problems are rarely caught early because they don’t throw obvious errors; they just quietly suppress traffic from one region while everything else looks fine. This guide is based on hands-on implementation and audit experience, not just documentation.
FAQs
What are hreflang tags?
Hreflang tags tell search engines which language and regional version of a page to show.
Where to put hreflang tags?
Add them in the HTML <head>, HTTP headers, or XML sitemap.
How to add hreflang tags?
Add a separate hreflang link for each language or regional page.
Is hreflang good for SEO?
Yes. Hreflang helps search engines show the correct language or regional page to users.
How to check hreflang tags?
Use Google Search Console, SEO crawlers, or dedicated hreflang testing tools.
Do you always need hreflang tags for international sites?
No. You mainly need hreflang when you have separate pages targeting different languages or regions.
How do hreflang tags work in international SEO?
They help search engines serve the appropriate language or regional URL to users.