Hreflang for English: US, UK, Canada, and Australia

English is the most common language on the web, and it is spoken as a primary language in dozens of countries. For hreflang purposes, the main markets are the United States, United Kingdom, Canada, Australia, Ireland, New Zealand, and South Africa. The question most site owners face is whether they need separate English versions for each region or whether a single English page is enough. For a general overview of how hreflang works, see our complete hreflang guide.

This guide covers the codes, the decision framework, and practical implementation examples.

English Hreflang Codes

The hreflang attribute uses ISO 639-1 language codes combined with optional ISO 3166-1 alpha-2 region codes. Here are the codes relevant to English content:

| Code | Meaning | |---|---| | en | English (no region specified) | | en-US | English for the United States | | en-GB | English for the United Kingdom | | en-CA | English for Canada | | en-AU | English for Australia | | en-IE | English for Ireland | | en-NZ | English for New Zealand | | en-ZA | English for South Africa | | en-IN | English for India |

The language code is lowercase. The region code is uppercase. They are separated by a hyphen.

When You Need Regional English Variants

Most English-speaking users can read any variety of English without difficulty. An American can read a British page and vice versa. So why bother with regional variants at all?

The answer is not about comprehension. It is about relevance and user experience.

Pricing and currency

If you sell products or services, users in the UK expect to see prices in GBP, users in Australia expect AUD, and users in the US expect USD. Showing a US user prices in pounds creates friction. This is one of the strongest reasons to create regional variants.

Legal and regulatory content

Privacy policies, terms of service, shipping policies, and return policies differ by jurisdiction. A UK site needs GDPR-compliant privacy notices. A US site may need state-specific disclosures. An Australian site has Australian Consumer Law obligations. These pages almost always require separate regional versions.

Spelling and terminology

The differences are well known: colour vs. color, organisation vs. organization, lift vs. elevator, boot vs. trunk. For informational content, these differences rarely confuse readers. But for product descriptions, marketing copy, and anything where brand voice matters, using the local spelling convention signals that you understand your audience.

Local references and examples

Content that references local institutions, regulations, tools, or customs is more useful when tailored to the region. A guide about tax filing is very different for US, UK, and Australian audiences.

Search intent differences

The same query can have different intent in different regions. "Football" means something very different in the US than in the UK. "First floor" means the ground level in the US but one level up in the UK. If your content addresses topics with regional meaning differences, separate versions improve relevance.

When a Single English Version Is Enough

You do not always need regional variants. A single en version works well when:

• Your content is informational and not tied to any specific country
• You do not sell products or services directly
• Your content does not reference local laws, institutions, or conventions
• Spelling differences are not important to your brand
• You do not have the resources to maintain multiple English versions

Many SaaS documentation sites, technical blogs, and educational resources use a single English version with no regional targeting. This is perfectly fine. Adding regional variants for the sake of it creates maintenance burden without meaningful benefit.

Implementation Examples

Single English version (no regional targeting)

If you have one English version and content in other languages:

<link rel="alternate" hreflang="en" href="https://example.com/en/page/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/page/" />

The en code covers all English speakers globally. No regional distinction is made.

US and UK versions

The most common regional English split:

<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en-us/page/" />

Users in the US see the en-US version. Users in the UK see en-GB. Users in other English-speaking countries (Canada, Australia, India) will not have an exact match. Google will pick one of the two based on its own assessment.

US, UK, Canada, and Australia with a generic fallback

For full coverage of the major English markets:

<link rel="alternate" hreflang="en" href="https://example.com/en/page/" />
<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="en-CA" href="https://example.com/en-ca/page/" />
<link rel="alternate" hreflang="en-AU" href="https://example.com/en-au/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/page/" />

The en version serves as a catch-all for English speakers in countries without a specific variant (New Zealand, Ireland, South Africa, India, and others). Each regional code gets its own tailored page.

English regions plus other languages

A fully international setup:

<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="en-AU" href="https://example.com/en-au/page/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en-us/page/" />

Here, x-default points to the US English version as the global fallback for users who do not match any specific language or region.

Canada: English and French

Canada is a bilingual country, and Canadian sites often need both English and French content. If you target Canada specifically, you will likely have both en-CA and fr-CA pages. See our dedicated hreflang for Canadian sites guide for the full setup.

The short version: Canadian English and American English are very similar. Most sites that create an en-CA variant do so for pricing, legal content, or local product availability rather than language differences.

Handling x-default for English Sites

The x-default tag tells Google what to show users who do not match any hreflang entry. For English-dominant sites, the typical approach is to point x-default to one of your English versions.

If you have a generic en version, point x-default there. If you do not have a generic version, point it to whichever regional version you consider your primary or default experience. For most international businesses, this is either en-US or en-GB.

There is no SEO penalty for any particular x-default choice. Pick the version that makes the most sense for users who fall outside your defined regions.

The en vs. en-US Question

This comes up frequently: if you only have one English version and it uses American English spelling, should you use en or en-US?

Use en if you want to target all English speakers. This is the broader net. Google will serve this version to English speakers everywhere, regardless of country.

Use en-US if you want to signal that the content is specifically for an American audience. This is appropriate when your content contains US-specific pricing, legal references, or product availability.

The practical difference is small for most sites. But if you later add a UK or Australian version, having used en-US from the start makes the transition cleaner. You will not need to change existing tags.

Spelling Differences: Do They Matter for SEO?

Google understands that "colour" and "color" are the same word. It does not penalize or reward either spelling. Users searching for "colour" will find pages that use "color" and vice versa.

That said, Google does use on-page language signals to determine a page's target region. A page full of British spelling (colour, favour, organise, licence) is a signal that the content is intended for a British audience. This can influence which version Google serves to users in different regions, even without hreflang tags.

Hreflang tags are a stronger and more reliable signal than spelling alone. But keeping your spelling consistent with your target region reinforces the signal and improves user experience.

Common Mistakes

Using en-UK instead of en-GB

The ISO 3166-1 code for the United Kingdom is GB, not UK. This is one of the most common mistakes in English hreflang. en-UK is not a valid code and will be ignored by Google. Always use en-GB. For more on valid codes, see our hreflang language codes reference.

Creating regional variants with identical content

If your en-US and en-GB pages have exactly the same content with no differences in spelling, pricing, or anything else, there is no point in having separate pages. Google may treat them as duplicates. Either make the content genuinely different or use a single en version.

Forgetting self-referencing tags

Every page must include a hreflang tag pointing to itself. The en-GB page must include hreflang="en-GB" with its own URL. This is not optional. Missing self-referencing tags can cause Google to ignore the entire hreflang set.

Missing return links

All hreflang relationships must be bidirectional. If your en-US page references en-GB, the en-GB page must reference en-US back. See our troubleshooting guide for tools to check for missing return links.

Overcomplicating the setup

Not every English-speaking market needs its own page. If you serve the US and UK but your content is effectively the same, just use en. Adding en-US and en-GB with identical content creates work without benefit.

URL Structure Considerations

How you organize regional English URLs is a separate decision from hreflang, but it affects maintenance complexity.

Subdirectories (/en-us/, /en-gb/) are the most common and easiest to manage. They keep everything on one domain and work well with most CMS platforms.

Subdomains (us.example.com, uk.example.com) offer more separation but require separate hosting configurations and can dilute domain authority.

Country-code top-level domains (example.com, example.co.uk, example.com.au) provide the strongest regional signal but are the most expensive and complex to manage. For a full comparison, see our guide on ccTLD vs. subdomain vs. subdirectory.

Whichever structure you choose, be consistent. If your US English pages are at /en-us/page/, your UK English pages should be at /en-gb/page/, not uk.example.com/page/.

Summary

For most sites, English hreflang is straightforward. Use en if you have one English version. Add regional codes (en-US, en-GB, en-CA, en-AU) only when your content genuinely differs by region in pricing, legal terms, or localized references. Always include self-referencing tags and return links. And do not use en-UK -- the correct code is en-GB.