OpenGraphDebug
← All posts

Open Graph Locale

A guide to the Open Graph locale and how it works.

•Dmytro Krasun
Open Graph

Open Graph locale tells social platforms what language and region your content is written for. If your site is multilingual or serves users in different countries, this tag matters more than most people think.

What Is Open Graph Locale?

The Open Graph locale is defined with this meta tag:

<meta property="og:locale" content="en_US" />

It tells platforms which language + regional variant your page uses.

The format is always:

language_COUNTRY

Examples:

  • en_US → English (United States)
  • en_GB → English (United Kingdom)
  • fr_FR → French (France)
  • de_DE → German (Germany)

Why Open Graph Locale Matters

Open Graph was introduced by Facebook, but many platforms follow the same rules.

Locale helps platforms:

  • Display the correct language version
  • Choose the right regional formatting
  • Understand international content relationships

If you ignore locale, platforms guess. Guessing fails often.

When You Should Use og:locale

You should explicitly set og:locale if:

  • Your site is not English
  • Your site supports multiple languages
  • You serve different countries with the same language
  • You want predictable previews across regions

If your site is English-only and US-focused, the default (en_US) usually works even if omitted.

Using og:locale:alternate (Multilingual Sites)

For multilingual websites, you should list all language versions of the page.

Example:

<meta property="og:locale" content="en_US" />
<meta property="og:locale:alternate" content="fr_FR" />
<meta property="og:locale:alternate" content="de_DE" />

This tells platforms:

  • Which locale is primary
  • Which alternatives exist

This is especially important for international brands and global SEO.

Common Open Graph Locale Mistakes

  1. Using invalid formats

    ❌ en-us ❌ en ✅ en_US

  2. Forgetting alternates Platforms may show the wrong language in some regions.

  3. Mismatch with page content Locale should match the actual language of the page, not the user.

  4. Confusing locale with hreflang

    • og:locale → social platforms
    • hreflang → search engines They solve different problems.

Does Open Graph Locale Affect SEO?

Not directly.

Search engines don’t use og:locale as a ranking signal. That job belongs to:

  • hreflang
  • Content language
  • Page structure

But locale does affect social distribution, click-through rate, and perceived relevance, which indirectly helps marketing outcomes.

Minimal Best-Practice Setup

Single-language site:

<meta property="og:locale" content="en_US" />

Multilingual site:

<meta property="og:locale" content="en_US" />
<meta property="og:locale:alternate" content="es_ES" />
<meta property="og:locale:alternate" content="fr_FR" />

That’s enough for correct behavior on most platforms.

Final Takeaway

Open Graph locale is small metadata with global consequences.

If your audience spans languages or regions, skipping it is lazy. Set it once, align it with your content, and your previews stay correct everywhere.