Separate en-GB and en-US versions are justified when the content differs in substance for each market, not merely in spelling. If prices, delivery, returns, currency, legal terms or offers genuinely differ, distinct URLs with reciprocal hreflang annotations help Google show the right version. If the content is effectively identical, one English page is usually simpler and safer.
What do en-GB and en-US mean in hreflang?
Hreflang uses language and, optionally, region codes. en means English; en-GB means English for the United Kingdom; en-US means English for the United States. The region is not a language. British and American English are the same language, so the distinction is about locale targeting, not translation.
Google's documentation on localized versions lists a relevant scenario: English-language content targeted to the US, GB and Ireland. That is a multi-regional case, not a multilingual one. Google's guide to managing multi-regional and multilingual sites explains that a multi-regional site explicitly targets users in different countries, while a multilingual site offers content in more than one language.
So the question is not whether you can add en-GB and en-US. You can. The question is whether the two pages actually serve different needs.
When are distinct en-GB and en-US versions justified?
Distinct versions are justified when a reader in one market would reasonably expect different information from a reader in the other. The clearest signals are commercial and operational:
- Pricing and currency. A page showing GBP prices with UK VAT treatment is not the same offer as a page showing USD prices with US sales tax handled at checkout. Currency and tax presentation differ, and confusing them creates a poor experience.
- Delivery and returns. Delivery times, carriers, return windows and return addresses often differ by country. A UK reader needs UK delivery terms; a US reader needs US terms.
- Legal and regulatory text. Consumer rights, warranty wording and privacy notices can differ. These are not cosmetic differences.
- Offers and promotions. A promotion available in one market may not be available in another.
- Assortment. Some products may be sold only in one country.
If none of these differ, separate pages often create more risk than value. Two near-identical English pages can compete with each other, and maintaining them doubles the work.
A useful test: open both pages side by side and ask whether a reader would notice the difference without being told. If the only changes are color versus colour and a swapped date format, that is not a substantive difference.
What about spelling and vocabulary differences?
Spelling alone rarely justifies separate URLs. Google's systems can understand that color and colour refer to the same concept. The same applies to organize and organise, or tire and tyre in context.
Vocabulary can matter more when it affects search behaviour. A UK reader may search for trainers while a US reader searches for sneakers. If your category page uses only one term, you may miss queries in the other market. But that is an argument for including both terms naturally on a shared page, or for genuinely localized content, not automatically for two URLs.
The decision should rest on whether the page's substance changes. If it does not, one well-written English page that serves both markets is usually the better choice.
How should hreflang be implemented?
Google supports several different methods for labeling language or region variants of a page, including hreflang annotations and sitemaps.
Pick one method. For most sites, HTML link elements in the head of each page are the simplest to audit.
Each page must reference itself and every alternate, including the return link. A common mistake is a one-way annotation: the en-GB page points to en-US, but en-US does not point back. Google's documentation states that if two pages don't both point to each other, the tags will be ignored.
A minimal example, using hypothetical URLs:
<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="x-default" href="https://example.com/product" />
This is illustrative only. The x-default value can be used for a fallback page for users whose language or region is not matched.
Should you use a fallback page?
A fallback is useful when you have markets beyond the UK and US, or when you want a neutral English page for users whose locale is not matched. The x-default annotation is designed for that purpose.
Do not use x-default as a substitute for a proper en-GB or en-US page. It is a fallback, not a targeting signal for a specific country.
If you only serve the UK and US and the content genuinely differs, you may not need a fallback at all. If you serve many English-speaking markets, a neutral page can reduce the number of near-duplicates.
What about Shopify and other platforms?
Shopify and similar platforms often provide built-in language and market features. These can generate URLs and annotations automatically, but the output still needs checking. Platform defaults may create market-specific URLs even when the content is identical, or may not include reciprocal hreflang links.
A practical verification method: after enabling a market or language, inspect the rendered HTML of both versions. Confirm that each page contains a self-referencing hreflang and a link to the other version. Then check whether the content actually differs. If it does not, consider consolidating.
Do not assume that a platform's market feature is equivalent to a justified localization. The feature creates the structure; you still decide whether the content warrants it.
How do you verify the setup?
A simple audit process:
- List every English URL that targets the UK or US.
- For each, check that the hreflang annotations are reciprocal.
- Confirm that the region codes are valid:
en-GBanden-US, noten-UK. - Check that the canonical URL on each page points to itself, not to the other market's version.
- Compare the content of paired pages. If the differences are only cosmetic, consider merging.
- Inspect how Google has indexed each version.
A common error is using en-UK. The correct ISO 3166-1 alpha-2 code for the United Kingdom is GB. Google's documentation uses en-GB.
What are the risks of splitting when you should not?
Splitting identical English content across two URLs can create several problems. The pages may compete for the same queries. Internal links may become inconsistent. Maintenance doubles. And if the annotations are wrong, Google may show the wrong version to users.
Google's documentation notes that localized versions of a page are only considered duplicates if the main content of the page remains untranslated.
The safer default is one English page unless there is a real reason to split. The reason should be visible to a reader, not just to a spreadsheet.
Frequently asked follow-up questions
Can I use en-GB and en-US on the same page?
No. Each URL should have one primary hreflang target. A single page should not be declared as both the en-GB and en-US version. If you want one page to serve both, use en without a region; x-default is intended as a fallback for unmatched languages or regions.
Do I need separate pages for spelling differences alone?
Usually not. Spelling differences such as color and colour may not change the substance of the page. Separate pages are better reserved for differences in price, delivery, returns, legal terms, offers or assortment.
What to do next
Start with a content comparison, not a technical one. If the UK and US pages differ in what they promise, distinct URLs with reciprocal hreflang are justified. If they do not, consolidate. The technical setup is straightforward once the content decision is clear. For related operational questions, see our articles on free-shipping thresholds and click and collect, which often drive exactly the kind of market-specific differences that justify separate pages.