Video SEO

TL;DR — Video SEO splits in two: helping search engines find and show the videos on your own website, and ranking videos on YouTube itself. They need different work, so this hub keeps them straight and links to the details.

The two halves of video SEO

When people say “video SEO” they usually mean one of two different things.

The first is video on your own site — a video embedded on a page you control. Before markup or sitemaps come into it, Google has to be able to find the video at all: it needs a normal <video>, <iframe>, or <object> element in the rendered HTML, not a player that only appears after a click or a video loaded purely from a URL fragment. Once discovery works, the goal is to make that video eligible to appear as a video result, which means having a real, watchable video, a representative thumbnail, and video structured data so search engines understand what the video is. A video sitemap helps with discovery too.

If you embed a third-party player — YouTube, Vimeo, and similar — Google may index both your own watch page and the hosting platform’s equivalent page for the same video. Neither placement is guaranteed just because you embedded it; it’s still worth adding structured data and including the page in your sitemap for your own watch page.

The second is YouTube SEO — treating YouTube as the search engine it is and getting your videos found there through titles, descriptions, transcripts, and engagement.

This hub covers both; the deep dives sit under it.

TL;DR — On-site video SEO is a technical eligibility problem: Google’s actual indexing requirements are an indexed watch page, a visible embed, and a stable thumbnail — VideoObject markup and sitemaps are recommended, not required, and the video still has to be the main content of its page, not a decorative clip. Search Console’s Video indexing report tells you which videos failed and why. YouTube is a completely separate ranking system.

What makes a video eligible for a video result

Google separates this into indexing requirements and recommended metadata, and the two get collapsed together more often than they should. The indexing requirements are strict: the watch page itself has to be indexed before its video can be considered, the video has to be embedded on that page and not hidden behind other elements, and it needs a valid thumbnail at a stable URL. Being playable in a browser isn’t proof Google can fetch the file — features like previews and key moments depend on Google reaching the video bytes directly, not just on a visitor being able to press play.

Separately, to count as a dedicated watch page at all — the prerequisite for video results, Key Moments, and the Live Badge — the video has to be the main reason someone’s visiting the page. A dedicated video-landing page or a sports-highlight page counts, because watching that one video is why the visitor is there. A blog post that happens to embed a video, or a category page listing several videos side by side, does not — the video is secondary to the rest of the page, no matter how clean the markup is. That’s the condition teams miss most; a hero background loop or a sidebar clip won’t qualify either.

VideoObject structured data, video sitemaps, and Open Graph tags aren’t indexing requirements in Google’s own docs — they’re recommended metadata that makes discovery easier and unlocks specific features. Skipping structured data doesn’t disqualify an otherwise-eligible watch page, but it does forfeit the extra signals that depend on it.

A worked VideoObject

VideoObject has three required fields per Google’s structured-data reference — name, thumbnailUrl, and uploadDate. description, duration, contentUrl, and embedUrl are recommended, not required — they don’t gate eligibility on their own, but they materially improve it and unlock extra features:

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "How to set up hreflang tags",
  "description": "A five-minute walkthrough of building a correct hreflang set.",
  "thumbnailUrl": "https://example.com/thumbs/hreflang.jpg",
  "uploadDate": "2026-07-13T08:00:00+00:00",
  "duration": "PT5M12S",
  "contentUrl": "https://example.com/video/hreflang.mp4",
  "embedUrl": "https://example.com/embed/hreflang"
}

uploadDate should carry a timezone, duration is ISO 8601 (PT5M12S is 5 minutes 12 seconds), and you should supply at least one of contentUrl (the raw file) or embedUrl (the player) so Google can fetch or embed the video.

The Video indexing report: why videos get excluded

The Video indexing report in Search Console is the feedback loop. It shows which pages Google found a video on, which it indexed, and — most usefully — why others were excluded. The recurring exclusion reasons map straight back to the eligibility rules: no prominent video detected, the video isn’t the main content of the page, no valid thumbnail, or the video is too small. Treat those messages as a checklist, not an error log.

YouTube is a separate ranking system

YouTube SEO shares almost none of the above. YouTube runs its own ranking system where discovery comes from the title, description, tags, the transcript, the thumbnail, watch time, and engagement — none of which is the structured-data work that governs on-site video. Optimizing a YouTube channel and optimizing a self-hosted video are different jobs that happen to share the word “video.”

And on either surface, meeting every requirement only makes a result possible. An indexed watch page, a fetchable video, a stable thumbnail, and valid metadata don’t guarantee indexing, ranking, a video thumbnail in the results, previews, key moments, or traffic.

Video SEO covers two distinct surfaces. (1) On-site video: Google first has to discover the video in rendered HTML — no interaction-gated or fragment-only loading — then its watch page must be indexed, the video visibly embedded and not hidden, and a thumbnail available at a stable URL; those are Google’s actual indexing requirements. VideoObject structured data, video sitemaps, and a dedicated watch page (the video is the page’s main reason for existing, not a decorative clip) aid eligibility and unlock features like key moments, but only three VideoObject fields — name, thumbnailUrl, uploadDate — are required; description and the rest are recommended. Third-party embeds (YouTube, Vimeo) can leave both the publisher’s and the platform’s page indexed, with neither guaranteed. Search Console’s Video indexing report is the diagnostic for all of this. (2) YouTube SEO: ranking within YouTube’s own search via titles, descriptions, transcripts, thumbnails, and engagement — a separate system from on-site indexing. Meeting every requirement on either surface makes a result possible, not guaranteed.

Changelog