docs/sitemap-0.xml declares the Google video sitemap namespace:
xmlns:video="http://www.google.com/schemas/sitemap-video/1.1"
and contains zero <video:video> entries. Namespace boilerplate with nothing in it — the kind of thing that reads as implemented on inspection but does nothing.
A repo-wide grep for VideoObject returns no hits, so there is also no structured-data path. The site has a /research/videos/ page in the sitemap, so there is video content with no machine-readable description of it at all.
Google supports three routes: structured data, Open Graph, or a video sitemap. A video sitemap is optional, not required — the docs call it "a good way to help Google find and understand the video content on your site, especially content that was recently added or that we might not otherwise discover." So the fix is a choice, not an obligation.
Recommended: add VideoObject structured data to the video pages rather than filling in the sitemap. Required properties are only name, thumbnailUrl, uploadDate; contentUrl (pointing at the actual video bytes, not the page) is recommended. It sits next to the content it describes, so it's less prone to drifting out of date than a separately generated sitemap.
Then either populate <video:video> entries or drop the unused namespace — leaving it declared and empty is a false signal to anyone reading the file.
If sitemap entries are preferred, required tags are <video:thumbnail_loc>, <video:title>, <video:description> (≤2048 chars), plus either <video:content_loc> or <video:player_loc>.
Found while auditing video structured data across repos.
https://claude.ai/code/session_013v6uVg33y2w9SrWAmDsWLL
docs/sitemap-0.xmldeclares the Google video sitemap namespace:and contains zero
<video:video>entries. Namespace boilerplate with nothing in it — the kind of thing that reads as implemented on inspection but does nothing.A repo-wide grep for
VideoObjectreturns no hits, so there is also no structured-data path. The site has a/research/videos/page in the sitemap, so there is video content with no machine-readable description of it at all.Google supports three routes: structured data, Open Graph, or a video sitemap. A video sitemap is optional, not required — the docs call it "a good way to help Google find and understand the video content on your site, especially content that was recently added or that we might not otherwise discover." So the fix is a choice, not an obligation.
Recommended: add
VideoObjectstructured data to the video pages rather than filling in the sitemap. Required properties are onlyname,thumbnailUrl,uploadDate;contentUrl(pointing at the actual video bytes, not the page) is recommended. It sits next to the content it describes, so it's less prone to drifting out of date than a separately generated sitemap.Then either populate
<video:video>entries or drop the unused namespace — leaving it declared and empty is a false signal to anyone reading the file.If sitemap entries are preferred, required tags are
<video:thumbnail_loc>,<video:title>,<video:description>(≤2048 chars), plus either<video:content_loc>or<video:player_loc>.Found while auditing video structured data across repos.
https://claude.ai/code/session_013v6uVg33y2w9SrWAmDsWLL