When AI Overviews include a video, two things have to be true: the page has VideoObject structured data describing the video, and the page's robots directives allow video previews. Without both, your video is invisible to AI features, even if it is the best video on the topic.
What Google says
“Help Google find your videos by adding structured data, providing a video sitemap, and ensuring your videos appear in pages where they are the main content.”
Why this matters for AI Overviews
A video on your page is in a strange state from Google's perspective. The video itself often lives on YouTube or Vimeo. Your page is the one that should benefit from it. To bridge that gap, Google needs structured data that tells it which video is embedded, what it is about, how long it is, and where the thumbnail lives.
The two directives and one schema:
max-video-preview:-1. Allows Google to show an unlimited-length video preview. The default cap is short.VideoObjectschema withcontentUrlorembedUrl. Tells Google which video is on the page.- A real thumbnail declared in
thumbnailUrl, at least 1200 px on the long edge.
Without the schema, the video on your page is a black box. Google does not know which YouTube ID corresponds to which page, and the video preview cannot appear in your search result.
We made this exact mistake on our own product demo pages for months. The videos were embedded, the pages were great, no schema was set. The fix took an hour. AI Overview eligibility for video on those pages came back the same week the schema went live.
How to fix it
Step 1: Set the right meta directive
<meta name="robots" content="max-snippet:-1, max-image-preview:large, max-video-preview:-1">
max-video-preview:-1 means no limit on video preview length. Without it, Google may show a static thumbnail only.
Step 2: Add VideoObject schema
For a YouTube embed, the schema should describe what is in the video, not just point to YouTube:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "How to install SiteSpeakAI on a Webflow site",
"description": "Step-by-step walkthrough of installing the SiteSpeakAI chatbot embed on a Webflow site, including custom CSS and event tracking.",
"thumbnailUrl": [
"https://example.com/thumbnails/webflow-install-1200x675.jpg"
],
"uploadDate": "2026-04-12",
"duration": "PT4M32S",
"contentUrl": "https://example.com/videos/webflow-install.mp4",
"embedUrl": "https://www.youtube.com/embed/dQw4w9WgXcQ"
}
</script>
The fields that matter most for AI Overviews:
nameanddescriptionshould describe the video, not just match the page titlethumbnailUrlshould be a real image at 1200 px on the long edgedurationin ISO 8601 format (PT4M32S= 4 minutes 32 seconds)uploadDatein ISO 8601 date format
Step 3: Make the video the main content of its page
Google's video guidance is clear: videos surface best when they are the main content of the page they are on. A video buried below 2,000 words of unrelated text is much less likely to be selected than a video that is the page's primary asset.
The pattern we use: a dedicated page per major video, with the video at the top, a short summary below, and a full transcript or detailed text continuation. The transcript both helps the schema (Google can match description and visible text) and gives users a text alternative.
Step 4: Verify
Use Google's Rich Results Test and paste the page URL. Under the results, you should see "Video" as a detected rich result type, with no errors.
Our AI Overview Checker flags the most common video failures: video present on page but no VideoObject schema, and video present but max-video-preview:-1 not set.
Common mistakes when implementing the fix
VideoObjectschema without a realthumbnailUrl. Without a usable thumbnail, the video cannot surface visually.- Pointing
contentUrlat the YouTube watch page instead of the embed URL. UseembedUrlfor the iframe URL,contentUrlfor the raw video file URL if you have one. - Multiple videos on the same page with one combined schema block. Each video needs its own
VideoObject. durationin human-readable format ("4:32") instead of ISO 8601 (PT4M32S). Schema validators flag this; Google silently ignores the field.- Forgetting that a video page also needs the regular content quality signals. Author, date, transcript, internal links. The video schema is necessary, not sufficient.