Open Graph tags were created by Facebook, but Google reads them too — and in ways that directly affect how your pages appear in Search, Google Discover, and link previews across Google products. Understanding what Googlebot does with your OG metadata is essential for any SEO-conscious developer.

Does Google Use Open Graph Tags?

Yes, but not exclusively. Google uses a combination of sources to determine the title, description, and image for a search result: the HTML <title> tag, og:title, the on-page heading structure, og:description, the meta description, og:image, and structured data (schema.org). Open Graph tags are one signal among many — not the only one, and not always the most important one.

TipGoogle may override your og:title with a different title if it determines the OG title is misleading, keyword-stuffed, or less representative of the page than the on-page h1. For the best results, keep your og:title, title tag, and h1 consistent.

How Googlebot Crawls Your Page

Googlebot renders pages using a full headless browser (Chromium), which means it executes JavaScript. This distinguishes it from most social media crawlers, which read only the raw HTML response. For Open Graph tags, however, Google still prefers tags present in the server-rendered HTML — tags injected by JavaScript after load may be indexed but are slower to be discovered and may not appear in all Google surfaces.

The practical implication: if you are using Next.js App Router's Metadata API or generateMetadata(), your OG tags are in the server-rendered HTML and Googlebot will read them reliably. If you are using a React SPA that sets meta tags via client-side JavaScript, there may be a crawl delay of days or weeks before Google indexes the correct metadata.

Google Search: Rich Results and Title Rewriting

Title tag vs og:title

Google primarily uses the HTML <title> tag for search result titles. It will consider og:title as an alternative if the title tag is absent or low quality. Google may also rewrite your title entirely based on the page's h1, anchor text pointing to the page, or breadcrumb structured data — regardless of what your title tag or og:title says.

meta description vs og:description

For the snippet shown under a search result, Google uses the meta description tag as the primary signal — og:description is a secondary fallback. Google also generates its own snippets dynamically based on the query, so even a well-written meta description may not appear verbatim in search results. That said, og:description is used by Google Discover (the personalized content feed on Android and iOS) and in Google Chat and Gmail link previews.

og:image and Google Discover

og:image has the most direct impact on Google Discover. Google Discover shows content as large image cards in the Google app and in Chrome on Android. The image used is primarily the og:image (or the first large image on the page). Google requires a minimum 1200px width image for full-width Discover cards — images under 1200px wide are shown as small thumbnails rather than full-width cards.

—Full-width Discover card: og:image must be at least 1200×630px
—To opt into large images for Discover: add max-image-preview:large in the robots meta tag
—Aspect ratio: 16:9 is preferred for Discover full-width cards
—Images must be publicly accessible — no auth required
—Google follows og:image:width and og:image:height hints to determine if the image qualifies

<!-- Required to enable large image preview in Google Discover -->
<meta name="robots" content="max-image-preview:large" />

<!-- OG tags for Google Discover full-width cards -->
<meta property="og:image" content="https://example.com/og-image.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

Google Chat, Gmail, and Google Meet Link Previews

When someone pastes a URL in Google Chat, Gmail, or Google Meet, Google generates a link preview using OG tags — specifically og:title, og:description, and og:image. This is similar to how Slack and Discord read OG tags for unfurling. The crawler user-agent is Googlebot for these surfaces.

—og:title — used as the preview card title
—og:description — shown as the card body text
—og:image — thumbnail shown with the link card
—og:url — canonical URL for deduplication
—og:site_name — shown as the source label

Googlebot User-Agents

Google operates multiple crawlers under different user-agents. The main ones you will encounter are:

—Googlebot/2.1 — the primary search crawler. Renders JavaScript.
—Googlebot-Image/1.0 — crawls images for Google Image Search. Does not render JavaScript.
—Google-InspectionTool/1.0 — the crawler used when you request a URL inspection in Google Search Console.
—APIs-Google (+https://developers.google.com/webmasters/APIs-Google.html) — used by some Google API surfaces.
—GoogleOther — a general-purpose crawler used by various Google products for link previews.

When simulating how Google sees your OG tags, use the Googlebot/2.1 user-agent. Most server-side OG tag validators (including OGProof) fetch with both the social crawler user-agents and Googlebot to show you what each sees.

Structured Data vs Open Graph: Which Should You Use?

For Google-specific use cases like rich results (article cards, product cards, review stars), schema.org structured data is more authoritative than OG tags. Google's rich results systems are designed around JSON-LD structured data, not OG tags. However, for Discover images and Google Chat/Gmail/Meet link previews, OG tags are the primary mechanism.

The practical answer: use both. OG tags serve the social media use case (all six major social platforms read them). Structured data serves the Google rich results use case. They complement each other rather than competing.

<!-- OG tags: serve social platforms AND Discover/Chat/Gmail -->
<meta property="og:title" content="Your Article Title" />
<meta property="og:description" content="A clear description under 150 characters." />
<meta property="og:image" content="https://example.com/og-image.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:type" content="article" />

<!-- Enable large image preview for Google Discover -->
<meta name="robots" content="max-image-preview:large" />

<!-- JSON-LD structured data: serves Google rich results -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "image": "https://example.com/og-image.jpg",
  "datePublished": "2026-06-19",
  "author": { "@type": "Person", "name": "Author Name" }
}
</script>

Google Image Search and og:image

Googlebot-Image crawls images for Google Image Search. It uses the og:image URL as a high-confidence signal that the image represents the page — meaning pages with og:image set are more likely to have their featured image indexed correctly in Google Image Search. Always include og:image:alt (or an alt attribute on the image element) to improve accessibility and image search ranking.

Open Graph Tags in Google Search Console

Google Search Console's URL Inspection tool shows you the rendered HTML that Googlebot sees, including your OG tags. Use it to verify that:

1.Your og:title, og:description, and og:image are present in the rendered HTML
2.og:image is an absolute HTTPS URL (relative URLs and HTTP images may not appear in Discover)
3.Your robots meta tag includes max-image-preview:large if you want full-width Discover cards
4.The page is indexed — only indexed pages appear in Discover

Recommended OG Tag Setup for Google

<!-- Consistent title across all surfaces -->
<title>Your Page Title — Under 60 Characters</title>
<meta property="og:title" content="Your Page Title — Under 60 Characters" />

<!-- Description: match meta description and og:description -->
<meta name="description" content="Your page description, under 160 characters." />
<meta property="og:description" content="Your page description, under 160 characters." />

<!-- Image: 1200×630px minimum for Discover full-width cards -->
<meta property="og:image" content="https://example.com/og-image.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Descriptive alt text for the image" />

<!-- Canonical URL -->
<meta property="og:url" content="https://example.com/your-page" />
<link rel="canonical" href="https://example.com/your-page" />

<!-- Enable large image previews for Google Discover -->
<meta name="robots" content="max-image-preview:large" />

Common Mistakes That Hurt Google Visibility

1.og:title diverges significantly from <title> — Google may distrust both and rewrite the result title with its own heuristic.
2.og:image under 1200px wide — the page misses out on full-width Discover cards and appears as a small thumbnail.
3.Missing max-image-preview:large — even with a 1200px image, Discover will downgrade to a small thumbnail unless this robots directive is set.
4.og:url pointing to a different domain — Google may associate metadata with the og:url instead of the actual page, creating indexing confusion.
5.og:description written as keyword spam — Google ignores keyword-stuffed descriptions in both the snippet and Discover. Write for humans.
6.JavaScript-only meta tags — Googlebot renders JavaScript but does so on a delayed schedule. Tags in server-rendered HTML are indexed faster.

Validating What Googlebot Sees

Validating your OG tags for Google requires checking two things: that the tags are present in the server-rendered HTML, and that the og:image is accessible and the right size. You can do this with Google Search Console's URL Inspection tool, with curl using the Googlebot user-agent, or with OGProof.

# Simulate Googlebot fetch (note: real Googlebot renders JS; curl does not)
curl -s -A "Googlebot/2.1 (+http://www.google.com/bot.html)" \
  "https://example.com/your-page" \
  | grep -iE 'og:title|og:description|og:image|og:url'

Note: curl with the Googlebot user-agent shows you the static HTML — it does not render JavaScript. To see the fully-rendered page (as Googlebot does), use Google Search Console's URL Inspection tool or a headless browser. For static OG tags generated by Next.js or other SSR frameworks, curl is sufficient.

OGProof fetches your URL using the Googlebot user-agent alongside the five major social crawler user-agents, parses your OG tags, and renders a visual preview for each platform. It validates og:image dimensions against Google's 1200px Discover threshold and flags missing max-image-preview:large directives.

Checklist: Google-Ready Open Graph Tags

—og:title consistent with <title> tag and on-page h1
—og:description consistent with <meta name="description">
—og:image present, absolute HTTPS URL, publicly accessible
—og:image at least 1200px wide for Google Discover full-width cards
—og:image:width and og:image:height declared
—meta name="robots" includes max-image-preview:large
—og:url set to canonical URL (matches <link rel="canonical">)
—All OG tags present in server-rendered HTML, not JavaScript-injected
—Validated with Google Search Console URL Inspection or OGProof

Google Open Graph Tags: How Google Uses OG Metadata in 2026