Hreflang for English in England and the United Kingdom

Written by

in

Use en-GB for English content intended for the United Kingdom. There is no supported England-only region value in hreflang. If your page serves English speakers generally, without a particular country audience, use en instead.

The distinction matters when a website has separate regional versions. A UK pricing page and a US pricing page may use the same language while offering different currencies, delivery terms or services.

Choose the code that matches the audience

Value

Meaning

Typical use

en

English without a specified region

A general English resource

en-GB

English targeted to the United Kingdom

A UK storefront or service page

en-US

English targeted to the United States

A US storefront or service page

The first component is the language; the second, when present, identifies a region. GB is the supported UK region code for this purpose. Avoid en-UK, uk as a UK-English label, and a country code on its own. In language coding, uk identifies Ukrainian, not English for the UK.

An en-GB annotation does not prevent visitors elsewhere from opening the page. It describes the intended audience; it is not an access restriction or a redirect.

Connect UK and US versions with a complete example

Imagine a company with market-specific delivery information:

· UK: https://example.com/uk/delivery/

· US: https://example.com/us/delivery/

Add this alternate set to the <head> of each version:

<link rel="alternate" hreflang="en-GB"

href="https://example.com/uk/delivery/">

<link rel="alternate" hreflang="en-US"

href="https://example.com/us/delivery/">

The /uk/ and /us/ folders are an example URL design. A folder's spelling does not determine the hreflang value: a site may use /uk/ in its address and still correctly use en-GB in the annotation.

These pages should explain the same type of delivery information for their respective markets. Do not pair the UK delivery page with the US homepage or a different product page.

Decide whether a generic English entry helps

If you already have a general English version, an en entry can identify that option for English speakers outside your named regions. For example, a general delivery overview could be included alongside the UK and US pages if it is a suitable equivalent.

You do not need to create an artificial third page just to add en. The same suitable URL can be associated with a regional code and a generic English code. Choose the visitor experience first, then label it accurately.

The generic English entry also serves a different purpose from x-default: en identifies an English alternative, while x-default identifies a fallback for unmatched language or regional settings.

Review the implementation for regional mistakes

Check the mapping, not just the syntax. A valid en-GB value is still unhelpful if its URL leads to US pricing. Open each destination and confirm that the currency, availability and delivery information match the audience described.

For distinct localized pages intended for separate indexing, check that canonical signals support those URLs. If the regional pages are substantially identical, review the duplicate-content decision before assuming that adding tags makes separate indexing appropriate.

Use the hreflang generator to format your selected values and URLs, then compare the result with Google's language and region guidance. The final check is simple: en-GB must identify the UK version, en-US the US version, and both pages must describe the relationship consistently.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *