Movie and TV Schema for Entertainment and Streaming Sites

Someone runs a film review site on WordPress. They add Movie schema to every review page, validate it, confirm it passes with no errors, and then wait for that eye-catching movie carousel to appear in Google.

It never does.

They assume something is broken. Nothing is broken. They have simply run into a rule about how the movie carousel works that Google documents clearly but almost nobody mentions: the carousel does not appear on single movie pages, and it does not appear on desktop.

If your schema validates cleanly but no rich result shows up, this is one of several common causes. Our guide on why schema markup is not showing rich results walks through the rest.

Understanding that one rule changes your entire approach. So let’s start there, then work through the rest of Movie and TV schema properly.

Quick answer: Movie schema describes films, TVSeries describes shows, and Episode describes individual episodes. Google’s movie carousel rich result requires an ItemList on a list page (like “Best Sci-Fi Movies of the Year”) and appears only on mobile devices. Only name and image are required per movie. Streaming watch buttons come from a separate limited-access program called Media Actions. On WordPress, a plugin like SchemaEngine AI handles the carousel structure for you.

Get Your Types Right First

Before anything else, you need to pick the correct schema type. This trips up a surprising number of entertainment sites, and using the wrong one undermines everything downstream.

Here is the map:

Content	Use this type
A film	Movie
A TV show as a whole	TVSeries
A single episode	Episode (or TVEpisode)
A season	TVSeason
A cinema	MovieTheater
A screening with showtimes	ScreeningEvent

The most common error is marking up a television series as a Movie. They feel similar, but they are structurally different things. A TVSeries has seasons and episodes nested inside it. A Movie does not. If you tag a show as a Movie, you lose the ability to express that structure, and you send Google a signal that contradicts your actual content.

Same goes for episodes. An individual episode page should be Episode, linked back to its parent TVSeries, not a standalone Movie.

Get this layer right and everything else becomes easier.

The Carousel Rule Nobody Mentions

Now back to the problem from the opening, because this is the highest-value thing in this article.

Google’s movie carousel is that horizontal, swipeable row of film posters with titles and ratings. It is genuinely attractive and it earns attention. But it comes with two hard constraints:

Constraint 1: It requires a list page, not a single movie page.

The carousel is built on ItemList markup. Your page needs to be a curated list of movies, with each film as an item in that list. Think “Top 10 Horror Films of the Decade” or “Best Documentaries on Streaming Right Now.”

A page reviewing one film is not a list. No matter how perfect your Movie schema is on that page, it cannot produce a carousel, because there is nothing to put in a carousel.

Constraint 2: It is mobile only.

Google states this directly in its documentation: the movie carousel is only available on mobile devices. If you have been testing on your desktop and seeing nothing, that alone may explain it.

There are two more rules worth knowing about carousels generally. All items in the carousel must be the same type, so do not mix movies and TV series in one list. And the visible text on your page must match what is in your structured data. If your schema lists ten films but your page only shows eight, that mismatch can disqualify you.

So the practical takeaway: if you want the carousel, build list content. Roundups, rankings, and “best of” pages are your vehicle.

Surprisingly Few Properties Are Required

Here is some good news after all those rules. The required property list for movie carousel items is remarkably short.

Required per movie:

• name: The film’s title.
• image: The poster or a representative image.

That is it. Two fields.

Recommended (and worth adding):

• director: Marked up as a Person.
• dateCreated: The release date.
• aggregateRating: The overall rating, if you host genuine ratings.
• review: Individual reviews, if applicable.

Google’s own guidance notes that providing more than the minimum helps it understand the entity better, which can surface your content for more general searches. So while two fields make you eligible, filling in director, release date, and ratings makes you competitive.

For TV content, TVSeries supports similar core fields plus structural ones like numberOfSeasons, numberOfEpisodes, and links to seasons and episodes.

What a Carousel Actually Looks Like in Code

Here is the shape of it. Notice that the outer structure is an ItemList, and each movie sits inside as a ListItem with a position.

json

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": {
        "@type": "Movie",
        "name": "The Long Winter",
        "image": "https://example.com/posters/long-winter.jpg",
        "dateCreated": "2022-11-04",
        "director": {
          "@type": "Person",
          "name": "Ana Reyes"
        },
        "aggregateRating": {
          "@type": "AggregateRating",
          "ratingValue": 4.4,
          "ratingCount": 812
        }
      }
    },
    {
      "@type": "ListItem",
      "position": 2,
      "item": {
        "@type": "Movie",
        "name": "Signal Fire",
        "image": "https://example.com/posters/signal-fire.jpg",
        "dateCreated": "2023-06-16",
        "director": {
          "@type": "Person",
          "name": "Tom Aldridge"
        }
      }
    }
  ]
}

The position values matter. They tell Google the order your list is meant to appear in, so keep them sequential and matching your visible ranking.

This is a good example of nested schema markup in action. You have a list containing items, each containing a movie, each containing a person and a rating. Once you are comfortable with that pattern, most complex schema becomes far easier to reason about.

What About Streaming Sites and Watch Buttons?

If you run a streaming platform, you have probably seen those “Watch on” buttons in Google search results and wondered how to get them.

Straight answer: that is a different feature with a different door.

Watch buttons come from Media Actions, a separate Google program for media providers. It is not something you achieve by adding WatchAction markup to your WordPress pages and hoping. Like several of Google’s provider-level features, it involves onboarding and is aimed at platforms that actually control a viewing catalog.

Similarly, if you want to claim a specific movie in a Knowledge Panel, that runs through Google’s entity verification process, not through page markup alone.

We mention this so you do not spend weeks chasing a feature through the wrong channel. If you are a review site, blog, or smaller entertainment publisher, the carousel and rich result path described above is your realistic route. If you are an actual streaming provider, look into Media Actions directly.

Doing This in WordPress

Two paths, and they diverge quickly once you have more than a couple of pages.

By Hand

You can write the ItemList JSON-LD yourself. The example above is a working template. For one roundup post, it is fine.

The friction is real, though. Every roundup you publish means building a fresh nested list. Every time you update a ranking, add a film, or swap positions, you are editing JSON and renumbering position values. Every director and rating is another nested object. Miss a bracket in a ten-film list and the whole thing silently fails validation.

For a site that publishes roundups regularly, this becomes a recurring tax on your time.

With a Schema Plugin

For most WordPress users, a plugin is the practical answer. It generates the ItemList structure, nests each movie correctly, and keeps positions in sync as your lists change.

This is what SchemaEngine AI is built for. Instead of hand-assembling carousel markup for every roundup, you can generate accurate Movie, TVSeries, and Episode schema, wrap it in a valid ItemList when you need a carousel, link directors and actors as proper Person entities, and validate everything in real time. It supports manual control for those who want it, plus AI-assisted generation that reads your page and structures it correctly. As your lists grow and change, the markup keeps up without you touching code.

👉 Good Read: How to add schema markup without coding

Mistakes That Cost Entertainment Sites Visibility

Expecting a carousel on a single movie page. The big one. Carousels need list pages with ItemList markup.

Testing only on desktop. The movie carousel is mobile only. Check on a phone or with a mobile user agent.

Using Movie for a TV show. Use TVSeries for shows and Episode for episodes. The types are not interchangeable.

Mixing types in one carousel. All items in a single carousel must be the same type. Do not combine movies and series in one list.

Structured data that does not match the page. If your markup lists films your page does not visibly show, or your rankings differ, that inconsistency can disqualify the whole thing.

Fabricating ratings. Only mark up genuine ratings from your own site. Invented or scraped ratings violate Google’s guidelines and can trigger a manual action.

Skipping validation after edits. Update a list and you have changed the markup. Re-run the Rich Results Test each time.

Why This Matters More for AI Discovery

Now for the part that is growing fastest, and it applies whether or not you ever earn a carousel.

Entertainment is one of the most natural categories for conversational search. People ask AI assistants things like:

“What are some good sci-fi movies from the last five years?”

“Which TV series should I watch if I liked this one?”

“Who directed that film about a coastal town?”

To answer, systems like ChatGPT, Google AI Overviews, Gemini, and Perplexity need structured facts: title, director, cast, release year, genre, rating. They cannot reliably pull those from flowing review prose that describes a film’s “haunting atmosphere and quiet devastation.”

A film page with clean Movie schema is a machine-readable entity. The AI knows exactly what the title is, who directed it, when it came out, and how it was rated. That makes your page far more likely to be the source it draws from and cites.

There is a compounding benefit for review sites specifically. When your films and shows are structured and your reviews are tied to a properly marked-up author, you build a recognizable entity around your publication. Over time, that is what helps an AI treat your site as a reliable source on film rather than one more page of text.

The carousel is mobile only. Being understood by AI is everywhere.

Let SchemaEngine AI Handle the Structure

Building valid ItemList carousels, choosing the right type for films versus series versus episodes, nesting directors and actors as entities, keeping positions accurate, matching markup to your visible rankings, and validating after every update is ongoing technical work. For a site that publishes entertainment content regularly, it adds up fast.

SchemaEngine AI takes it off your plate. It generates accurate Movie, TVSeries, and Episode schema, assembles valid carousel markup when you need it, links people and organizations into a clean entity graph, and validates everything in real time, so your entertainment content is ready for rich results and AI recommendations. Whether you prefer manual control or AI-assisted generation, your markup stays correct as your lists evolve. Your existing content stays exactly where it is.

Frequently Asked Questions

Wrapping Up

Movie and TV schema rewards precision. Pick the right type for your content, understand that carousels live on list pages and show on mobile, keep your markup matched to what visitors actually see, and validate after every change.

If you publish roundups and rankings, you have a real shot at the carousel, and it only takes two required fields per film to be eligible. If you run a streaming platform, Media Actions is a separate conversation worth having directly with Google. And regardless of which category you fall into, clean structured data is quickly becoming how your films and shows get recommended by AI.

The rules are specific, but they are learnable, and most of your competitors have not learned them.

If assembling nested carousel markup for every roundup is not how you want to spend your publishing time, SchemaEngine AI can generate, structure, and validate it automatically, so your entertainment content is understood everywhere it counts.