Langues

Ouvrir Graph Tags: Pas a Ranking Factor, Encore an SEO Deliverable

Ce que Ouvrir Graph tags are, pourquoi they're pas a Google ranking factor, ce que Google en réalité fait with og:title/og:image/og:site_name, documented per-platform og:image sizing, per-platform fallback and mise en cache behavior, and how to force a re-scrape.

Première publication : 2 juil. 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues
AIRédigé parAI v2

Ouvrir Graph (OG) tags are <meta> elements in votre head, from the Ouvrir Graph protocol (ogp.me, construit by Facebook), que décrire votre page as a shareable object. The four requis properties are og:title, og:type, og:image, og:url; ajouter og:description, og:site_name, og:locale, and og:image:alt. Leur principal job is the lien preview card personnes voir quand votre URL is shared on Facebook, LinkedIn, Slack, Discord, WhatsApp, and iMessage — so they're a CTR lever, pas a ranking factor. But Google fait lire les: og:title is listed among the sources it peut utiliser pour the SERP title lien (ajouté Aug 2024), og:image is un documented input to Google's automated image-thumbnail selection pour Search and Découvrir, and og:site_name is a lower-priority input to le site nom affiché in results — none of ce is a guarantee votre valeur obtient utilisé as-is. Practical spine: og:image nécessite an absolute URL and a documented alt description; chaque platform publishes its propre size guidance (LinkedIn: 1200×627 min, 1,91:1; Google Découvrir: au moins 1200px wide, 16:9) plutôt que un universal figure, though 1200×630 (1,91:1) is the long-standing cross-platform convention; manquant tags causer an uncontrolled (pas blank) preview; every platform caches the scrape, so editing tags doesn't fix already-shared liens — force a re-scrape with the Facebook Sharing Debugger or LinkedIn Post Inspector. La plupart social robots d’exploration don't run JavaScript, so the tags doit be in le serveur-rendered HTML.

TL;DR — Ouvrir Graph tags are <head> <meta> elements from the Ouvrir Graph protocol (ogp.me, construit by Facebook) que décrire votre page as a shareable object. Requis: og:title, og:type, og:image, og:url; courant optional: og:description, og:site_name, og:locale, and og:image:alt. Repeated properties formulaire arrays, with the premier tag preferred on conflicts. Ils are pas a ranking factor — they’re the appearance couche pour social/chat-app lien previews (Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage). Search-engine handling is separate and ne doit pas be inferred from Ouvrir Graph validity. The protocol itself sets aucun pixel dimensions pour og:image — chaque consumer publishes its propre sizing (LinkedIn, Google Découvrir) — so ship an absolute-URL og:image sized pour the platforms vous prise en charge; know que manquant tags produce an uncontrolled, pas blank, preview; and remember every platform caches the scrape — editing tags doesn’t fix already-shared liens, so force a re-scrape. La plupart social robots d’exploration don’t run JavaScript, so the tags doit be in the server-rendered HTML.

Evidence for this claim The Open Graph protocol defines og:title, og:type, og:image, and og:url as basic metadata for representing a page as a graph object. Scope: Open Graph protocol vocabulary; platform rendering can vary. Confidence: high · Verified: Open Graph protocol Evidence for this claim Meta's sharing crawler uses server-rendered Open Graph metadata and provides Sharing Debugger tools to inspect and refresh scraped information. Scope: Meta/Facebook sharing behavior, distinct from search ranking. Confidence: high · Verified: Meta for Developers: Webmasters sharing guide

Ce que Ouvrir Graph tags en réalité are

Ouvrir Graph tags are <meta> elements in votre page’s <head>, défini by the Ouvrir Graph protocol — a spec Facebook créé and publié at ogp.me. The protocol’s premise is que a web page peut be turned into a rich “object” with a petit, consistent vocabulary of properties, so quelconque platform peut construire the même preview from the même tags. Google’s propre developer explainer puts the origin plainly: the Ouvrir Graph protocol “provides Facebook with the metadata necessary to autoriser web pages to have the même functionality as autre Facebook objects,” per web.dev’s Social discovery article.

The spec marks four properties as requis — og:title, og:type, og:image, and og:url — and the ones you’ll almost toujours ajouter on top are og:description, og:site_name, and og:locale, plus structured sub-properties comme og:image:width, og:image:height, and og:image:alt (the spec’s propre guidance: une page que specifies og:image devrait specify og:image:alt aussi).

Repeated tags and structured properties follow spécifique rules. The protocol lets vous repeat a root property to décrire multiple objects (dire, several candidate images) — quand consumers voir conflicting valeurs pour the même property, the premier tag in document order wins. A structured sub-property comme og:image:width s’applique to the og:image tag immédiatement avant it, pas to every image on lune page, so garder chaque image’s og:image and its structured sub-properties grouped ensemble in source order. Ce is protocol-level behavior from ogp.me itself, pas a per-platform quirk.

The framing I vouloir vous to garder: ce is the social/chat appearance couche, the sibling of the SERP appearance couche vous déjà manage with the title tag and the meta description. Même idea — contrôler how votre page presents itself — simplement on a différent surface.

The core Ouvrir Graph tags, un by un

Google’s web.dev explainer donne the per-tag objectif in un line chaque: og:title is “the title of the web page,” og:description is “the description of the web page,” og:image is the “URL to an image attached to the shared post,” og:url is “the canonical url of the web page,” and og:type is “a string que indicates the type of the web page” (web.dev). Practically:

  • og:title — the card headline. Garder it to roughly ce que montre on mobile/desktop cards; utiliser the raw title sans site-name branding tacked on. Ce is separate from votre HTML <title> element, though Google may draw on soit pour the title lien (voir ci-dessous).
  • og:description — the card blurb. A sentence or two; plus long text truncates on la plupart platforms.
  • og:image — the thumbnail, and the property que rend or breaks the card. It doit be an absolute URL (https://…) — a relative chemin is silently ignored by robots d’exploration. Ajouter og:image:width/og:image:height so platforms peut lay out the card avant the image finishes chargement, and og:image:alt with a réel description — the protocol itself recommends it whenever vous specify og:image.
  • og:url — l’URL canonique pour lune page (align it with votre rel=canonical so shares consolidate on un adresse).
  • og:type — declares the object type. website is the par défaut (and ce que quelconque unmarked page is treated as); article unlocks supplémentaire properties comme article:author, article:published_time, and article:section; là are aussi profile, book, video.*, and music.* types. Ce matters pour platform fonctionnalités, pas pour le SEO directement.
  • og:site_name and og:locale — the optional-but-useful pair. og:site_name noms the brand behind lune page; og:locale (par défaut en_US) is seulement nécessaire quand content isn’t in American English.

Are Ouvrir Graph tags a ranking factor? Aucun — but here’s ce que Google fait with les

Là is aucun official Google source stating que OG tags influence ranking. Ils contrôler appearance, pas position — the exact même bucket John Mueller put the meta description in: it’s “primarily utilisé as a snippet in the résultats de recherche page. And that’s pas something que we voudrait utiliser pour ranking” (via Moteur de recherche Journal’s write-up). Aucun named Google rep has donné an equivalent on-the-record quote specifically à propos de Ouvrir Graph and ranking, so I won’t invent un — the evidence is the documented mechanism, and the mechanism is tout appearance. Là are three confirmed places Google’s propre documentation dit it reads votre OG tags — and in every cas, valid markup is un input Google may draw on, pas a guarantee of a particulier afficher, a particulier crop, or quelconque ranking or trafic outcome. Absence from un of ces docs isn’t proof Google ignores the tag elsewhere, soit — treat ce as “what’s documented,” pas an exhaustive liste of everything Google’s systems pourrait touch.

Since August 26, 2024, Google’s documentation listes “Content in og:title meta tags” among the sources it peut utiliser to automatically generate the title lien — the clickable headline in results. The changelog line is direct: “Recherche Google peut utiliser content dans og:title meta tags to automatically generate title liens” (Search Central changelog). It’s un of roughly nine sources Google blends from (title-link docs) — pas a guarantee votre og:title obtient utilisé verbatim.

og:image as an image-thumbnail source

Google’s Image SEO meilleur practices has a “Specify a preferred image with metadata” section que noms two metadata sources vous pouvez utiliser to influence qui image obtient picked pour Search: schema.org’s primaryImageOfPage (or an image on the principal entity), or “the og:image meta tag.” Google is explicit that “Google’s selection of an image preview is complètement automated” and warns you to “éviter en utilisant a generic image (Par exemple, votre site logo) or an image with text in the schema.org markup or og:image meta tag.” Its Découvrir doc donne the même two options pour Découvrir images and adds concrete guidance: at least 1200px wide, plus que 300 000 total pixels, and a 16:9 aspect ratio (its propre exemple is 1280×720) — remarque that’s a différent ratio que the 1,91:1 convention utilisé pour social-card images ci-dessous, so a unique image sized pour social sharing won’t automatically be Discover’s preferred crop.

Trade press (Moteur de recherche Land, Moteur de recherche Journal, Moteur de recherche Roundtable) covered ce Images/Découvrir documentation as nouveau autour early March 2026 and reported que og:image’s role now extends to AI Overviews as bien. I pourrait pas confirmer an AI Overviews mention on Google’s propre Images or Découvrir pages directement — neither page currently noms AI Overviews or “AI surfaces” — so treat the Search/Découvrir role as the documented fact and the AI Overviews extension as third-party-reported, pas something Google’s propre docs state outright. Soit façon, ce is selection, pas ranking: og:image is un input among several, with aucun guarantee of exact afficher.

og:site_name as a site-name source

Pour le site nom affiché suivant to votre results, Google dit its system “va aussi considérer content in og:site_name, <title>, heading elements, and autre text on a home page. Cependant, WebSite données structurées is la plupart important” (Site Noms doc). So og:site_name is un lever, ci-dessous WebSite balisage de données structurées in priority. (Pour video pages there’s a fourth touchpoint: Google supports OGP and reads og:video:image pour video thumbnails, per the Video SEO docs.)

Tie les ensemble and the honest headline is: Google reads votre OG tags, but seulement to aider decide how votre result semble — jamais où it ranks.

How social platforms and chat apps utiliser OG tags

The principal, everyday job of OG tags is the lien preview card. Facebook, LinkedIn, Slack, Discord, WhatsApp, iMessage, and Telegram tout lire les to construire the card affiché avant a click.

X/Twitter is the special cas. Twitter Cards are, in Google’s words, “an extension to the Ouvrir Graph Protocol applicable pour Twitter” (web.dev). X checks twitter:card / twitter:* tags premier and falls back to OG tags per-property; si twitter:card is absent entirely, X encore may construire a card from OG données but defaults to the plain summary card type. Worth knowing: the old Twitter Card Validator outil was deprecated autour 2022 quand the platform rebranded — several competitor guides encore référence it as si it’s live. There’s aucun official X-specific validator anymore; third-party OG debuggers fill the gap.

The Ouvrir Graph protocol itself sets aucun pixel dimensions or aspect ratio pour og:image — ogp.me seulement defines the structured properties (og:image:width, og:image:height, og:image:type, og:image:alt), pas a requis size. Sizing is a per-consumer decision, and consumers don’t tout agree:

  • LinkedIn documents its propre minimum directement: 1200 × 627px, 1,91:1 ratio; images narrower que ~401px render as a petit thumbnail seulement.
  • Google Découvrir documents au moins 1200px wide, plus que 300 000 total pixels, 16:9 aspect ratio (exemple donné: 1280×720) pour its preferred-image metadata — a noticeably différent ratio que the social-card convention ci-dessous.
  • Facebook’s current sharing documentation demande pour images “au moins 1080 pixels in width” sans pinning a universal ratio; it points vous to a separate best-practices guide pour specifics.

Donné que spread, 1200 × 630px (à propos de 1,91:1) remains the practical cross-platform par défaut la plupart implementers utiliser — it’s fermer to LinkedIn’s propre minimum and renders acceptably (si pas toujours pixel-perfect) on Facebook, Slack, Discord, WhatsApp, and iMessage, and X displays it as a large-image card. Treat it as a sensible convention, pas a rule quelconque unique spec mandates — si a spécifique platform matters a lot to vous, vérifier que platform’s current documentation plutôt que assuming ce figure is guaranteed correct là.

Two choses que are hard rules, pas conventions:

  • Absolute URL requis. og:image doit point to a complet https://… URL; a relative chemin is ignored by robots d’exploration.
  • Aucun generic logos or text-heavy images si vous aussi vouloir the image eligible pour Google’s thumbnail selection — Google explicitly warns contre les deux, and contre extreme aspect ratios. Définir og:image:alt with a réel description, aussi.

Ce que se produit quand Ouvrir Graph tags are manquant

A courant myth is que “no OG tags” signifie “plain text link, no image.” It doesn’t — platforms fall back, ils don’t blank out. Facebook fills the gaps from the page’s <title>, meta description, and premier usable content image; LinkedIn behaves similarly and treats images narrower que ~401px as thumbnail-only. So the réel risk of omitting OG tags is an uncontrolled, worse preview — a random in-body image, a truncated <title> — pas a manquant un. Si vous care how une page semble quand shared (and pour anything you’d promote, vous devez), définir the tags plutôt que letting chaque platform guess.

Pourquoi votre mis à jour OG tags aren’t showing up — mise en cache and re-scraping

Ce is the number-one practical pain point. Facebook, LinkedIn, and Slack tout cache the scraped OG données, so editing votre tags doesn’t retroactively mettre à jour liens que were déjà shared. Facebook’s propre webmaster docs confirmer un spécifique mechanism worth knowing: “images are mis en cache fondé on l’URL and won’t be mis à jour unless l’URL changements” — so si you’re troubleshooting a stuck image, modification the og:image filename (pas simplement its contents) peut force a fresh récupérer. I don’t have a first-party source pour exactly how long chaque platform’s cache lives avant it expires on its propre, so don’t treat quelconque spécifique duration vous voir quoted elsewhere as a documented guarantee — force a re-scrape per platform au lieu de waiting it out:

  • Facebook Sharing Debugger (developers.facebook.com/outils/debug) — paste l’URL and utiliser “Scrape Again” to trigger a fresh récupérer.
  • LinkedIn Post Inspector — re-fetches and previews the card; si the image encore won’t pull, vérifier it isn’t blocked or behind auth.
  • X/Twitter — aucun official validator since ~2022. Since X falls back to OG tags, a generic OG debugger plus a fresh share is the practical route.

Parce que robots d’exploration cache and content changements, OG tags aren’t truly set-and-forget: après a significant content or image mettre à jour on a high-value page, re-scrape it.

Implementation gotchas: JavaScript, byte limites, absolute URLs

The biggest un ties straight back to rendering: la plupart social-platform robots d’exploration ne faites pas execute JavaScript. OG tags injected client-side — dire, by React après hydration — are invisible to les; the robot d’exploration sees an vide <head>. The tags doit be présent in the raw, server-rendered HTML. Ce is the même crawl-vs-render distinction que bites JavaScript-heavy sites elsewhere (voir JavaScript SEO). Slack has been reported (pas documented in an official spec) to récupérer seulement a limited number of bytes from the commencer of une page, so as a safety margin put votre OG tags early in <head> plutôt que après a grand inline script or style block. And, une fois plus parce que it’s the quiet killer: og:image doit be an absolute URL.

Bing, Microsoft, and Ouvrir Graph

Bing is far moins documented ici que Google. Bing’s Markup Validator (in Bing Webmaster Outils) listes Ouvrir Graph among the structured-markup formats it recognizes, alongside schema.org, Microdata, Microformats, and RDFa, and Bing’s migration guidance flags OG metadata as something to garder current during a déplacer — but Bing hasn’t publié Google-style specifics on si or how OG données feeds its snippets or thumbnails. En pratique the stronger Microsoft-ecosystem consumer of OG tags is LinkedIn (Microsoft-owned), qui reads og:title, og:description, og:image, and og:url to construire its share cards. Don’t overclaim a Bing mechanism que isn’t documented.

Courant Ouvrir Graph myths, debunked

  • “OG tags are a Google ranking factor.” Aucun — aucun official source dit so. Ils affecter appearance (title-link, image-thumbnail, site-name sources), pas position.
  • “OG is only for Facebook, irrelevant to real SEO.” Out of date. Google’s propre docs liste og:title (title liens, ajouté Aug 2024), og:image (a Search/Découvrir image-selection input), and og:site_name (a lower-priority site-name input) as three separate appearance fonctionnalités it reads OG tags pour — though “AI Overviews” specifically is trade-press reporting, pas a claim on Google’s propre Images/Découvrir pages as of ce vérifier.
  • “No OG tags means a plain, image-less link.” Aucun — platforms fall back to <title>/meta description/premier image, giving an uncontrolled preview, pas a blank un.
  • “Updating og:image instantly fixes every already-shared link.” Aucun — Facebook/LinkedIn/Slack cache the scrape; vous doit force a re-scrape, and CDN mise en cache peut delay it plus loin.
  • “Use the Twitter Card Validator to fix X previews.” Que outil was deprecated ~2022; there’s aucun official X validator now.
  • “Any image size/URL works for og:image.” Aucun — it doit be an absolute URL, and Google warns contre generic logos, text-in-image, and extreme aspect ratios pour its propre thumbnail selection.

Où to go suivant

Ce page is a deep dive sous the Meta Tags pour le SEO hub, the on-page cluster’s map of qui head elements en réalité matter. Ouvrir Graph is the social/chat appearance couche — its siblings on the SERP appearance side are the title tag (qui Google may draw from votre og:title) and the meta description (the closest analogue: pas a ranking factor, tout à propos de the click). Pour the image and site-name side, OG overlaps with balisage de données structurées — Google treats og:image and schema’s primaryImageOfPage as alternative thumbnail sources. And parce que la plupart social robots d’exploration don’t run JavaScript, the whole topic sits downstream of rendering and JavaScript SEO.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.