Why Google Isn't Indexing Your Videos

A well-produced, correctly marked-up video can appear nowhere in video results. The explanation is usually an editorial rule very few sites have absorbed.

Photo by Maik Winnecke / Unsplash

A well-produced video, embedded in a well-written page, and nowhere to be found in Google's video results. The situation is ordinary, and the explanation is rarely the one people reach for: in most cases the problem is neither the content nor the markup, but an editorial rule Google has applied since the end of 2023 and which very few sites have absorbed.

The subject is worth rebuilding from the foundations, because it is cluttered with advice that has expired. Several commonly recommended sitemap tags are officially deprecated, seven error reasons still listed in tutorials no longer exist, and the single most widespread belief in the field — that Google reads your subtitle files — has no documentation behind it at all.

Three required properties, and no more

Start with what surprises people most. Google requires exactly three properties on a VideoObject: the video's name, the URL of its thumbnail, and its upload date. Everything else — description, duration, content URL, embed URL — is recommended rather than required, contrary to a firmly established assumption.

That is not an argument for doing the minimum. Google states that contentUrl, which points at the video file itself rather than the page hosting it, is the most effective way for it to fetch the content, and recommends supplying it where possible, with embedUrl as a fallback. That fetch is what makes video previews and automatic key moments possible: the optional properties determine feature eligibility even though their absence does not block indexing.

Two formats deserve particular care because they generate avoidable errors. Upload date is expressed in ISO 8601, and Google recommends including the timezone, failing which it applies its own crawler's timezone — a correct date can therefore end up shifted. Duration is also ISO 8601, written as PT00H30M5S for thirty minutes and five seconds, not as a number of seconds. Note the apparent inconsistency with video sitemaps, where duration is counted in seconds.

One observation from the field, which is not anecdotal: structured data blocks get copied from one article to the next, and pages regularly reach production with an upload date still containing template text of the "to be completed" variety. The crawler does not infer what was meant — the property is invalid and the video loses its rich result eligibility. The Rich Results Test catches it immediately, provided somebody runs it.

The rule that disqualifies most pages

Here is the decisive point, and the reason so many correctly marked-up videos never appear anywhere. Google indexes a video only from a watch page, defined as a page whose primary purpose is to show a single video.

The documentation gives examples in both directions and they leave no room for interpretation. Watch pages include a video landing page, an episode page for a series, a news video page, a sports highlight page. Not watch pages: a blog post commenting on an embedded video, a product page carrying a 360-degree video, a category page listing several videos of equal prominence, a film review with the trailer embedded.

Which means the most common configuration on editorial sites — a substantial article with an illustrative video embedded — is structurally excluded from video results. This is not a penalty: Google states that such a page remains perfectly eligible for text results and for image results with a video badge. It simply loses access to Video mode and the associated features.

Three further requirements complete the rule, and each one eliminates pages. The watch page must be indexed, and Google adds a condition that is rarely quoted: an indexed page must already be performing well in Search before its video can be considered for indexing. The player must not be hidden behind other elements. And above all, the video must not depend on a user action to load — no scrolling, no clicking, no typing. A video behind a tab, an accordion, a modal, or behind a preview image that has to be clicked before the player appears, is not indexable as video. That last case carries its own error reason in Search Console.

Thumbnails, the silent failure

Thumbnails account for seven of the error reasons in the video indexing report, which tells you where the trouble concentrates.

The requirements are specific. Accepted formats are BMP, GIF, JPEG, PNG, WebP, SVG and AVIF. The minimum size is 60 by 30 pixels, with larger preferred — and note that Google publishes neither a maximum nor a recommended aspect ratio, contrary to the 1280 by 720 figure quoted everywhere. The file must be reachable by both the standard and the image crawler, and available at a stable URL: Google explicitly warns that some delivery networks use rapidly expiring URLs, and that a thumbnail whose address changes too often prevents indexing. Finally, at least 80 % of the pixels must have an alpha value above 250, which effectively rules out partially transparent thumbnails.

A less familiar constraint deserves a mention: Google accepts four thumbnail sources — the poster attribute, the sitemap tag, the structured data property and the Open Graph metadata — and expects the same URL in all of them. An inconsistency between sources is itself a failure reason.

Video sitemaps are not obsolete

You will regularly read that structured data has superseded video sitemaps. Google's documentation says the opposite: it recommends video sitemaps while also supporting mRSS feeds, and places the three formats — structured data, sitemap, Open Graph — on equal footing.

A video sitemap requires four elements per video: thumbnail, title, description limited to 2,048 characters, and either the content URL or the player URL. HTML entities must be escaped or wrapped. Several optional tags remain useful, notably duration in seconds between 1 and 28,800, publication date, regional restrictions, family-friendly status and a live indicator.

A handful of tags, on the other hand, are officially deprecated and still circulate in tutorials: category, gallery, price, TV show, along with the autoplay and embed-permission attributes on the player tag. Keeping them achieves nothing.

Key moments

Google detects segments on its own and may display key moments with no intervention from you. Markup exists to take control back, and the documentation states that manually defined moments take priority.

Two methods coexist. Clip markup means declaring each segment yourself with a title, a start offset in seconds and a URL pointing at that exact moment; it works in every language where Google Search operates. SeekToAction means describing your timestamp URL pattern and letting Google find the segments itself; it is limited to about a dozen languages.

Three shared eligibility conditions eliminate a share of candidates. The video must be reachable by a deep link to somewhere other than its start. The markup must sit on a page where the user can actually watch the video. And the total duration must be at least thirty seconds.

A YouTube video embedded on your own site

The situation is more favourable than generally believed. Google states that when a site embeds a video from a third-party platform, it may index that video both on your page and on the platform's equivalent page, and that both versions may appear in video features provided the pages meet the indexing criteria. It goes on to recommend supplying structured data on your embedding page and including those pages in your video sitemaps.

What Google nowhere states is which of the two pages it favours in a conflict, or how attribution is decided. The widespread claim that "YouTube always wins" has no official source. Search Console help notes only that where several URLs are judged equivalent, Google may combine their metadata, taking the title from one and the thumbnail from another.

Subtitles: what Google says, and what it does not

This is where collective belief diverges most sharply from the documentation, and it is worth saying plainly.

Google's video best practices page contains no mention of transcripts, captions or subtitles. The transcript and caption properties do exist in the schema.org vocabulary, but appear in neither Google's required nor its recommended list. And Google's official list of indexable file types mentions no subtitle format — neither WebVTT nor SubRip.

The idea that Google reads your subtitle files is therefore a community hypothesis, never confirmed. What is documented is that Google uses the text of the page, and that it can fetch and analyse the bytes of the video file to power previews and automatic key moments. The practical consequence is simple and reassuring: publishing the transcript as visible text on the page is ordinary indexable HTML, and therefore certain to count. It is the only advice in this section resting on something solid, and it also happens to be the most effective.

On YouTube's side, the official argument for subtitles is accessibility and audience reach, never ranking. The same help pages note, on video tags, that they mainly compensate for common spelling mistakes — which should settle a different debate.

Reading the Search Console report

The video indexing report shows how many videos are eligible for video features and why the others are not. Two clarifications prevent false diagnoses.

First, the report covers indexed pages only: a page that is not indexed, including because it is not canonical, does not appear at all, which explains most discrepancies between the number of real videos and the number displayed. Second, the last-crawled date shown in an issue's detail refers to the page, not to the video.

The report also supplies the single most useful piece of information on the whole subject: for each URL, whether Google considers the page a watch page. A negative answer is spelled out as the page containing other meaningful content in addition to the video — that is the diagnosis you are looking for, and it is explicit.

One last point, because it still distorts a lot of audits: seven former error reasons concerning video format, position in the page or size were removed in December 2023 and folded into the single watch-page reason. Articles that still list them are describing a report that no longer exists.

Frequently asked questions

Do I need a dedicated page for every video?

It is the only route to video result eligibility, since Google indexes videos solely from pages where they are the main content. Nothing prevents publishing the same video on a dedicated page and inside a longer article: the first targets Video mode, the second targets text results.

Can a click-to-load video be indexed?

No. Google explicitly asks that the video not depend on a user action to load, and the case of a clickable image that summons the player carries its own error reason. The player must be present at its real size and position when the page loads.

Does markup guarantee a rich result?

No, and Google says so itself: adding markup does not guarantee any particular feature in results. Markup creates eligibility, it does not decide.

Should the upload date include a timezone?

Google recommends it without requiring it, noting that in its absence the crawler's own timezone applies. Depending on your publishing time, the difference can shift the displayed date by a day — so include it.