I sell in both Saudi Arabia and the UAE. Should I choose ar_SA or ar_AE as the page locale (og:locale)?
og:locale describes the language of the text on the page and its regional flavour; it has nothing to do with the countries you ship to. Pick the value closest to how the page is written, or leave it on 'Not specified', since it is optional. The builder writes only one locale per page.
What og:locale actually describes
The value has two parts, a language code and a region code, so ar_SA means Arabic as written in Saudi Arabia. It is a fact about the text itself, read by whatever displays the share card. It is not a country targeting setting, and it will not make your page appear more to customers in the UAE.
A store that sells in both countries from one Arabic page does not need two values. The oud oil page reads the same in Riyadh as in Dubai, so choose what describes your writing: Saudi phrasing and prices in riyals point to ar_SA, a store rooted in the Emirates points to ar_AE. If you are unsure, the difference here is small.
What the tool writes either way
In the Arabic interface the menu starts on 'Arabic, Saudi Arabia (ar_SA)', and in the English one on 'English, United States (en_US)'. With ar_SA chosen, one extra line appears in the output:
<meta property="og:locale" content="ar_SA">
When we picked 'Not specified' from the same menu, that line vanished from the output and every other tag stayed the same. No warning and no error, because og:locale is not one of the four required properties.
The menu lists eight choices: Not specified, Arabic for Saudi Arabia, the UAE, Egypt, Kuwait and Qatar, and English for the United States and the United Kingdom. You can choose only one.
What if your store has an English version?
The English version is a different page with a different URL, so it gets its own tags. Build a separate set for it in the tool, choose en_US or en_GB depending on how it is written, and paste it into the head of the English page only. Never put the Arabic page's tags on the English page, or the other way round.
- Open the Open Graph metadata builder for the Arabic page and choose the Arabic locale closest to your style.
- Copy the tags into the Arabic page head.
- Fill the form again for the English page with its own URL and title, and choose en_US or en_GB.
- Copy the second set into the English page head.
What this tag does not do
og:locale does not change the currency of your prices, redirect visitors to their country's version, or promise anything about search visibility. Each platform decides whether and how to use it. If you care how the page appears in search results, check its title and description in the Search snippet preview and read the search engine's documentation on multilingual pages.
Common questions
Can I write just ar without a region?
The tool's menu has no language-only value. Pick the closest one, or Not specified.
Is leaving og:locale empty a problem?
It is optional, and the tool gives no warning when it is absent.
Do I need one value per country I ship to?
No. The value describes the language of the page text, not your delivery area.
