Insights / Threads
Open Graph for multilingual pages: how to configure it
Open Graph for multilingual pages should be configured for each language version. Every URL needs its own title, description, image, locale, and og:url to avoid mixed previews when the page is shared on social networks, messaging apps, or internal tools.
Open Graph for multilingual pages should be configured by URL
Open Graph for multilingual pages should not be solved with a single block of metadata shared across the whole website. Each language version has a different URL, a different intent, and often text adapted to a different audience.
The practical rule is simple: each URL should declare its own Open Graph metadata. If you are on the English version, the title, description, image, and Open Graph canonical URL should correspond to that version. The same applies to Spanish, German, or any other language.
When this is not handled properly, strange previews appear: a Spanish page shared with an English title, an image with the wrong copy, or a URL that sends people to another version. It may seem small, but it communicates disorder in seconds.
What Open Graph metatags a multilingual page needs
A multilingual page should include at least og:title, og:description, og:url, og:image, og:type, and og:locale. For editorial content, it can also make sense to add complementary data depending on the page type.
The key is that those values should not be poorly pasted automatic translations. og:title should work as a shareable title in that language. og:description should summarize the piece properly. And og:url should point to the exact URL for that version, not to the home page or another language.
It is also worth making sure the image is designed for that page. If you use an Open Graph image with text, that text should be localized. If the image has no text, you can reuse it more safely.
How to use og:locale on multilingual pages
og:locale indicates the language and region of the page. For example, a Spanish page for Spain can use es_ES, while a US English version can use en_US.
There is also og:locale:alternate, which allows you to declare other available locales. It can be useful, but it should not be overvalued. It does not fix a confusing multilingual architecture by itself, nor does it replace tags designed for search engines.
Our recommendation is to use og:locale consistently and support it with a clear URL structure. If the website has /es/ and /en/, each route should publish the corresponding locale and point to itself with og:url.
Multilingual Open Graph does not replace hreflang
Open Graph and hreflang solve different problems. Open Graph defines how a page appears when shared. Hreflang helps search engines understand which language or regional versions exist for the same page.
That is why a serious multilingual website should take care of both layers. You can have perfect Open Graph and poorly configured hreflang, or the other way around. In both cases, something breaks: either the social preview or the SEO interpretation of the versions.
The orderly way to see it is this: hreflang guides search engines; Open Graph guides social and messaging platforms. They do not compete. They complement each other.
Common mistakes in multilingual Open Graph
The most common mistake is copying the same metatags across every language. This often happens when the CMS generates Open Graph from a global configuration instead of from each page’s localized content.
We also see incorrect URLs, untranslated images, overly generic descriptions, badly written locales, and pages that declare one version as og:url while being shared from another. Each of these small inconsistencies reduces trust.
Another frequent issue is forgetting to test previews after publishing. Many platforms cache the preview, so correcting a metatag is not always visible immediately. You need to validate and, when necessary, force a refresh with their debugging tools.
How to review Open Graph on a multilingual website
The review should start with a sample of real pages: home, services, articles, landing pages, and key pages in each language. For each one, check that title, description, URL, image, and locale match the version you are viewing.
Then review consistency with canonical, hreflang, and route structure. Not because Open Graph depends directly on all of that, but because a multilingual website needs its signals not to contradict one another.
Finally, test previews on real platforms or debugging tools. One thing is for the HTML to look correct, and another for LinkedIn, WhatsApp, Slack, or Facebook to render it as expected. In Open Graph, the visible result matters a lot.
Frequently Asked Questions
Each language version should have its own Open Graph metadata: og:title, og:description, og:url, og:image, and og:locale. The important thing is that the Spanish page does not show English previews, and that the English version does not pull text or URLs from another language.
The most specific tag is og:locale. It indicates the page language and region, for example en_US or es_ES. You can also use og:locale:alternate to declare other available languages, although it does not replace a clear URL structure or hreflang.
No. Open Graph controls how a page appears when shared on social or messaging platforms. Hreflang helps search engines understand alternative language versions. They are different layers, and both should be configured correctly.
Not always, but it is usually recommended if the image includes text. If the visual piece has copy in English, the French page should use a French version. If the image is purely visual or brand-based, it can be reused more easily.
The most common mistake is reusing the same metadata across all languages. That creates mixed previews: titles in one language, descriptions in another, incorrect URLs, or images that do not match the shared version.
To dig deeper into this topic
