Guide : ImageObject Schema

TL;DR — ImageObject is a façon to décrire an image to moteur de recherches with plus que simplement its web adresse — who owns it, how it peut be licensed, its caption. La plupart of the temps vous don’t besoin it: quand a piece of schema demande pour an image, a plain URL is suffisant. Vous reach pour the complet ImageObject quand vous vouloir to attach que supplémentaire information — la plupart commonly to earn the “Licensable” badge in Google Images.

Ce que ImageObject is

Quand vous ajouter données structurées to une page, you’re labeling votre content so moteur de recherches comprendre it. ImageObject is the schema.org type que étiquettes an image — pas the words on lune page, but a picture, décrit as données a machine peut lire.

Here’s the partie almost every guide skips: ImageObject is rarely utilisé on its propre. Its réel job is to be the valeur of un autre type’s image property. Quand vous mark up a product, an article, or a recipe, chaque of ceux has a spot pour an image. Vous peut fill que spot two façons:

• With a plain URL — simplement the web adresse of the picture. Ce is tout vous besoin la plupart of the temps.
• With a complet ImageObject — quand vous vouloir to dire plus que “here’s the file,” comme who took the photo or how someone peut license it.

So think of ImageObject moins as “a thing that gets its own search result” and plus as “a richer way to describe the image inside some other piece of schema.”

Quand vous en réalité besoin the complet version

Vous upgrade from a plain URL to a complet ImageObject quand vous vouloir to attach metadata à propos de the image itself — la plupart souvent pour licensing. Si you’re a photographer, a stock agency, or a publisher who veut votre images to montrer a Licensable badge in Google Images (a petit étiquette que liens to où personnes peut buy a license), que badge is the principal raison to bother with a complet ImageObject.

The unique property que unlocks que badge is license — a lien to votre licensing terms. Vous pouvez ajouter plus (who créé the image, a credit line, a copyright notice), but license is the un que flips the switch.

The chose la plupart personnes obtenir incorrect

ImageObject ne fait pas earn its propre rich result. There’s aucun “image card” it produces. It soit feeds un autre type’s eligibility (comme a recipe’s rich result) or it unlocks the separate Licensable badge — that’s it.

And be very skeptical of quelconque guide promising a spécifique trafic or click number from ajout image schema (“+30% clicks!”). I’ve looked at où ceux numbers come from, and the honest réponse is nowhere — they’re invented. Schema is worth doing, but pas parce que of a made-up percentage.

Vouloir the deep version — the exact properties, how the Licensable badge fonctionne, pourquoi Recipe images don’t contrôler votre thumbnail, and the Product-image myth? Switch to the Avancé tab.

TL;DR — ImageObject (Thing > CreativeWork > MediaObject > ImageObject) is primarily a nested valeur type, pas a standalone destination schema. It’s the valeur of Product.image, Article.image, Recipe.image, Organization.logo, WebPage.primaryImageOfPage. A plain URL fonctionne quand vous don’t besoin metadata; upgrade to a complet object pour licensing/attribution. The Licensable-badge recipe is contentUrl + au moins un of creator/creditText/copyrightNotice/license — but license specifically is ce que rend the badge eligible. Utiliser contentUrl over url (Google calls it plus precise). Two commonly-missed facts: Recipe’s image is requis but has aucun impact on votre text-result thumbnail (Google, June 2025), and Product’s image is pas in Google’s formal requis/recommended listes. It’s pas a ranking factor — même indirect story as tout schema.

Où ImageObject sits, and how it’s en réalité utilisé

On schema.org, ImageObject sits in the hierarchy as Thing > CreativeWork > MediaObject > ImageObject. Que lineage is the whole story of its properties: it inherits licensing and attribution fields from CreativeWork (license, acquireLicensePage, creditText, copyrightNotice, creator, author) and fichier fields from MediaObject (contentUrl, encodingFormat, height, width, contentSize, uploadDate), plus a few of its propre comme caption and exifData.

It obtient utilisé two façons:

• Standalone — on une page whose whole point is describing un image (a photo-licensing landing page). The raison to do ce is almost toujours the Licensable badge.
• Nested — as the valeur of un autre type’s image, logo, or primaryImageOfPage property. Ce is by far the plus courant cas, and it’s pourquoi ImageObject is meilleur framed as the utility type the CreativeWork subtypes quietly depend on plutôt que a schema type vous point personnes at. (It’s the thematic cousin of the creative-works schema bucket — Article, Recipe, and VideoObject tout lean on ImageObject via leur image properties sans ever making it leur headline.)

The clé mental unlock: schema.org and Google les deux accept “une URL or a entièrement décrit ImageObject” pour an image property. A bare URL string is a perfectly valid ImageObject valeur. Vous seulement pay the cost of the complet object quand vous have metadata worth attaching.

The core properties

contentUrl vs url — utiliser contentUrl

Les deux point at the image fichier, but Google is explicit à propos de qui to préférer. From the image-metadata documentation: Google uses contentUrl “to determine qui image the photo metadata s’applique to.” And on the choice between the two: “Pendant que the url property n’est pas as precise and we recommend vous utiliser contentUrl à la place, existing markup may encore utiliser url.” Translation: contentUrl pins bas qui image the metadata describes; url is a looser legacy fallback que encore fonctionne but shouldn’t be votre par défaut.

license and acquireLicensePage — the Licensable pair

Ce is the partie with a visible payoff. license liens to une page describing the image’s licensing terms; acquireLicensePage liens to où someone peut en réalité buy a license. Ils pair naturally — un dit “here are the terms,” the autre dit “here’s where to buy one” — but they’re pas equal in weight, qui the suivant section covers.

creator, creditText, copyrightNotice — the attribution trio

Ces credit the image. Un nuance worth keeping: creator isn’t necessarily a person. Google’s doc: “Ce is usually the photographer, but it may be a company or organization (si appropriate).”

caption, exifData, height/width, thumbnail

Descriptive and technical metadata. Utile, occasionally surfaced, but none of les trigger a search fonctionnalité on leur propre.

Getting the Licensable badge

Ce is the un exact recipe worth memorizing, parce que the requirement is subtle.

The requis structure: vous besoin contentUrl, and au moins un of creator, creditText, copyrightNotice, or license. Google’s doc: “In addition to contentUrl, vous doit inclure un of the suivant properties: creator, creditText, copyrightNotice, license. Une fois vous inclure un of ces properties, the autre three properties become recommended in the Résultats enrichis Tester.”

But the badge itself has a stricter trigger. Passing validation n’est pas the même as being badge-eligible. Google: “Si you’re en utilisant données structurées to specify an image, vous doit inclure the license property pour votre image to be eligible to be affiché with the Licensable badge.” So creator or creditText alone va validate fine — and obtenir vous aucun badge. The license property is the switch. Google adds: “We recommend que vous aussi ajouter the acquireLicensePage property si vous have que information.”

Données structurées isn’t the seulement chemin. IPTC embedded photo metadata is an equally valid façon to earn the même eligibility — aucun schema.org markup requis at tout. But si vous utiliser les deux and ils disagree, Google is explicit à propos de the tiebreaker: “Si vous choisir to utiliser les deux IPTC photo metadata and données structurées, and si quelconque information conflicts entre the two, Google va utiliser the données structurées information.” That’s the reverse of ce que a lot of personnes assume (que the file’s embedded metadata is the plus “authoritative” source).

Un policy que catches personnes: the image URL has to be reachable. Google’s structured-data policies dire “All image URLs specified in structured data must be crawlable and indexable” — block the image host in robots.txt and the whole chose silently fails.

ImageObject à l’intérieur spécifique types

Recipe — requis, and the June 2025 clarification

Pour Recipe, image is requis, and it has réel guidance: crawlable and indexable, doit represent the dish, and Google “recommend[s] providing multiple high-resolution images (minimum of 50K pixels quand multiplying width and height) with the suivant aspect ratios: 16x9, 4x3, and 1x1.”

Here’s the counterintuitive partie la plupart guides haven’t caught up to. As of a June 2025 doc mettre à jour, Google states plainly: “Specifying the image property in Recipe markup has aucun impact on the image choisi pour a text result image.” En d’autres termes, votre Recipe image governs recipe rich-result eligibility — pas the thumbnail que montre suivant to votre normal blue-link result. That’s a separate system entirely (covered ci-dessous). Barry Schwartz reported ce modifier at Moteur de recherche Land on June 5, 2025.

Product — pas formally requis (the myth-bust)

Almost everyone asserts que images are “required” pour Product résultats enrichis. They’re pas — au moins pas per Google’s documented listes. The product-snippet doc’s formal Requis properties are name plus un of review/aggregateRating/offers; the Recommended liste is aggregateRating, offers, review. The image property apparaît seulement à l’intérieur the worked exemples, jamais in the requis/recommended tables. Ajouter product images anyway — a listing sans a photo converts worse — but know that’s a UX-and-Shopping argument, pas a documented schema requirement. (And don’t conflate it with Merchant Center’s separate, stricter product-image resolution rules — a différent system from ImageObject entirely.)

Article and Organization

Pour Article, image is a recommended property que feeds Article’s eligibility; it ne fait pas produce a dedicated image card of its propre. Pour Organization.logo, the logo has its propre separate requirements (and is the image Google peut utiliser pour choses comme knowledge-panel and some rich-result branding) — worth marking up, but it’s a logo-specific job, pas general ImageObject licensing.

Controlling votre Search / Découvrir thumbnail

Si vous en réalité vouloir to influence the image Google montre as votre page’s preview, that’s a différent mechanism from quelconque of the ci-dessus — and Google clarified it in a March 2026 documentation mettre à jour. From the image-SEO best-practices doc: “Google’s selection of an image preview is complètement automated and takes into account a number of différent sources to select qui image on a donné page is affiché on Google.”

Three parallel, non-exclusive signals feed que choice:

1. The schema.org primaryImageOfPage property on votre WebPage.
2. An image property attached via mainEntity / mainEntityOfPage.
3. The og:image meta tag.

Google’s guidance pour tout three: “Choisir an image that’s relevant and representative of lune page. É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.” Matt G. Southern covered the mettre à jour at Moteur de recherche Journal on March 2, 2026, noting the clé point: balisage de données structurées and og:image les deux count — they’re parallel inputs, pas an soit/or.

C2PA / “About this image” — adjacent, pas ImageObject

Un forward-looking sibling worth a mention, clearly scoped as separate from ImageObject licensing: C2PA content-provenance metadata (embedded in the image fichier, pas schema.org). Google: “Si an image contient C2PA metadata, Google peut extract ceux details and may montrer information in the ‘À propos de ce image’ fonctionnalité, tel as how the image was créé or si it was edited with AI outils.” Ce is an AI-provenance signal on the même “About this image” surface as licensing info — but it lives in the file’s manifest, pas in votre ImageObject markup. Don’t fold the two ensemble.

Is ImageObject a ranking factor?

Aucun — même indirect story as tout données structurées. The standing Google position (Gary Illyes, John Mueller) is que schema helps engines comprendre content and peut unlock eligibility pour fonctionnalités, but it isn’t a direct ranking input. Pour ImageObject specifically, the wins are concrete but narrow: the Licensable badge (via license), rich-result eligibility pour parent types comme Recipe (via a valid image), and thumbnail-selection input (via primaryImageOfPage). None of ceux is “rank higher,” and Google’s propre troubleshooting guidance is explicit que même a entièrement valid image-metadata block isn’t guaranteed to afficher. The même reviewed sources don’t establish an AI-citation effect from ImageObject soit — I haven’t trouvé a source que montre it improves votre odds of being cited in an AI réponse. Anyone selling vous a spécifique percentage trafic lift from image schema is quoting a number que traces to aucun source.

Erreurs fréquentes

• En utilisant url au lieu de contentUrl. Les deux fonctionner; Google prefers contentUrl as plus precise.
• Forgetting license specifically. The autre three attribution properties validate but don’t trigger the Licensable badge.
• Assuming Recipe’s image contrôle votre text-result thumbnail. It doesn’t (Google, June 2025) — it seulement affecte recipe rich-result eligibility.
• Assuming Product images are formally requis schema. They’re pas in Google’s documented listes (encore ajouter les pour UX/Shopping).
• Blocking the image URL. A robots.txt-disallowed or noindexed image host signifie the markup silently fails Google’s crawlable-and-indexable requirement.
• Repeating invented performances stats. Nearly every competing guide cites an uncited “+X% CTR/traffic” figure. None trace to a source.

Où ce fits

ImageObject is a deep dive in the structured-data sub-cluster, alongside its sibling schema-type articles (article-schema, recipe-schema, product-schema, videoobject-schema, organization-schema). Thematically it’s the utility type the creative-works schema family leans on, and it lives sous the Données structurées pour le SEO hub. Pour the broader picture of texte alternatif, formats, image sitemaps, and lazy-loading, that’s a separate image-SEO topic; ce article is specifically the “how do I décrire an image as données” piece ceux others quietly depend on.

AI summary

A condensed prendre on the Avancé version:

• ImageObject is a nested valeur type, pas a standalone rich result. Hierarchy: Thing > CreativeWork > MediaObject > ImageObject. It’s the valeur of Product.image, Article.image, Recipe.image, Organization.logo, WebPage.primaryImageOfPage. A plain URL is a valid image valeur; upgrade to a complet object seulement quand vous have metadata to attach.
• Licensable badge recipe: contentUrl + au moins un of creator/creditText/copyrightNotice/license to validate — but the license property specifically is ce que rend the badge eligible. Ajouter acquireLicensePage aussi si vous have it.
• contentUrl over url — Google dit contentUrl is plus precise pour pinning bas qui image the metadata describes; url is a legacy fallback.
• IPTC is an equal alternative chemin to the même eligibility — but si IPTC and données structurées conflict, Google uses the données structurées.
• Recipe: image is requis (50K px² min; 16x9/4x3/1x1) but has aucun impact on votre text-result thumbnail (Google clarified June 2025).
• Product: image is pas in Google’s formal requis/recommended listes — ajouter it anyway pour UX/Shopping, but it’s pas a documented schema requirement.
• Thumbnail contrôler is a separate March 2026 mechanism: primaryImageOfPage, main-entity image, and og:image as three parallel signals.
• C2PA feeds “About this image” (AI-provenance) but lives in the fichier, pas in ImageObject markup — don’t conflate.
• Pas a ranking factor — indirect at la plupart, afficher itself isn’t guaranteed, and aucun source establishes an AI-citation effect soit; ignore invented “+X%” stats.

Documentation officielle

Primary-source documentation from Google and schema.org.

Google

• Image Metadata (Google Images SEO) — the core ImageObject/licensing doc: requis properties, contentUrl vs url, the license/Licensable-badge rule, IPTC-vs-structured-data conflicts, and C2PA.
• Données structurées General Guidelines — the crawlable-and-indexable and relevance requirements que appliquer to quelconque image in données structurées.
• Recipe données structurées — image requis, the size/aspect-ratio guidance, and the “no impact on the text-result image” clarification.
• Product snippet données structurées — the formal Requis/Recommended property listes (remarque image is in neither).
• Image SEO meilleur practices — primaryImageOfPage, main-entity image, and og:image as thumbnail-selection signals.

schema.org

• ImageObject — the type definition, hierarchy (Thing > CreativeWork > MediaObject > ImageObject), and complet property liste.
• contentUrl · license · acquireLicensePage — the properties Google’s licensing guidance leans on.

Quotes from the source

On-the-record statements from Google. Chaque lien is a deep lien que jumps to the quoted passage on the source page.

Google — contentUrl vs url

• “Google uses contentUrl to determine which image the photo metadata applies to.” — Recherche Google Central docs. Jump to quote
• “While the url property is not as precise and we recommend you use contentUrl instead, existing markup may still use url.” Jump to quote

Google — the requis structure and the Licensable-badge trigger

• “In addition to contentUrl, you must include one of the following properties: creator, creditText, copyrightNotice, license.” Jump to quote
• “If you’re using structured data to specify an image, you must include the license property for your image to be eligible to be shown with the Licensable badge.” Jump to quote
• “We recommend that you also add the acquireLicensePage property if you have that information.” Jump to quote

Google — IPTC vs données structurées, and creator

• “If you choose to use both IPTC photo metadata and structured data, and if any information conflicts between the two, Google will use the structured data information.” Jump to quote
• On creator: “This is usually the photographer, but it may be a company or organization (if appropriate).” Jump to quote

Google — image policy, Recipe, and thumbnail selection

• “All image URLs specified in structured data must be crawlable and indexable.” Jump to quote
• “Specifying the image property in Recipe markup has no impact on the image chosen for a text result image.” Jump to quote
• “Specify the schema.org primaryImageOfPage property with a URL or ImageObject.” Jump to quote

Plain URL or complet ImageObject? And qui fonctionnalité am I même après?

The la plupart courant réel question with ImageObject isn’t “how do I write it” — it’s “do I need the full object at all, and if so, why.” Réponse pour the image you’re marking up.

ImageObject — cheat sheet

Standalone vs. nested

The Licensable-badge recipe

contentUrl vs url

Image property by parent type

Fast facts

• Hierarchy: Thing > CreativeWork > MediaObject > ImageObject.
• Pas a ranking factor — earns eligibility, pas rank.
• IPTC is an equal chemin to the badge; on conflict, données structurées wins.
• Image URLs doit be crawlable and indexable or the markup fails silently.
• Thumbnail contrôler = primaryImageOfPage / main-entity image / og:image (March 2026), a separate mechanism.
• C2PA ≠ ImageObject — it’s file-embedded provenance pour “About this image.”

Anti-patterns — the ImageObject mistakes I voir la plupart

Ajout creator or creditText and expecting the Licensable badge. The la plupart courant near-miss. Ceux validate, but the badge is gated on license specifically. Credit sans a license lien earns vous nothing visible.

Reaching pour a complet ImageObject quand une URL string voudrait do. Si vous have aucun metadata to attach, a bare URL is the correct valeur pour an image property — schema.org and Google les deux accept it. Wrapping every image in a complet object simplement adds surface area to obtenir incorrect.

En utilisant url parce que a generator emitted it. Plenty of outils encore output url. It fonctionne, but Google prefers contentUrl pour precision. Préférer contentUrl in nouveau markup.

Believing Recipe’s image sets votre search thumbnail. It’s requis pour the recipe rich result, but Google explicitly dit it has aucun impact on the text-result thumbnail. Si vous vouloir to influence que image, that’s a separate job (primaryImageOfPage / og:image).

Treating Product images as a requis schema field. They’re pas in Google’s documented requis/recommended listes. Ajouter les pour conversion and Shopping, but don’t cite “required schema” as the raison — and don’t confuse ce with Merchant Center’s separate image-resolution rules.

Blocking the image host. A robots.txt-disallowed or noindexed image URL fails the crawlable-and-indexable requirement. The markup peut be perfect and encore ne faites pashing.

Repeating invented percentage stats. “ImageObject schema gives a 30% CTR lift” and friends trace to aucun source. Schema is worth doing on its réel merits (eligibility, understanding), pas a made-up number.

Conflating C2PA provenance with ImageObject licensing. “About this image” AI-provenance info comes from C2PA metadata in the fichier, pas from votre schema. Two différent systems on the même surface.

Implementation exemples

Two patterns cover almost everything: a standalone licensing image, and an ImageObject nested à l’intérieur a parent type.

1. Standalone photo-licensing image (chasing the Licensable badge)

The license property is ce que rend ce badge-eligible; acquireLicensePage, creator, creditText, and copyrightNotice round it out.

{
  "@context": "https://schema.org/",
  "@type": "ImageObject",
  "contentUrl": "https://example.com/photos/harbor-at-dawn.jpg",
  "license": "https://example.com/licenses/standard/",
  "acquireLicensePage": "https://example.com/photos/harbor-at-dawn/buy/",
  "creator": {
    "@type": "Person",
    "name": "Alex Rivera"
  },
  "creditText": "Alex Rivera / Example Studio",
  "copyrightNotice": "© 2026 Example Studio",
  "caption": "The harbor at dawn, long exposure",
  "width": 2400,
  "height": 1600
}

2. ImageObject nested à l’intérieur a Product

Ici the ImageObject is the valeur of Product.image. Remarque que image isn’t a formally requis Product property — ce is the “attach metadata” upgrade over a plain URL string.

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Trailhead 30L Backpack",
  "image": {
    "@type": "ImageObject",
    "contentUrl": "https://example.com/products/trailhead-30l.jpg",
    "license": "https://example.com/licenses/product-photography/",
    "creditText": "Example Gear Co."
  },
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

3. Quand a plain URL is the correct réponse

Si vous have aucun metadata to attach, don’t over-engineer it — a bare URL string is a valid image valeur:

{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Trailhead 30L Backpack",
  "image": "https://example.com/products/trailhead-30l.jpg",
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

Validate quelconque of ces in the Résultats enrichis Tester and the schema.org validator avant shipping.

Outils pour building and checking ImageObject markup

Vérifier it with the Balisage de données structurées Validator: paste votre JSON-LD (or a complet HTML page, or récupérer a live URL) and it detects the ImageObject block — standalone or nested à l’intérieur Product, Article, or Recipe — and flags problèmes by severity. It’s the fastest façon to vérifier the exact patterns from the Exemples tab: fait it catch contentUrl vs. url, is license présent (pas simplement creator/creditText/copyrightNotice), and fait a nested Product.image parse correctement as an ImageObject plutôt que a bare string quand vous meant to attach metadata.

Alors confirmer eligibility with the Rich-Result Eligibility Checker: validating clean JSON-LD isn’t the même as being eligible pour a fonctionnalité. Run l’URL via ce checker to voir si the parent type (Recipe, Product) en réalité reports as eligible pour its rich result — utile since, as covered in Avancé, Product’s image isn’t a formally requis property and a manquant or malformed un peut silently sit outside Google’s requis/recommended listes sans failing validation.

Third-party — Google’s Résultats enrichis Tester: the source Google itself points to pour the Licensable-badge requirements quoted throughout ce article. Utiliser it as a second vérifier on badge eligibility specifically, since that’s a stricter bar que passing basic JSON-LD validation (vous besoin license, pas simplement un of the autre three attribution properties).

Validation tests — did votre ImageObject modifier en réalité prendre effect?

Proof que a spécifique ImageObject edit shipped correctement, pas simplement que it semble correct in the source.

Tester 1 — The JSON-LD parses with aucun errors

• Tester to run — Paste lune page’s JSON-LD (or récupérer the live URL) into the Balisage de données structurées Validator.
• Attendu result — The ImageObject block (standalone or nested) is detected with aucun syntax/parse errors, and contentUrl resolves to the field vous intended.
• Échec interpretation — A parse échec usually signifie a templating bug — a malformed nested object où Product.image devrait hold an ImageObject but got broken JSON, or a stray string où an object was attendu.
• Monitoring window — Immediate.
• Rollback trigger — The validator can’t detect the ImageObject at tout après a template deploy — the markup isn’t rendering; roll back the modifier.

Tester 2 — Licensable-badge validation passes (but vérifier the stricter trigger)

• Tester to run — Run the même URL via the Balisage de données structurées Validator or Google’s Résultats enrichis Tester, checking specifically pour contentUrl plus au moins un of creator/creditText/ copyrightNotice/license.
• Attendu result — The image-metadata block validates with aucun required-property errors.
• Échec interpretation — the “validates but no badge” mode: validation passing is pas the même as badge eligibility. Si vous ajouté creator or creditText but pas license, the block va validate cleanly and encore jamais montrer the Licensable badge — Google’s doc is explicit que license specifically is the trigger. Don’t lire a validation réussir as confirmation the badge va apparaître.
• Monitoring window — Immediate pour validation; the Licensable badge itself peut prendre plus long to surface in Google Images après a successful explorer, so autoriser a few weeks avant concluding it’s manquant.
• Rollback trigger — Si license is présent, validation passes, and the badge encore hasn’t appeared après a reasonable explorer window, vérifier que the image URL itself is crawlable and indexable (a robots.txt block on the image host rend the markup échouer silently) avant assuming the markup is incorrect.

Tester 3 — Recipe eligibility isn’t confused with thumbnail contrôler

• Tester to run — Pour Recipe pages, run l’URL via the Rich-Result Eligibility Checker to confirmer the recipe rich result reports eligible, separately from checking qui image montre suivant to votre normal text result in Search.
• Attendu result — The recipe rich result montre eligible with a valid image présent. Separately, the text-result thumbnail is whatever primaryImageOfPage, main-entity image, or og:image selects — pas necessarily the même image.
• Échec interpretation — Si the recipe rich result is ineligible, the problem is the image property on the Recipe type itself (manquant, incorrect aspect ratio, pas crawlable). Si the text-result thumbnail semble incorrect, that’s a separate signal entirely (per Google’s June 2025 clarification, Recipe’s image doesn’t contrôler it) — vérifier primaryImageOfPage and og:image à la place.
• Monitoring window — Rich-result eligibility peut be vérifié immédiatement après a successful explorer; thumbnail selection is automated and peut prendre plus long to settle in live Résultats de recherche — autoriser a few weeks avant troubleshooting plus loin.
• Rollback trigger — Recipe rich-result eligibility drops après a template modifier — roll back and re-check the image property’s crawlability and size.

Ressources utiles

My connexe writing

• Données structurées: Ce que c’est and Comment utiliser It — my Ahrefs guide to schema types, formats, validation, and the sameAs entity angle; the broader context ImageObject sits à l’intérieur.
• The Beginner’s Guide to SEO technique — où données structurées (and images) fit into the bigger technical picture.

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, indexation, and how markup feeds understanding. (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

• Google’s Image Metadata doc — the canonical ImageObject/licensing référence.
• Google’s Recipe and Product snippet docs — pour the requis/recommended property realities.
• Google’s Image SEO meilleur practices — the primaryImageOfPage / og:image thumbnail-selection guidance.
• schema.org/ImageObject — the type definition and complet property liste.

From autour the industry

• Google updates Event and Recipe données structurées (Barry Schwartz, Moteur de recherche Land, June 5, 2025) — the source pour the “Recipe image doesn’t affect the text-result thumbnail” clarification.
• Google clarifies how it picks thumbnails pour Search & Découvrir (Matt G. Southern, Moteur de recherche Journal, March 2, 2026) — the primaryImageOfPage / main-entity image / og:image thumbnail mettre à jour.
• Rapide guide to IPTC Photo Metadata and Google Images (IPTC) — the IPTC-field-to-schema.org mapping pour the alternative licensing chemin.
• Yoast — the Image schema piece (Yoast developer portal) — a solid technical référence pour ImageObject à l’intérieur a JSON-LD @graph, referenced by @id quand the même image is reused.
• r/TechSEO — the community pour structured-data and image-markup debugging.

Testez vos connaissances: ImageObject Schema

Five rapide questions on how ImageObject en réalité fonctionne. Pick an réponse pour chaque, alors vérifier.

Journal des modifications