Give every localized page its own Open Graph metadata in its rendered HTML head. Set og:image to an absolute URL for an image that represents that locale, and set og:url to that page’s canonical object URL. Use hreflang separately to identify language and regional variants for Google Search: it does not choose or override the image shown in social previews.
Set Open Graph metadata separately on each localized URL
The Open Graph Protocol defines og:title, og:type, og:image, and og:url as its four required properties. og:image identifies an image representing the page; og:url identifies the canonical URL of that object. og:locale describes the locale of the Open Graph tags, while og:locale:alternate can list other locales where the page is available. Open Graph Protocol
As an Amazon Associate I earn from qualifying purchases.
For each language or regional URL, render a matching title, canonical object URL, image, and locale value. The following English and French heads illustrate the pattern; they are examples, not observed implementations.
English page
<html prefix="og: https://ogp.me/ns#">
<head>
<meta property="og:title" content="How to prune roses" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://example.com/en/article" />
<meta property="og:image" content="https://example.com/images/rose-pruning-en.jpg" />
<meta property="og:image:alt" content="A gardener pruning a rose bush" />
<meta property="og:locale" content="en_US" />
<meta property="og:locale:alternate" content="fr_FR" />
<link rel="alternate" hreflang="en" href="https://example.com/en/article" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/article" />
</head>
</html>French page
<html prefix="og: https://ogp.me/ns#">
<head>
<meta property="og:title" content="Tailler les rosiers" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://example.com/fr/article" />
<meta property="og:image" content="https://example.com/images/taille-rosier-fr.jpg" />
<meta property="og:image:alt" content="Une personne taille un rosier" />
<meta property="og:locale" content="fr_FR" />
<meta property="og:locale:alternate" content="en_US" />
<link rel="alternate" hreflang="en" href="https://example.com/en/article" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/article" />
</head>
</html>The image can be shared between locales when it remains accurate and appropriate for each audience. Use separate images when embedded text, product details, imagery, or cultural context differs. Localize the title and description too when the page’s representation changes.
Keep hreflang distinct from Open Graph locale
hreflang tells Google Search about language or regional page variants; Open Graph metadata describes a page as an object for social sharing. Google’s documentation does not describe hreflang as a mechanism for selecting og:image. Maintain and validate these as separate metadata systems. Google Search Central: Localized Versions of your Pages
Google Search Central says: “Use hreflang to tell Google about the variations of your content, so that we can understand that these pages are localized variations of the same content.”
HTML hreflang requirements
- On every variant, include a link to itself and links to all the other variants, using fully qualified URLs.
- Keep the same variant set across the pages and make links reciprocal. Google warns that missing return links can cause annotations to be ignored or interpreted incorrectly.
- Use a language code, optionally followed by a region code. A region without a language is not valid.
- Use
x-defaultfor a fallback page when useful, such as a language selector for visitors whose language does not match a listed variant.
Choose one maintainable delivery method
Google supports hreflang declarations in HTML, HTTP response headers, or XML sitemaps and treats these methods as equivalent for Search. You do not need to maintain all three simultaneously. Choose the method your team can keep accurate and reciprocal. Google Search Central: Localized Versions of your Pages
Recommended Free Tools
Google recommends distinct URLs for language versions. Cookie- or browser-dependent language delivery can prevent Google from discovering and crawling each variation; avoid automatic redirects that block access to other versions, and provide links that let visitors switch languages. Visible page content matters to Google’s language determination: a URL folder, hreflang, or an HTML lang value alone does not establish the page language. Google Search Central: Managing Multi-Regional and Multilingual Sites
Choose an image that represents the localized page
Google says image-preview selection is automated and may use multiple sources. Providing image metadata such as og:image can influence the selection, but does not guarantee that a platform will display that exact image. Google recommends a relevant, representative image, avoiding generic logos and extreme aspect ratios, and using high resolution where possible. Its guidance does not establish one universal image dimension for every social platform. Google Search Central: Image SEO Best Practices
The Open Graph Protocol documents optional image properties: og:image:secure_url, og:image:type, og:image:width, og:image:height, and og:image:alt. If you specify og:image, the protocol says to also specify og:image:alt. Write alt text as a description of the image, not as a caption. Open Graph Protocol
Rank #4
Inspect and troubleshoot each rendered variant
- Open each localized URL and inspect its rendered HTML head. Confirm that its title,
og:url,og:image, andog:localematch that page rather than another locale. - Check that
og:imageis an absolute image URL and thatog:image:altdescribes the image. Confirm that each localized image is appropriate for its page, or deliberately reuse an image that suits all variants. - Compare the hreflang sets across variants: each page should include itself and the other fully qualified URLs, and links should be reciprocal.
- Use the relevant social platform’s current preview or debugging tool to check how it interprets the page. A declared image does not guarantee a particular platform preview.
If the wrong social image appears
Check the rendered page head for a stale, shared, or locale-mismatched og:image. Confirm that the page’s metadata is available on the localized URL and that the image itself represents that version. Then inspect the URL with the relevant platform’s current preview/debugging tool; image selection and display are platform-controlled.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If localized variants are not associated in Search
Check that all variants list the same set, each includes itself, URLs are fully qualified, and links point back to one another. Verify language and region code formatting. If language delivery depends on cookies or automatic redirects, ensure that the other locale URLs remain directly accessible and discoverable.
Best Value
Or skip the browser setup
If you need to inspect the rendered head or capture a preview while checking localized pages, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a screenshot or PDF; consult the ScreenshotNeo documentation for parameters and response details.
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/fr/article -o shot.webpScreenshotNeo removes supported cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, failed loads, and cache hits are not billed. Its MCP server lets AI agents use screenshot tools. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. These captures can help inspect a page, but do not replace checking its actual metadata or using a social platform’s preview tool. Sign up for 1,000 free screenshots a month, no card required.
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.
