Consistent video rich-result and video-search visibility requires four things working together: properly implemented VideoObject structured data with accurate required and recommended properties, a genuinely crawlable and indexable video (both the hosting page and the video file itself accessible to Googlebot), a reliable discovery path via video sitemap or well-linked schema, and the video being real, prominent content on the page rather than an incidental embed. Missing any one of these tends to produce the same symptom, valid-looking schema with no actual rich-result display, which is why treating this as a checklist rather than a single schema-correctness question matters.
The required and recommended VideoObject properties
Google’s Video SEO best practices and VideoObject structured data documentation specify a defined set of properties that matter for eligibility. The required fields are name and description (identifying what the video actually is), plus a thumbnailUrl pointing to an accessible, appropriately sized image, and either uploadDate or the combination of properties Google’s documentation accepts for establishing when the video was published. Beyond required fields, duration (in ISO 8601 format) and contentUrl or embedUrl (pointing to the actual playable video resource, not just the hosting page) are documented as strongly recommended because they’re used directly in how Google surfaces and previews the video in search results. Omitting or malforming any of these doesn’t necessarily throw a hard validation error in every case, but it does reduce the completeness of what Google can use to build a rich video result, which matters for consistent display.
Crawlability of the video file itself, not just the page
This is a distinct requirement from having correct schema, and it’s a common point of failure. The hosting page can be perfectly crawlable and indexed while the actual video file or embed source is blocked by robots.txt, gated behind authentication, hosted on a CDN with bot-restrictive access rules, or served only after a client-side interaction Googlebot’s crawler doesn’t perform. Google’s documented behavior is that it needs to actually access the video resource referenced in contentUrl or verify the embed at embedUrl, so a page with excellent VideoObject markup pointing to a video Googlebot can’t reach will not reliably produce a video rich result, since there’s no way for Google to verify or preview a resource it can’t fetch.
A reliable discovery path
Google’s Video SEO documentation describes video sitemaps (or, alternatively, sufficiently clear structured data discovery on well-linked, crawlable pages) as the mechanism for ensuring Google finds and prioritizes video content for indexing at scale. For sites with a meaningful volume of video content, a video sitemap listing each video URL along with key metadata gives Google a direct, efficient discovery and refresh path, reducing dependency on Google finding and correctly associating video content through incidental crawling alone.
The video must be genuinely primary content on the page
This requirement is explicit in Google’s own Video SEO guidance and is one of the more specific, checkable documented factors in this space: the video needs to be the primary content of the page it’s on, not an ancillary embed on a page that’s mostly about something else. A page whose main substance is a long article with a tangentially related video embedded partway down is a materially weaker candidate for video rich results than a page built specifically around that video, even with identical VideoObject schema on both. This is a genuinely documented requirement, not a hedge-worthy inference, though Google’s own language frames it as guidance/best-practice rather than an absolute, ironclad algorithmic gate, so it should be understood as a strong factor rather than a strict binary pass/fail rule.
Why “meets all requirements” still doesn’t guarantee display
Even with every item above correctly implemented, Google doesn’t guarantee video rich result or carousel display for any given query, since display decisions also depend on competitive SERP factors, query type, and Google’s own algorithmic judgment about what serves a given search best, the same “validity is necessary but not sufficient” pattern that applies across structured data generally. What consistent, correct implementation of the above does is maximize eligibility and remove the self-inflicted failure modes (a blocked video file, missing required properties, an ancillary rather than primary embed) that are the most common practitioner-side reasons video content doesn’t surface, versus factors genuinely outside the site owner’s control.
A hypothetical illustration
Imagine a hypothetical online cooking school, “Hearth & Ladle,” that adds VideoObject schema to all of its recipe-tutorial pages but notices only about a third of them ever appear in video carousel results despite consistent markup. Working through the checklist might reveal the actual split: the videos that do appear are hosted on pages built specifically around a single tutorial video with the recipe text as supporting content, while the ones that don’t appear are embedded partway down long, multi-recipe roundup articles where the video is clearly a secondary element next to substantial unrelated text. In that scenario the schema was never the problem; the video’s role on the page, primary content versus incidental embed, was the deciding factor Google’s guidance flags explicitly.
A practical requirements checklist
- VideoObject JSON-LD with
name,description,thumbnailUrl,uploadDate,duration, andcontentUrl/embedUrlall accurately populated and matching the actual video - Confirm via URL Inspection or direct fetch testing that the video file/embed source itself is not blocked by robots.txt, authentication, or bot-restrictive CDN rules
- Submit or maintain a video sitemap for sites with meaningful video volume, keeping it current as videos are added or removed
- Ensure the video is structurally and visually the primary content of its hosting page, not a secondary element on a page about other subjects
- Verify markup accuracy against Google’s Rich Results Test and monitor actual display performance via Search Console’s video-related search appearance data over time, since ongoing monitoring is the only way to distinguish “eligible but not currently selected for display” from “something in the implementation is actually broken.”
