Open Graph tags: what Google uses and what to keep current

Open Graph tags set the title, image and text a shared link shows, and Google Search lists og:title and og:image among its own sources too. They are not where Merchant Center gets your prices; that is your product data and your structured data. Keep them current anyway. A preview showing last season’s price is a small untruth with your shop’s name on it.

Minor4 min read

By Edvinas Ivanauskas How the guides are reviewed

Why this matters

Google documents two uses. Its “Influencing title links” page says “Google Search uses the following sources to automatically determine title links:” and includes content in og:title among them, beside the title element and the page's main heading. Its “Image SEO best practices” page lists og:image as one of the metadata sources you can use to name your preferred image, and asks you to “Choose an image that's relevant and representative of the page.” and to avoid “using a generic image (for example, your site logo)”. A logo in og:image on every product page is the exact thing that page warns against.

Prices are a different story. Merchant Center's “About structured data markup for Merchant Center” page is written around schema.org markup: “You can use schema.org structured annotations to allow Google to reliably retrieve up-to-date information directly from your website.” Its rule for that markup is the one to copy for every tag on the page: “Structured data must match the values that are shown to the customer.” Open Graph price tags such as product:price:amount are covered in og:price and product:price, explained; the markup Merchant Center does use is in what your Product structured data needs.

Why keep the tags right when Merchant Center's structured data help never mentions them? Because shoppers see them. A link shared in a chat, a post or a newsletter shows the og:title, og:image and, on some platforms, a price, and the shopper clicks expecting what the preview promised. If the page then shows a different product photo or a higher price, the first thing your shop did was get a detail wrong. Hidden tags drift because nobody sees them; that is the whole problem, and the whole fix is generating them from the same fields as the page.

The free scan covers the structured-data side of that set: it reports a markup price or stock status that contradicts the visible page as a failure. The Open Graph tags are yours to check, with the steps below. The complete set of page checks is on the misrepresentation checker.

Typical evidence

The price nobody can see is the one that rots

OpenGraph tags live in the head, not on the screen, so when a price changes the customer-facing page can be updated while the og: tags are forgotten. A week later the page can charge one price and a shared link preview another. Verify the public tag with a dedicated debugger.

yourdomain.com

Merino Wool Crew — Charcoal

£24.99 · from og:price

page <head> — stale

<meta property="og:price:amount" content="24.99">

<meta property="og:availability" content="instock">

The page now charges £34.99 — the og: tag has lagged ten days because it was stamped in once at creation. Generate og:price and og:availability from live fields; confirm with Facebook's Sharing Debugger.

The public signals this check looks for:

og
og:image is the shop logo on every product page, so every shared link shows the same logo.
og
og:title is the shop name, not the product name.
A product…
A product:price:amount tag was set when the product launched and never updated, so previews show an old price.
og
og:description still carries template text or copy from before the product was rewritten.
og
og:url points at an old address, a variant, or a staging domain.
The theme and an SEO app both print Open Graph tags, and the two sets disagree
The theme and an SEO app both print Open Graph tags, and the two sets disagree.

What it looks like once it is right

The theme fills og:title with the product name, og:image with the main product photo and the price tags from the live price field. A shared link shows the candle, its name and £18.00: the same as the page and its structured data.

Common mistakes

Common mistake

A candle shop’s product page shows £18.00. Its og:title is the shop name, its og:image is the logo, and its product:price:amount still says 22.00 from launch day. Every shared link shows a logo, no product name and a price the shop dropped months ago.

Fix checklist

Open a product page with view-source and search for “og:” and “product:price”. List og:title, og:description, og:image, og:url and any price tags, and compare each one with what the page shows.
Set og:title to the product name and og:url to the product's own address, the same one you send as its link to Merchant Center.
Set og:image to the main product photo, not the logo. Google's image guidance asks for an image that is relevant and representative of the page.
Generate any price and availability tags from the live product fields, or remove them. A missing price tag costs you little; a wrong one advertises a price you no longer charge.
If the theme and an app both print tags, switch one off so each page carries one set.
Paste the product URL into the link-preview or sharing-debug tool of each platform your customers use, and ask it to fetch the page again after every change, because platforms cache previews.
After any price change, check that three things agree: the visible price, the structured data and any Open Graph price tag.

Read back the OpenGraph values a tool reports

Facebook’s Sharing Debugger fetches a page and shows the OpenGraph values it receives. After a price change, use it to verify the public tag moved; this is not evidence of Merchant Center behaviour.

Sharing Debugger · /products/merino-crewog:price stale

og:titleMerino Wool Crew — Charcoal

og:price:amount24.99 · page now 34.99

og:availabilityinstock

last scraped10 days ago

Generate og:price and og:availability from live fields so they can't lag. Hardcoded OpenGraph values are the ones that rot, because nobody can see them rotting.

Questions merchants ask

Does Google use Open Graph tags?

For some things. Google's title link documentation lists og:title among the sources Google Search uses to generate title links, and its image documentation lists og:image as one way to name your preferred image. For product prices, Merchant Center works from your product data and schema.org structured data.

Do I need og:price or product:price tags for Google Shopping?

Merchant Center's structured data help is written around schema.org markup, and your listing prices come from the [price] in the product data you submit, with that markup as the backstop for automatic item updates. If you keep Open Graph price tags for social previews, generate them from the live price so they never disagree with the page.

Why does my shared link still show the old image or price?

Platforms cache link previews. Fix the tags on the page first, then use the platform's preview or sharing-debug tool to fetch the page again. If the preview is still wrong, view the page source: a second set of tags from an app is the usual cause.

Remediation

Risk signal

A link preview is a promise made before the click, and the page has to keep it. Put the page, its structured data and its Open Graph tags on one source of truth, check the tags after every price change, and run the free scan to check the markup half.

PriorityLow priority on its own — clear it as housekeeping so the record is complete.

EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

Last reviewed 23 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.