Language Codes vs Region Codes: What's the Difference?

You've seen codes like en, en-US, and en-GB scattered across hreflang tags, CMS language settings, and URL folders, and they all look close enough to be interchangeable. They're not. Two different standards are quietly stacked on top of each other here, and mixing them up is one of the most common — and most invisible — mistakes in international SEO.

Get this wrong and nothing crashes. There's no error message. Your site just quietly serves the wrong version of a page to the wrong audience, or search engines ignore your targeting entirely because the code you used doesn't exist.

What are language codes and region codes?

These are two unrelated classification systems that happen to get combined constantly on the web, which is exactly why they're so easy to confuse.

• Language codes come from ISO 639-1, a two-letter standard where en means English, fr means French, and ja means Japanese — regardless of where the reader lives.
• Region codes come from ISO 3166-1, a separate two-letter standard where US means United States, GB means United Kingdom, and BR means Brazil — regardless of what language is spoken there.
• A locale code joins the two with a hyphen, in the format language-REGION, like en-US or es-MX, to describe both the language and the regional variant in one tag.
• They aren't interchangeable. A region code alone (US) doesn't tell you the language, and a language code alone (en) doesn't tell you the country — you need both when the distinction actually affects your content.

The practical takeaway: whenever you see a two-letter code, check whether it's describing a language, a place, or both stitched together — they're never the same thing wearing a different label.

Why the distinction matters for your site

This isn't a pedantic naming issue. Getting it right — or wrong — has direct, measurable effects on how your site performs internationally:

• Correct hreflang targeting. Search engines use language and region codes to decide which page version to show a searcher — an invalid or mismatched code means that targeting silently fails.
• Avoiding duplicate content confusion. Serving the same English content to the US, UK, and Australia under one generic en tag can look like duplication when it's actually deliberate, but only if the codes are structured consistently.
• Accurate formatting. Region codes drive date formats, currency symbols, and number formatting — en-US and en-GB disagree on both the date and the spelling of "colour," despite sharing a language code.
• Real audience segmentation. A region code lets you serve different pricing, shipping, or legal text to different countries without needing a different language at all.

Step-by-step: choosing the right codes

1. Identify the language the content is actually written in. Not the language you assume your audience speaks — the actual language of the words on the page.
2. Decide whether region matters. If the content is identical for every country that speaks that language, you may only need a language code, like en, with no region attached.
3. Identify the specific region, if it does matter. Use the two-letter ISO 3166-1 country code, not a colloquial abbreviation — GB, not UK; KR, not Korea.
4. Combine them into a locale code. Format it as language-REGION in lowercase-uppercase, such as en-US, fr-CA, or pt-BR.
5. Apply it consistently across the site. Use the same code in the html lang attribute, hreflang tags, and any URL structure or CMS locale setting for that page.
6. Add an x-default, if relevant. If you have a fallback page for visitors who don't match any specific language-region pair, mark it with x-default in your hreflang set.
7. Validate the final set. Check that every code used actually exists in the ISO standards and that no two tags accidentally point to the same combination.

Common mistakes with language and region codes

1. Using "UK" instead of "GB"

UK is the everyday abbreviation everyone uses in conversation, but it isn't a valid ISO 3166-1 region code. The correct code for the United Kingdom is GB, and using UK in an hreflang or locale attribute can cause it to be ignored.

2. Treating a region code as if it implies a language

BR means Brazil, not "Portuguese." A code like BR on its own says nothing about language — it needs to be paired with pt to mean Brazilian Portuguese specifically.

3. Mismatching language and region without meaning to

A code like en-FR is syntactically valid and means "English content for visitors in France," which is rarely the intended target — this kind of typo is easy to make and easy to miss.

4. Using one generic code when regional differences actually exist

Publishing US-specific pricing or spelling under a bare en tag, with no region distinction, can send the wrong version to UK or Australian visitors who search engines assumed were covered by the same generic tag.

Real-world examples

How the same language splits into different locale codes depending on the region it's targeting:

In each case, the language code alone would have left out a distinction that genuinely matters to the reader — the region code is doing real work, not just adding decoration.

Language codes vs region codes compared

A side-by-side look at what each standard actually covers, so it's clear which one to reach for.

Generate valid locale and hreflang codes right now — free

The Rebrixe Locale & Hreflang Code Generator checks your language and region choices against the ISO standards and outputs ready-to-paste hreflang tags and html lang attributes. No guessing whether "UK" or "GB" is correct — just pick from a validated list.

Frequently asked questions