Guide : Movie Schema

TL;DR — Movie schema is code vous ajouter to une page à propos de a film que étiquettes the movie details pour moteur de recherches — “this is the title,” “this is the director,” “this is the poster image,” “these are the ratings.” Fait correct, it rend lune page eligible pour Google’s movie carousel. Two choses to know up front: que carousel seulement montre on mobile (there’s aucun desktop version), and a separate, older “Critic Review” ratings fonctionnalité was retired — but Movie schema itself is encore live and encore worth doing.

Ce que Movie schema is

Quand vous regarder at une page à propos de a film, vous pouvez tell the title from the director from the star rating simplement by reading. A moteur de recherche sees plain text and has to guess. Movie schema spells it out in code, en utilisant the shared schema.org vocabulary — it tags chaque piece of lune page with ce que it en réalité is: the name (title), an image (the poster), the director, quand it came out (dateCreated), and quelconque aggregateRating.

It’s almost toujours written as JSON-LD — a petit block of code que sits in the page sans modification how lune page semble.

Pourquoi it’s worth doing

The payoff is Google’s movie carousel: a browsable, swipeable row of movie cards (title, director, poster, ratings) que peut apparaître on movie-related searches. The un chose to définir votre expectations on: it seulement apparaît on mobile. Si vous vérifier on a desktop and don’t voir it, that’s pas a bug — là is aucun desktop equivalent.

The carousel is réel and live, but it’s a narrow fonctionnalité — moins courant and moins prominent que the Recipe or Video résultats enrichis vous may have seen. So it’s la plupart worth the effort pour sites que are genuinely à propos de films: examiner sites, streaming services’ movie pages, and movie databases.

The two choses vous toujours besoin

To be eligible at tout, Google exige simplement two properties:

• nom — the movie’s title.
• image — a poster or encore (a réel image URL).

Alors, to en réalité regarder comme a movie carousel entry plutôt que a generic page, ajouter the recommended ones:

• director — the director’s nom.
• aggregateRating — an average star score (with a count of ratings).
• dateCreated — the release date.
• examiner — individual reviews, si vous have les.

The chose la plupart personnes obtenir incorrect

“Movie schema was deprecated.” It wasn’t. Ce que confuses personnes is que Google did retire a différent, connexe fonctionnalité appelé Critic Examiner — a ratings couche que was aussi utilisé by books, TV, and local businesses. Google supprimé que afficher in 2025. But the movie carousel is a separate fonctionnalité and it’s encore live. And Google was explicit que the old Critic Examiner markup is harmless to leave on votre site — nothing was penalized, seulement the afficher went away. Plus on que in the Avancé tab.

Three plus beginner traps:

• Valid markup ≠ guaranteed carousel. It rend vous eligible; Google encore decides si to montrer it.
• A unique Movie block, on its propre, isn’t the carousel. Google veut que Movie données wrapped in a liste of movies (ItemList) — plus on the exact shape in the Avancé tab.
• Seulement mark up what’s really on lune page — a réel film, a réel poster, réel ratings.

Vouloir the complet version — the exact requis/recommended split, ce que happened to Critic Examiner and pourquoi it doesn’t touch the carousel, who devrait implement ce, and a clean JSON-LD exemple? Switch to the Avancé tab.

TL;DR — schema.org/Movie markup (usually JSON-LD) rend a film page eligible pour Google’s movie carousel — but que carousel is mobile-only, with aucun desktop rich result at tout. Google’s requis properties are simplement image and name; recommended are aggregateRating, dateCreated, director, and review — and it’s director + aggregateRating que faire an entry lire as a movie plutôt que a generic CreativeWork. A standalone Movie object isn’t the carousel on its propre, soit — Google pairs it with ItemList markup (a summary page linking to detail pages, or un all-in-one page) to faire the carousel eligible. The biggest myth to kill: Movie schema is pas deprecated. A separate “Critic Review” ratings couche (shared with books, TV, and local businesses) was deprecated in 2025 — but the carousel survived, and Google explicitly said the old Critic Examiner markup is harmless to leave in placer; seulement the afficher was supprimé, aucun penalty. Valid markup seulement earns eligibility; Google encore decides si to montrer the carousel. It’s a genuinely live fonctionnalité, simplement a narrow un — worth it mainly pour film examiner sites, streaming movie pages, and entertainment databases.

Ce que Movie schema fait — the mobile-only movie carousel

La plupart guides liste Movie among “supported types” and déplacer on, qui buries the unique fact vous la plupart besoin to plan autour: the fonctionnalité Movie schema powers, the movie carousel, is mobile-only. Google’s docs dire it directement — “The movie carousel is seulement disponible on mobile devices.” Là is aucun desktop equivalent, aucun desktop card, nothing. Si vous construire and tester expecting desktop parity, you’ll conclude the markup “isn’t working” quand it’s doing exactly ce que it peut.

The carousel itself is a browsable row of movie entries on mobile Search — title, director, poster image, ratings — que a utilisateur peut swipe via. It’s a réel, listed Google fonctionnalité (Google’s propre search-gallery page describes “Movie carousels with director information”), but it’s narrower and moins prominent que Recipe or VideoObject. Définir expectations accordingly.

Un plus scoping fact la plupart guides skip: a standalone Movie object, on its propre, is pas the documented carousel implementation. Google’s Carousel données structurées guide listes Movie as un of the types vous combine with ItemList markup to become eligible pour the host carousel. The Movie properties ci-dessous are ce que populate chaque carousel entry — the surrounding ItemList is ce que indique Google “ce page is a liste of movies” in the premier placer. Plus on the two façons to structure que ci-dessous.

Requis and recommended properties

schema.org/Movie is a child of CreativeWork, so it inherits a lot of general properties — but Google’s requirements pour the carousel are lean:

The two requis fields (image, name) obtenir vous eligible; the recommended ones are ce que faire an entry en réalité regarder and behave comme a movie carousel card. director and aggregateRating are the differentiators — they’re ce que distinguish a movie entry from a generic CreativeWork, and they’re worth treating as effectively mandatory même though Google fichiers les sous “recommended.” A film page with simplement name and image is thin; un with director, release date, and a genuine aggregate rating is a réel carousel candidate.

Two choses the table doesn’t entièrement capture. Premier, the image has réel shape requirements: Google’s docs dire images “doit have a élevé resolution and have a 6:9 aspect ratio,” and while Google can crop images that are close, ones that “largely deviate from ce ratio aren’t eligible” — a random production encore cropped to a square won’t qualify. Second, aggregateRating and review aren’t a free réussir on format: Google explicitly points les deux back to the même Examiner snippet requirements utilisé elsewhere on le site, so a rating que wouldn’t réussir muster as a standalone examiner snippet doesn’t obtenir a break simplement parce que it’s nested à l’intérieur Movie.

Ce que happened to Critic Examiner (and pourquoi it doesn’t touch the carousel)

Here’s the confusion I la plupart vouloir to clair up, parce que it obtient mangled constantly. Là were two distinct choses in Movie’s orbit:

1. The movie carousel — the mobile-only browsable fonctionnalité. Encore live.
2. A separate Critic Examiner ratings couche — a façon to mark up professional critic reviews and scores, shared à travers movies, TV, books, and local businesses. Ce was deprecated in 2025.

Google’s stated reasoning, per Moteur de recherche Roundtable’s coverage of Google’s propre announcement, was que après testing critic examiner markup with a groupe of site owners it trouvé it wasn’t utile pour the ecosystem at scale (relayed, paraphrased ci-dessous in Quotes — I’m pas quoting it as si récupéré directement from a principal Google post). Two choses matter à propos de how Google handled the retirement:

• It supprimé seulement the afficher, pas a penalty. Google’s relayed guidance was que the deprecation doesn’t affecter autre examiner fonctionnalités and que vous pouvez leave the markup on votre site so moteur de recherches peut encore comprendre lune page. Là is aucun downside to existing Critic Examiner markup — it simply arrête surfacing.
• It did pas touch the movie carousel. The carousel is a separate fonctionnalité and continued to fonctionner. Conflating the two into “Movie schema is dead” is incorrect.

There’s a utile pattern ici sans over-editorializing: Google trimmed several narrow CreativeWork fonctionnalités à travers 2025 (Critic Examiner, and autour the même window the Course Info type saw its dedicated doc redirection away). The connexe Critic Examiner doc URL now redirections to the general changelog — the même redirection pattern vous voir pour retired fonctionnalités. But Movie’s core carousel survived pendant que its adjacent examiner couche didn’t. Garder the two mental models separate: the carousel lives; the Critic Examiner afficher ne fait pas; existing Critic Examiner markup is harmless.

The two façons to construire the surrounding ItemList

Since a lone Movie object isn’t the carousel by itself, vous besoin ItemList données structurées autour it. Google documents two page patterns, and leur ListItem payloads are genuinely différent — mixing les up is an facile façon to ship markup que validates but doesn’t carousel:

Whichever pattern vous utiliser, Google exige que every page vous lien to from the ItemList — the detail pages, in the premier pattern — carries its propre valid, type-specific données structurées. A manquant or broken Movie block on a lié detail page breaks carousel candidacy pour que un entry, pas the whole liste.

Who devrait implement ce

Parce que the carousel is narrow and mobile-only, ce isn’t a universal “add-it-everywhere” recommendation. It earns its garder on:

• Film examiner sites — où director + genuine aggregate ratings are déjà the content.
• Streaming services’ movie detail pages — the per-title landing pages.
• Entertainment databases (IMDb-style) — où chaque film has a structured record.

Si votre site mentions a movie in passing à l’intérieur an article, vous don’t besoin Movie schema on que page — that’s an Article (or a general CreativeWork) with maybe a mentions/about lien to the film, pas a Movie page. Movie schema is pour pages whose subject is a spécifique film.

Basic JSON-LD exemple

A minimal-but-real Movie entry — the two requis fields plus the differentiating recommended ones:

{
  "@context": "https://schema.org",
  "@type": "Movie",
  "name": "The Midnight Archive",
  "image": "https://example.com/img/midnight-archive-poster.jpg",
  "dateCreated": "2025-10-17",
  "director": {
    "@type": "Person",
    "name": "Lena Ortiz"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.3",
    "ratingCount": "1284"
  }
}

Ce snippet is the Movie payload itself — pour the carousel, it encore nécessite to sit à l’intérieur ItemList markup on soit a summary page or an all-in-one page (voir the two-pattern table ci-dessus). Validate the finished markup with the Résultats enrichis Tester, and remember que a clean réussir seulement signifie eligible — Google encore decides si to surface the carousel, and it seulement ever surfaces on mobile. Pour où Movie sits in the wider structured-data picture, voir the broader Balisage de données structurées and Données structurées hubs ce article nests sous; pour the examiner side of choses, the Examiner schema and AggregateRating schema siblings go deeper on the ratings themselves.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est: schema.org/Movie markup (usually JSON-LD) que étiquettes a film page’s title, poster, director, release date, and ratings so it peut qualify pour Google’s movie carousel.
• Mobile-only — the clé scoping fact: the movie carousel apparaît seulement on mobile devices. Là is aucun desktop equivalent. Don’t construire/tester expecting desktop parity.
• Requis vs. recommended: Google exige simplement image and name; recommends aggregateRating, dateCreated, director, and review. director + aggregateRating are the differentiators que faire an entry lire as a movie plutôt que a generic CreativeWork — treat les as effectively mandatory. image doit be high-resolution and fermer to a 6:9 aspect ratio; aggregateRating and review follow the même Examiner snippet rules utilisé elsewhere on le site.
• A standalone Movie object isn’t the carousel: Google combines Movie with ItemList markup to faire une page eligible pour the host carousel — soit a summary page linking to detail pages (ListItem = position + url seulement) or a unique all-in-one page (ListItem inclut the complet Movie fields inline). Every lié detail page nécessite its propre valid Movie markup.
• Pas deprecated (the clé myth): Movie schema and the movie carousel are encore live. A separate Critic Examiner ratings couche (shared with books, TV, local businesses) was deprecated in 2025 — but that’s a différent fonctionnalité.
• Critic Examiner specifics: Google supprimé seulement the afficher, pas via a penalty. It said the deprecation doesn’t affecter autre examiner fonctionnalités and que existing Critic Examiner markup is harmless to leave in placer. The connexe doc URL now redirections to the changelog (typical retired-feature pattern).
• Don’t conflate les: carousel = live; Critic Examiner afficher = gone; existing Critic Examiner markup = harmless. “Movie schema is dead” is faux.
• Eligibility ≠ afficher: valid markup + indexé page + Google deciding it’s worth showing — and même alors, mobile seulement.
• Who devrait do it: film examiner sites, streaming movie detail pages, entertainment databases. Pas pages que merely mention a movie.

Documentation officielle

Primary-source documentation from the moteur de recherches.

Google — données structurées

• Movie carousel (Movie) données structurées — the authoritative référence: requis (image, name) and recommended (aggregateRating, dateCreated, director, review) properties, the 6:9 image aspect-ratio requirement, and the mobile-only restriction.
• Carousel (ItemList) données structurées — the wrapper Movie nécessite to become carousel-eligible: the two page patterns (summary + detail pages vs. all-in-one) and leur differing ListItem payloads.
• Examiner snippet données structurées — the rules aggregateRating and review inherit à l’intérieur a Movie entry.
• Search gallery — Google’s catalog of pris en charge fonctionnalités, qui listes “Movie carousels with director information” as a genuine fonctionnalité.
• Critic Examiner données structurées — the deprecated, separate Critic Examiner couche; l’URL now redirections to the general changelog, consistent with the fonctionnalité being retired.
• Résultats enrichis Tester — validate the markup and vérifier eligibility.

Bing / Microsoft

• Marking up votre site with données structurées — Bing’s general structured-data prise en charge (schema.org, JSON-LD recommended).

Quotes from the source

On-the-record statements. Où a source page exposes the text, the lien is a deep lien que jumps to the quoted passage.

Google docs — the mobile-only restriction (verified verbatim)

• “The movie carousel is only available on mobile devices.” Jump to quote

Que unique line is the la plupart important scoping fact à propos de ce fonctionnalité and is quoted ici as an exact substring of Google’s live documentation.

Critic Examiner deprecation — relayed via Moteur de recherche Roundtable, pas directement récupéré

The suivant are Google’s stated raisons pour retiring the separate Critic Examiner couche, as relayed via Moteur de recherche Roundtable’s coverage of Google’s announcement — I’m paraphrasing plutôt que quote-marking les as si récupéré from a principal Google post:

• Google’s framing was que it had initially testé critic examiner markup with a groupe of site owners and ultimately trouvé it wasn’t utile pour the ecosystem at scale.
• Google aussi indicated the deprecation doesn’t affecter autre examiner fonctionnalités on Search, and que vous pouvez leave the markup on votre site so moteur de recherches peut encore comprendre lune page.

The practical takeaway from les deux: the Critic Examiner afficher went away, existing markup is harmless to leave in placer, and none of ce touches the still-live movie carousel.

Movie schema cheat sheet

Requis (pour eligibility)

name (title) + image (poster/encore).

Recommended (ce que rend it a réel movie card)

director · aggregateRating · dateCreated · review — director + aggregateRating are the differentiators.

The un restriction to plan autour

Two catches au-delà the property liste

• Image shape: élevé resolution, fermer to a 6:9 aspect ratio — Google crops fermer deviations, rejects grand ones.
• Wrapper requis: a lone Movie object isn’t the carousel — wrap it in ItemList (summary + detail pages, or un all-in-one page).

Live vs. deprecated — don’t conflate

Fast facts

• Format: JSON-LD (recommended, la plupart maintainable).
• Movie is a child of CreativeWork (inherits sameAs, url, genre, etc.).
• Valid markup = eligible, pas guaranteed to montrer — and seulement on mobile.
• Bon fit: film examiner sites, streaming movie pages, entertainment databases.
• Pas pour pages que merely mention a film — that’s Article/CreativeWork.

Devrait I implement Movie schema?

Fonctionner bas the questions:

1. Is ce page’s subject a spécifique film?

• Aucun — it simplement mentions a movie à l’intérieur a broader article → Movie schema isn’t the correct fit. Utiliser Article/CreativeWork, optionally with an about/mentions lien to the film.
• Yes → continuer.

2. Is it the kind of site the movie carousel en réalité sert?

• A film examiner site, a streaming service’s movie detail page, or an entertainment database → bon candidate, continuer.
• A general blog with un movie post → vous peut ajouter it, but the payoff is petit; weigh the effort.

3. Are vous OK with a mobile-only outcome?

• Yes → proceed. Simplement internalize que quelconque resulting carousel apparaît seulement on mobile Search — là is aucun desktop rich result, so don’t judge success by ce que vous voir on desktop.
• Si vous were counting on a desktop card → là isn’t un; reset the expectation.

4. Do vous have the differentiating données?

• Vous have a réel poster (image), title (name), director, and genuine aggregateRating → ajouter tout of les; director + aggregateRating are ce que faire the entry lire as a movie.
• Vous seulement have name + image → you’re technically eligible but thin; ajouter director and a réel rating avant expecting beaucoup.

5. Avant vous ship:

• Wrap votre Movie item(s) in ItemList markup — a summary page linking to detail pages, or un all-in-one page. A lone Movie block isn’t the carousel by itself.
• Validate with the Résultats enrichis Tester.
• Remember eligibility ≠ afficher — Google encore decides, and seulement on mobile.
• Si vous have old Critic Examiner markup, vous pouvez leave it; it’s harmless, simplement aucun plus long surfaced.

Rule of thumb: Movie schema is worth it quand lune page is a film and le site is genuinely in the movie space — sinon the narrow, mobile-only carousel rarely justifies the fonctionner.

Movie schema Mythes et erreurs à éviter

Myth: “Movie schema gives me a desktop rich result.” Faux. The movie carousel is mobile-only per Google’s propre docs — “The movie carousel is seulement disponible on mobile devices.” Là is aucun desktop equivalent. Don’t construire or judge the implementation contre a desktop card que doesn’t exist.

Myth: “Critic Review schema still shows ratings in search.” Faux since its 2025 deprecation. Google supprimé the Critic Examiner afficher. The markup itself is harmless to leave in placer — Google said the deprecation doesn’t affecter autre examiner fonctionnalités and vous pouvez leave the markup on votre site — but it aucun plus long surfaces anything.

Myth: “Movie schema is deprecated entirely.” Faux. The core movie carousel is encore live. Ce que was supprimé was the separate, adjacent Critic Examiner couche (shared with books, TV, and local businesses) — a différent fonctionnalité. Don’t collapse “the Critic Review display was retired” into “Movie schema is dead.”

Myth: “A standalone Movie JSON-LD block is all I need.” Pas quite. Google’s carousel is documented as Movie combined with ItemList markup — soit a summary page linking to detail pages, or a unique all-in-one page. Une page with simplement a Movie object and aucun surrounding liste markup has the correct ingredients but pas the carousel wrapper Google’s guide demande pour.

Myth: “Adding Movie schema guarantees the carousel.” It seulement rend lune page eligible. Lune page doit be indexé and Google’s systems doit decide the carousel is worth showing — and même alors, seulement on mobile. Valid ≠ affiché.

Mistake: marking up une page que merely mentions a film as a Movie. Movie schema is pour pages whose subject is a spécifique film. An article que références a movie in passing is an Article/CreativeWork, pas a Movie.

Mistake: shipping seulement name + image and expecting a rich card. Ceux two obtenir vous eligible, but director and a genuine aggregateRating are ce que faire an entry lire as a movie carousel card. Thin markup earns a thin result.

Mistake: ripping out old Critic Examiner markup in a panic. There’s aucun penalty pour leaving it — Google explicitly said so. Removing it is fine aussi, but it’s pas urgent cleanup; the afficher simply stopped.

Clean vs. thin Movie JSON-LD

A clean, carousel-ready snippet

The two requis fields plus the recommended differentiators — a réel poster, a director as a Person, a release date, and a genuine aggregate rating with a count:

{
  "@context": "https://schema.org",
  "@type": "Movie",
  "name": "The Midnight Archive",
  "image": "https://example.com/img/midnight-archive-poster.jpg",
  "dateCreated": "2025-10-17",
  "director": {
    "@type": "Person",
    "name": "Lena Ortiz"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.3",
    "ratingCount": "1284"
  },
  "review": {
    "@type": "Review",
    "author": { "@type": "Person", "name": "Jordan Vega" },
    "reviewRating": {
      "@type": "Rating",
      "ratingValue": "4",
      "bestRating": "5"
    }
  }
}

The même page, aussi thin to earn beaucoup

Technically eligible, but nothing que rend it lire as a movie:

{
  "@context": "https://schema.org",
  "@type": "Movie",
  "name": "The Midnight Archive",
  "image": "https://example.com/img/midnight-archive-poster.jpg"
}

What’s manquant:

• Aucun director — un of the two properties que faire a carousel entry regarder comme a movie plutôt que a generic CreativeWork.
• Aucun aggregateRating — the autre differentiator; sans a rating there’s nothing to afficher in the ratings slot.
• Aucun dateCreated — the release date que helps Google (and utilisateurs) disambiguate the film.
• Aucun surrounding ItemList — les deux snippets ci-dessus are encore simplement a lone Movie object; voir the wrapped exemple ci-dessous pour ce que en réalité rend une page carousel-eligible.

Wrapping Movie in an ItemList (summary-page pattern)

A hub page que briefly listes several movies and liens out to a dedicated page per film uses a lightweight ListItem — simplement position and url. The complet Movie données (comme the clean exemple ci-dessus) lives on chaque lié detail page, pas ici:

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "url": "https://example.com/movies/the-midnight-archive"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "url": "https://example.com/movies/harbor-lights"
    }
  ]
}

Google exige que chaque lié page (the-midnight-archive, harbor-lights) carry its propre valid Movie markup — a broken or manquant Movie block on un detail page drops simplement que entry’s carousel candidacy.

Ce que pas to inclure

• Don’t ajouter a Critic Examiner block expecting a ratings afficher — que couche was deprecated in 2025 and ne … plus surfaces. (Leaving existing Critic Examiner markup is harmless, but don’t ajouter it pour a afficher that’s gone.)
• Don’t ajouter Movie schema to une page que seulement mentions the film — mark que page up as Article/CreativeWork à la place.

Reality vérifier

Testez vos connaissances: Movie Schema

Five rapide questions on schema.org/Movie, the mobile-only carousel, the ItemList wrapper it nécessite, and the Critic Examiner deprecation. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

My writing on ce topic

I haven’t publié a standalone Movie schema guide of my propre — so plutôt que point vous at something que doesn’t exist, the honest déplacer is to send vous to the principal sources ci-dessous and to the connexe structured-data fonctionner on ce site. Pour the broader vocabulary and où Movie fits, voir the Balisage de données structurées and Données structurées hubs; pour the AI angle, Balisage de données structurées pour AI.

From autour the industry

• Movie carousel (Movie) données structurées (Recherche Google Central) — the authoritative référence pour requis/recommended properties and the mobile-only restriction.
• Search gallery (Google) — confirms “Movie carousels with director information” as a genuine listed fonctionnalité.
• Critic Examiner données structurées (Google) — the deprecated, separate couche; l’URL now redirections to the changelog.
• Moteur de recherche Roundtable’s coverage of Google’s Critic Examiner deprecation — the relayed source pour Google’s stated reasoning (“wasn’t useful for the ecosystem at scale”) and the “leave the markup in place” guidance.

A remarque on the coverage gap ce fills: the popular schema plugins under-serve two facts que matter la plupart ici. Yoast listes Movie among covered types but doesn’t flag the mobile-only restriction — so implementers walk away expecting a desktop card que doesn’t exist. AIOSEO omits Movie from its roundup entirely, and neither plugin’s docs clearly separate the still-live carousel from the deprecated Critic Examiner couche. Les deux gaps are exactly ce que ce article is ici to fermer: the carousel is mobile-only, and Critic Examiner is a separate, retired fonctionnalité — pas evidence que Movie schema itself is dead.

Journal des modifications