VideoObject Schema for Healthcare YouTube — Getting Into Video Results
What Google sees without VideoObject schema
An embedded YouTube video without schema is, to Google, just an iframe on a page. The page competes as a text page. YouTube itself indexes and ranks the video separately, but the two indexes do not merge on the shared query unless the on-page context tells Google they belong together. The signal that produces the merge is VideoObject schema.
The evidence is easy to reproduce: take an already-ranking blog on a healthcare topic, add an embedded YouTube video without schema, and measure video rich-result appearance in GSC's "Search appearance" filter over 30 days. Now add VideoObject schema on a matched page. Within 8 to 21 days, the schema-marked page shows video appearances rise sharply while the control does not. We have run this pattern on 60+ page pairs.
The minimum viable VideoObject payload
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "PCOS symptoms explained — a gynaecologist's guide",
"description": "A named gynaecologist explains the six PCOS symptoms most Indian women miss, why they are often mis-attributed, and when to see a specialist.",
"thumbnailUrl": "https://i.ytimg.com/vi/VIDEO_ID/maxresdefault.jpg",
"uploadDate": "2026-08-12T09:00:00+05:30",
"duration": "PT8M42S",
"contentUrl": "https://www.youtube.com/watch?v=VIDEO_ID",
"embedUrl": "https://www.youtube.com/embed/VIDEO_ID"
}
</script>
That is the floor. Every field is required for Google's video rich result to render. Missing any single field disables the rich result on the page.
What the AIO Lab race needs on top of the floor
Getting a video into the video-in-page rich result is one game. Getting the video cited inside a Google AI Overview is a harder game with two additional signals:
- hasPart — chapter marks. A well-marked VideoObject includes a hasPart array of Clip objects, each with a name that maps to a question the paired text page answers. This is what tells the AIO extractor which timestamp answers which question.
- transcript. A machine-readable transcript field lets the AIO extractor confirm the video actually answers the question the chapter promises. Without a transcript, chapter marks are unverifiable and rarely used.
The full healthcare VideoObject pattern with chapters and transcript
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "PCOS symptoms explained — a gynaecologist's guide",
"description": "A named gynaecologist explains the six PCOS symptoms most Indian women miss.",
"thumbnailUrl": "https://i.ytimg.com/vi/VIDEO_ID/maxresdefault.jpg",
"uploadDate": "2026-08-12T09:00:00+05:30",
"duration": "PT8M42S",
"contentUrl": "https://www.youtube.com/watch?v=VIDEO_ID",
"embedUrl": "https://www.youtube.com/embed/VIDEO_ID",
"hasPart": [
{"@type": "Clip", "name": "What is PCOS", "startOffset": 12, "endOffset": 95, "url": "https://www.youtube.com/watch?v=VIDEO_ID&t=12s"},
{"@type": "Clip", "name": "Six PCOS symptoms often missed", "startOffset": 95, "endOffset": 268, "url": "https://www.youtube.com/watch?v=VIDEO_ID&t=95s"},
{"@type": "Clip", "name": "When to see a gynaecologist", "startOffset": 268, "endOffset": 410, "url": "https://www.youtube.com/watch?v=VIDEO_ID&t=268s"}
],
"transcript": "Full transcript text here…",
"author": {"@type": "Person", "name": "Dr Firstname Lastname", "sameAs": ["https://www.linkedin.com/in/…"]}
}
</script>
The chapter names are questions or question-fragments, not marketing headlines. The startOffset values match the YouTube chapter timestamps exactly. The author is a resolvable Person entity — LinkedIn at minimum, Wikidata if the doctor has crossed that threshold.
Where the schema goes and what it must match
The schema ships in a script tag inside the head or body of the page that embeds the video. The name, description, and duration fields must match the YouTube video's own metadata exactly. Any divergence — a different title on-page, a description shortened to fit — is treated by Google's structured-data policy as a mismatch and can trigger schema demotion.
The video also has to be genuinely embedded on the page (or the contentUrl reachable to Googlebot). Ghost schema — VideoObject pointing at a YouTube video that isn't on the page — is a policy violation that stalls the entire domain's video rich-result eligibility. Do not do it.
The pairing pattern that compounds
One text article on your website, one YouTube video on the same anchor topic. Both are schema-tagged. The text article carries FAQPage schema; the video page carries VideoObject with chapters. The two are interlinked — the article embeds the video, and the video description links back to the article. In this pattern, Google's video ranker and text ranker both read the pair as coherent topical coverage, and AIO citations start rendering both the text and the video from the same brand.
This is the pairing pattern YODA was built around. Text alone on the topic underperforms; video alone underperforms. The pair compounds because both indexes reinforce each other. On the 60+ pairs we run in production, the pair earns 2.1 to 3.4 times more qualified sessions than either half alone.
The healthcare-specific gotchas
- Do not include patient testimonials in the video. Even a compliant on-screen doctor discussion becomes a policy exposure the moment a testimonial clip is spliced in. Compliance risk plus schema demotion risk on healthCondition claims.
- Do not spam MedicalCondition schema on the video page. One MedicalWebPage marker is fine; ten MedicalConditions listed as page subjects reads as spam. Google demotes.
- Avoid claim-heavy descriptions. "The best gynaecologist explains" is a comparative claim. "A named gynaecologist explains" is not. The former risks both NMC and structured-data policy demotion.
- Do not schema-tag old, low-quality videos. If the schema opens Google's video ranker to a video with poor watch-through, the whole domain's video rich-result eligibility can be capped.
What appears when the schema takes effect
- Video-in-page rich result — the blue-link listing for the page shows a video thumbnail. Typically appears in 8 to 21 days after schema validation.
- Video appearance in GSC — the Search appearance filter shows "video" impressions. This is the leading indicator of video ranker eligibility.
- Google video carousel — the page's video appears in the horizontal video carousel on health queries. Typically 4 to 10 weeks after rich-result appearance.
- AIO video citation — the highest-leverage signal. Typically 8 to 14 weeks after full schema, chapters, and transcript are in place.
Audit your healthcare video schema for AIO Lab eligibility
We will pull every video embedded across your site, validate the VideoObject payload, check chapter alignment and transcript presence, and lay out the fix sequence that unlocks the video citation slot. Fixes typically produce first citations inside 60 days.
Explore YODA WhatsApp ICG