Implement both a video sitemap and on-page VideoObject structured data for a video-heavy site, keeping the two signals consistent
domain: developers.google.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add VideoObject structured data to each video's host page with the required fields (name, thumbnailUrl, uploadDate/description per current docs) plus contentUrl or embedUrl
Use interactionStatistic for view-count reporting rather than the deprecated interactionCount property
Generate a video sitemap (or maintain an mRSS feed) listing each video's location, thumbnail, title, and description as a complementary discovery signal alongside the on-page markup
Keep the video sitemap's metadata (title, thumbnail, duration) consistent with the corresponding VideoObject markup on the page — conflicting values between the two undermine both
Add Clip/hasPart and SeekToAction markup for long-form videos where you want Google to surface key-moment jump links in search results
Resubmit the video sitemap via Search Console when large batches of video content are added or removed, and monitor indexing via the Video Indexing report
Known gotchas
A video sitemap alone, without on-page VideoObject markup, is a weaker signal — Google documents the two as complementary, not substitutes for each other
The interactionCount property is deprecated; sites still emitting it instead of interactionStatistic and VideoObject's proper structure risk stale/ignored markup
Video content only reachable via JavaScript-rendered players without a resolvable contentUrl/embedUrl can be discoverable in the sitemap but still fail Google's video rich-result eligibility checks
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?