Give every localized URL its own Open Graph metadata: set og:locale to that page’s locale, and repeat og:locale:alternate for the other locales available for that page. Use separate, reciprocal hreflang annotations to connect the localized URLs for Google Search; Open Graph locale tags do not do that job.
Add Open Graph metadata to each localized page
Place Open Graph tags in the document’s <head>. The protocol identifies four required properties for each graph object: og:title, og:type, og:image, and og:url. For a localized page, use values that describe and identify that specific version, then set its locale. The Open Graph protocol uses a language and territory separated by an underscore, such as en_GB. Its stated default is en_US; explicitly declaring the page’s actual locale avoids relying on that default. See the Open Graph protocol.
As an Amazon Associate I earn from qualifying purchases.
For example, the English page below is also available in French and Spanish:
<html prefix="og: https://ogp.me/ns#">
<head>
<title>Example page</title>
<meta property="og:title" content="Example page" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://example.com/en/page" />
<meta property="og:image" content="https://example.com/images/page.jpg" />
<meta property="og:locale" content="en_GB" />
<meta property="og:locale:alternate" content="fr_FR" />
<meta property="og:locale:alternate" content="es_ES" />
</head>
</html>On the French URL, change the title, URL, image and other page-specific metadata to match its content, set og:locale to fr_FR, and list the other available locales as alternates. Do the equivalent for every localized URL. An alternate locale says that the page is available in that locale; it does not provide the URL of that alternate page.
#1 Best Overall
Open Graph array values are expressed as repeated meta elements. If consumers encounter conflicting values, the protocol says the first value is preferred. For an image, it also specifies structured properties such as secure URL, MIME type, width, height and alternative text. When you specify og:image, include og:image:alt to describe the image rather than supply a caption. See the Open Graph structured properties.
Use hreflang separately to connect localized URLs
og:locale and og:locale:alternate label the current page’s locale and other available locales in Open Graph metadata. Google’s hreflang annotations instead associate the actual alternate URLs for Search. Adding Open Graph locales alone does not tell Google which URLs are the language or regional variants.
Rank #2
Google recommends distinct URLs for different language versions. In the HTML head, put a complete set of alternate links on every variant, including a link to itself. Use the same set across variants and make sure the pages link back to one another. For corresponding English and French URLs, with a language-selection fallback:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
<link rel="alternate" hreflang="en-GB" href="https://example.com/en/page" />
<link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/language/page" />x-default can identify the fallback for users whose language or region is not explicitly covered. Google describes it as particularly suited to a language selector or another default page. Hreflang can also be delivered in a sitemap or HTTP headers; headers can be useful for resources such as PDFs. See Google’s guidance on localized versions of your pages.
Rank #3
- Provides quick, reliable answers to your questions about words
- Economically priced to fit your budget
- Makes a great gift for new high school or college graduates
Keep the two locale formats distinct
Open Graph examples use an underscore between language and territory, such as en_GB. Google’s hreflang syntax uses a hyphen, such as en-GB: an ISO 639-1 language code may be followed by an ISO 3166-1 Alpha 2 region code. A region by itself is not valid. Do not copy one format into the other.
Keep the page language accessible to users and crawlers
Google says it determines page language from visible content, not from the lang attribute or the URL. Make the main content and navigation on each page clearly reflect its primary language. Google also advises against automatically redirecting users between locales based on inferred language: that can make variants inaccessible to users or crawlers. Provide links that let visitors switch languages instead. Read Google’s guidance on managing multi-regional and multilingual sites.
For regional pages written in the same language, canonicalization may matter alongside hreflang. Google describes the canonical URL as a hint, not a binding instruction, and says canonicalization used together with hreflang can help it understand which regional URL to show. See What is URL canonicalization.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Review the localized metadata before publishing
- Open each locale URL and confirm it is reachable and its Open Graph title, URL, image and locale describe that version.
- Check that every listed alternate locale is actually available for that page.
- Check that hreflang codes use valid language and optional region codes, with hyphens rather than Open Graph’s underscores.
- Confirm that every variant includes itself in the hreflang set and links back to the other variants.
- Make sure
x-default, if used, points to the intended fallback. - Verify that visitors can switch languages without relying on an automatic locale redirect.
Or skip the browser setup
If you need screenshots of localized pages to review their rendered appearance, ScreenshotNeo provides a screenshot API and MCP server. One GET request returns an image or PDF; here is a cURL example for the English page:
Quick Recap
Best Value
- Designed for student use anywhere
- Hands-on learning resource any time you need to reference a word
- Makes a great gift for new high school or college graduates
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/en/page -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups and chat widgets are removed before capture; bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for free.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
