What Is Movie Schema?

Movie Schema is structured data that identifies films in an ordered list so eligible mobile search results can present a site-specific movie carousel.

The content entity is Movie, while ItemList and ordered ListItem objects provide carousel structure. Every movie needs an accurate title and representative poster image. Director, release date, review and aggregate rating data can add useful context when visible and truthful. This feature serves list discovery - such as a collection of notable films - not a generic video player, a knowledge-panel claim or a watch-button integration. Valid markup establishes only technical eligibility; it does not guarantee a carousel, ranking position or click-through increase. The documented movie carousel is a mobile experience.

1. Identify the exact page, asset, entity or relationship described in this section.
2. Inspect the live implementation and retain the observed evidence.
3. Compare the observation with the intended meaning and its primary specification.
4. Correct any mismatch, then retest the live result.
5. Record the accountable owner and review date.

• Create a real movie collection.
• Use accurate film identity.
• Preserve visible list order.

Primary specification: Schema.org definition for Movie.

Movie Schema works best when an authentic editorial list maps cleanly to identifiable film entities.

Movie carousel markup belongs on pages that visibly list multiple movies of the same content type, using either a summary-page or all-in-one-page architecture.

A summary page might list “Best Science Fiction Movies of 2026” and link each entry to a dedicated movie detail page on the same domain. An all-in-one page can contain the full information for every movie and link to visible anchors on that page. A single movie review does not form a carousel, nor does a category page that mixes films, television series, games and books. The list must contain at least two ListItem objects for the standard carousel structure, and every structured item shown in the list must also be represented to users.

• The exact page, asset, entity or relationship covered by this section
• The live implementation rather than an editor-only preview
• The primary specification or first-party record defining the expected behavior
• The validation result, accountable owner and review date

1. Classify the page architecture.
2. Confirm at least two movies.
3. Keep one item type.
4. Render the full structured list.

Choose a carousel architecture only when the visible page genuinely presents an ordered collection of movies.

Each Movie in the carousel needs an accurate name and a crawlable high-resolution image that represents that film.

The name should be the film title, not the review headline, ranking number, ticket price or promotional slogan. The image should use a poster-like 6:9 aspect ratio or a close crop that remains eligible, and the URL must be crawlable and indexable. Supported formats include common web image types documented for the feature. Avoid logos, generic cinema graphics, cast photos that do not identify the film or a poster borrowed from another release. Optional facts such as director, release date and ratings improve context but cannot repair a wrong title or image.

1. Identify the exact page, asset, entity or relationship described in this section.
2. Inspect the live implementation and retain the observed evidence.
3. Compare the observation with the intended meaning and its primary specification.
4. Correct any mismatch, then retest the live result.
5. Record the accountable owner and review date.

• Use the official display title.
• Provide a relevant poster.
• Test image crawlability.

Required movie identity is complete when title and poster unmistakably describe the same film users see in the list.

ItemList contains the movie collection, and each ListItem assigns a unique one-based position plus the correct destination or nested Movie entity.

The position determines carousel order, so values should begin at one, remain unique and match the visible ranking. On a summary page, each ListItem uses its position and a unique URL for a same-domain movie detail page. On an all-in-one page, each list entry nests a Movie and uses a URL that points to a nearby visible anchor on the current page. Do not use duplicate destinations, skip hidden entries or let client-side sorting change the page without regenerating structured positions. Pagination requires a deliberate editorial and technical model rather than repeating position one across every page.

• The exact page, asset, entity or relationship covered by this section
• The live implementation rather than an editor-only preview
• The primary specification or first-party record defining the expected behavior
• The validation result, accountable owner and review date

1. Enumerate visible movies.
2. Assign one-based positions.
3. Validate every destination.
4. Retest sorting and pagination.

The list is reliable when each position resolves to the same movie and order that the visitor sees.

Use high-resolution, crawlable poster images near a 6:9 ratio that accurately represent the specific movie and release.

A theatrical poster or authorized key art is usually more suitable than a wide trailer thumbnail. Alternate cuts, remakes and films sharing a title need artwork that matches the structured release. Avoid tiny images, CSS backgrounds unavailable to crawlers, expiring signed URLs and assets blocked by robots rules. Rights and licensing still apply; schema does not grant permission to republish artwork. The poster should also be visible or clearly associated with the movie on the page. Broader asset discoverability can follow Image SEO, while the carousel-specific crop remains a separate eligibility concern.

1. Identify the exact page, asset, entity or relationship described in this section.
2. Inspect the live implementation and retain the observed evidence.
3. Compare the observation with the intended meaning and its primary specification.
4. Correct any mismatch, then retest the live result.
5. Record the accountable owner and review date.

• Match title and release.
• Target the documented ratio.
• Keep URLs stable and crawlable.
• Verify usage rights.

Poster optimization is finished when the asset is accessible, licensed, high quality and unambiguously tied to that movie.

Add director, release date, reviews and aggregate ratings only when each value is visible, correctly scoped and supported by source records.

The director is a Person with the correct name; movies with multiple credited directors can include the applicable people. dateCreated represents the movie’s release date, not the article publication date, streaming availability date or page update timestamp. A nested Review needs a valid author and rating data, while AggregateRating must summarize genuine evaluations using accurate counts and scale. Follow Review Schema and Aggregate Rating Schema rather than copying scores from an unrelated source without permission or context.

• The exact page, asset, entity or relationship covered by this section
• The live implementation rather than an editor-only preview
• The primary specification or first-party record defining the expected behavior
• The validation result, accountable owner and review date

1. Verify film credits.
2. Separate release and article dates.
3. Trace review authorship.
4. Recalculate rating aggregates.

Optional movie facts improve trust only when their entity, date and rating scope are exact.

Movie identifies the creative film, VideoObject describes a specific video asset, and Media Actions power watch experiences through a separate integration.

A movie page may embed a trailer, but the trailer is a VideoObject, not the movie itself. The film entity can relate to video media without collapsing those identities. A movie carousel helps users explore an ordered movie list; it does not create a play button or streaming entitlement. Watch actions require media-feed and deep-link work beyond the Movie carousel documentation. A knowledge-panel claim is also a different process. Use Video SEO for trailer discovery and keep playback availability, subscription requirements and regional restrictions accurate in the systems that own them.

1. Identify the exact page, asset, entity or relationship described in this section.
2. Inspect the live implementation and retain the observed evidence.
3. Compare the observation with the intended meaning and its primary specification.
4. Correct any mismatch, then retest the live result.
5. Record the accountable owner and review date.

• Separate film and video assets.
• Treat watch actions as another integration.
• Keep availability claims out of the carousel.

Use each vocabulary for its real job instead of expecting Movie markup to create playback or ownership features.

Common mistakes include marking a single page as a carousel, mixing media types, using landscape thumbnails, duplicating positions and attaching ratings or dates to the wrong movie.

Publishers may create an ItemList with one film or include TV series beside movies because the page calls everything “watchable.” Summary pages sometimes point to external streaming services rather than unique same-domain detail URLs. All-in-one pages may omit anchors or use URLs that do not identify visible items. Templates can repeat position one, retain removed films, copy the same poster across remakes or use the article date as dateCreated. Another error is assuming the carousel appears on desktop even though the documented experience is mobile-only. These problems require semantic and rendered-page checks.

• The exact page, asset, entity or relationship covered by this section
• The live implementation rather than an editor-only preview
• The primary specification or first-party record defining the expected behavior
• The validation result, accountable owner and review date

1. Validate list cardinality and type.
2. Open every URL or anchor.
3. Compare title, poster and release.
4. Test rendered mobile output.

The most serious error is a list item that sends users to a different title, release or content type than the structured movie.