Video Indexing: complete guide

Diagnose watch-page, thumbnail, prominence, video-fetch, and metadata indexing problems.

Partially automatable Advanced

Search Console's Video indexing report answers a two-stage question: did Google index a page where it detected a video, and did it index one video from that page? It separates page-indexing failures from video-specific failures and identifies the most likely video candidate on each reported page.

The report counts indexed pages with detected videos, not a definitive inventory of unique video assets. Google indexes no more than one video per page, can see the same video on several pages, and may select a different video than the one a site owner expects.

This guide reflects Google's documentation on July 18, 2026.

The indexing sequence

A video cannot be indexed from a page unless the prerequisite stages succeed:

Google discovers the watch-page URL.
Google can crawl, render, and index that page.
Google selects that page as canonical.
Google detects a video in the rendered page.
Google recognizes the page as a watch page whose main purpose is showing one video.
Google can obtain a valid thumbnail and sufficient video information.
Google selects and indexes one video from the page.

The report begins only after the hosting page is indexed and Google detects a video. A page that is not indexed, or an indexed page where Google detects no video, is absent from the report rather than counted under No video indexed.

What the report counts

The top-level chart has two page states:

State	Meaning
Video indexed	Google indexed the page and one video found on that page.
No video indexed	Google indexed the page and detected at least one video, but indexed none of them.

These are page counts with a selected video status. They are not unique-video counts.

Totals diverge from a site's video catalog when:

Several videos appear on one page; Google reports only one selected candidate.
The same video is embedded on several indexed pages.
A page is non-canonical or otherwise not indexed.
Google indexes the page but cannot detect its video.
Google has not discovered or recrawled the watch page.

Search Console explicitly cannot report the total number of unique videos indexed across a site, every video Google can or cannot index, or every indexed page associated with a specific video.

Comprehensive totals do not mean a complete URL export

Google describes the Video indexing report as one of the reports that provides comprehensive totals, but visible example lists can still be limited to 1,000 URLs. Use chart totals for population-level monitoring and examples for diagnosis; do not treat the example export as a complete watch-page inventory.

What qualifies as a watch page

For video indexing, a watch page is a page whose main purpose is to let a user watch one video.

Typical watch pages include:

A dedicated video landing page.
A TV episode player page.
A news video watch page.
A sports highlight or event clip page.

These are generally not watch pages:

A blog article where a video supplements the text.
A product page with a demonstration or 360-degree video.
A category page listing several equally prominent videos.
A review page containing a trailer.

The same asset can appear on both a dedicated watch page and a supporting article or product page. The supporting page can still appear as a text result or an image result with a video badge, but it is not thereby eligible for video indexing as a watch page.

Page layout is evidence, not a markup switch

There is no structured-data property that forces Google to classify a page as a watch page. The rendered page should make the single video the primary purpose and prominent content.

Use:

A unique page title and description about that video.
One clearly primary player available when the page loads.
Supporting text that describes the video rather than displacing it as the page's main purpose.
Stable, indexable URLs and self-consistent canonical signals.

Do not remove useful transcripts or accessibility content merely to reduce text. The relevant question is why the user visits the page, not whether the HTML contains a certain word count.

Video discovery requirements

Google can discover players referenced through common HTML elements such as video, embed, iframe, and object.

For JavaScript players:

The video container must appear in rendered HTML.
Do not require a click, swipe, typing, or another user action before loading the player.
Keep the actual player present at its real position and size when the page loads.
If a media API fails, preserve a discoverable HTML video container and metadata.
Do not rely on URL fragments to load the video.

Use URL Inspection's live test and rendered screenshot to confirm that Google can see the player without interaction. A player visible in a human browser after clicking a poster image is not sufficient evidence.

Provide consistent metadata

Google can collect video details from structured data, video sitemaps, Open Graph metadata, HTML and player tags, mRSS, hosting platforms, rendered content, and generated evidence.

Keep the following consistent across every source that describes the same video:

Video title.
Thumbnail URL.
Player or content URL.
Duration and publication date.
The relationship between video and watch page.

Conflicting metadata can cause Google to combine a title from one source, a thumbnail from another, and a URL from a third. Search Console can list several URLs when Google believes they identify the same video.

Use the correct video URLs

A video implementation can involve three distinct URL types:

URL	Purpose	Common metadata location
Watch page	The indexed page where the user watches the video	XML sitemap `<loc>`
Player	A player dedicated to the asset	`VideoObject.embedUrl` or video sitemap `video:player_loc`
Content file	The actual video bytes or supported stream	`VideoObject.contentUrl` or `video:content_loc`

Do not use the watch-page URL as contentUrl. When possible, supply a stable, fetchable content URL; otherwise provide a specific player URL through embedUrl.

Search Console can show N/A as the video URL when Google detects a video but cannot locate its player or content URL. Add the correct URL in VideoObject, an appropriate HTML element, or the video sitemap.

VideoObject structured data

VideoObject helps Google discover a video and understand its metadata. Google's currently required properties for the structured-data feature are:

name.
thumbnailUrl.
uploadDate.

Important recommended properties include description, duration, and either contentUrl or embedUrl; Google recommends contentUrl when it is available because it is the most effective path for fetching the video bytes.

Markup must describe the video visible on that watch page. It does not turn a supporting video into the page's main content, repair an unindexed page, or guarantee a video result.

Use the Rich Results Test to validate VideoObject, Clip, SeekToAction, or BroadcastEvent. Use URL Inspection for the indexed page and live rendering. These tools answer different questions from the Video indexing report.

Thumbnails are an indexing requirement

A video needs a valid thumbnail at a stable URL. Google may extract a frame when it can fetch the video, but publishers should provide a reliable thumbnail explicitly.

A thumbnail should:

Use a Google-supported image format.
Meet the documented image-size requirements.
Be accessible without login and not blocked by robots.txt.
Return successfully without excessive host-load failures.
Remain at a stable URL.
Contain meaningful visible image data; the report rejects excessively transparent images.
Represent the video accurately.

The report can distinguish missing, unsupported, invalid-size, blocked, unreachable, transparent, host-load, and other invalid-thumbnail conditions. Test the thumbnail URL itself when debugging crawl access; testing only the watch page can miss a resource-level block.

Stable and fetchable video files

Google attempts to fetch video bytes during video indexing and needs access for features such as previews and key moments.

Check that:

The content or streaming URL does not expire quickly.
Google can fetch the file or stream without login, firewall, or robots.txt blocking.
The file uses a supported video type.
The page host, player host, video CDN, and thumbnail host can serve Googlebot reliably.
Redirects and signed URLs resolve consistently.
The hosting service has not deleted or privatized the video.

If access must be restricted from unknown crawlers, verify Googlebot and expose the stable media URL to verified Google crawlers. Do not assume that a URL working in an authenticated browser works for Google.

Read each issue category

Video isn't on a watch page

Google detected a video but considers it supplementary or one of several equal items.

Confirm whether the page genuinely should be a watch page. If yes, inspect the rendered page, make one video clearly primary, load the player without interaction, and ensure the page's title, description, and purpose focus on that video. If the page is intentionally an article, product, or category page, the status can be expected rather than an error to clear.

Cannot determine video position and size

The player is not present at a measurable position and size when the page loads. A common pattern is a poster or placeholder that turns into a player only after a click.

Render the real video container at its intended dimensions during initial load. Then inspect the live rendered HTML and screenshot.

Thumbnail issues

Separate the exact failure before replacing the image:

No thumbnail URL provided: supply one through consistent video metadata.
Unsupported thumbnail format: use a supported image type and correct extension.
Invalid thumbnail size: serve a compliant image size.
Blocked by robots.txt: allow Google to crawl the image host and path.
Could not be reached: repair the URL, response, authentication, or network path.
Could not be crawled due to hostload: investigate origin or CDN capacity and crawl response.
Thumbnail is transparent: provide an opaque, meaningful image.
Invalid thumbnail: recheck every thumbnail guideline and resource response.

Video not processed yet

Google is still processing the video. Wait several days before treating it as a persistent defect. Repeated URL changes can prolong or restart processing, so keep watch-page, player, content, and thumbnail URLs stable.

Video not processed

Google found a video but decided not to index it. Recheck the complete chain: indexed canonical watch page, visible primary player, stable metadata, valid thumbnail, fetchable media, supported format, and hosting reliability.

This reason is not proof of one specific technical failure. Change one evidence layer at a time and compare representative pages that succeeded.

Video not found on host service

The host no longer exposes the stated video or Google cannot reach the private hosting service. Confirm the asset ID and public player URL directly, then update stale embeds and metadata.

Diagnose a missing or unexpectedly small report

The entire report is missing

A missing report can mean Google has no indexed pages in the property where it detected a video. Check:

The selected Search Console property and protocol.
Page Indexing totals for the watch-page directory.
The Google-selected canonical for representative watch pages.
Whether the player appears in rendered HTML without interaction.
Whether new pages are internally linked and included in a sitemap.
Whether Google has had time to crawl and process the implementation.

The total is lower than the watch-page inventory

Partition the missing URLs before debugging video metadata:

Missing stage	Best evidence
URL not discovered	Internal links, sitemap submission, server logs
Page not indexed	Page Indexing report and URL Inspection
Duplicate/non-canonical	User-declared and Google-selected canonical
Indexed page, no video detected	Live render, screenshot, player HTML
Detected video, not indexed	Video indexing issue detail

Do not compare the report total directly with the number of rows in a CMS unless the CMS list contains only canonical, indexable watch pages with a detectable primary video.

Filter the report by sitemap correctly

The sitemap filter limits the report to indexed page URLs from a submitted or robots.txt-referenced sitemap where Google found a video.

It does not require those sitemap entries to contain video extension tags. It can include an indexed page from a normal XML sitemap when Google independently detected the video, and it excludes sitemap URLs that are not indexed or where no video was detected.

Use separate watch-page sitemaps to segment templates, languages, or publishing periods. Add video sitemap metadata when it helps discovery and understanding, but do not interpret the filter as a validation of those tags.

Video sitemaps help discovery, not eligibility

A video sitemap can help Google discover new or otherwise hard-to-find watch pages and understand their videos. It does not override page indexing, canonical selection, watch-page classification, thumbnail requirements, or video fetch problems.

Every referenced watch page, player, content file, and thumbnail must be accessible to Googlebot without login, firewall, or robots.txt blocking. List videos that are relevant to the host page, and keep sitemap metadata synchronized with page markup.

Use URL Inspection for a specific page

Inspect a representative URL when the aggregate report cannot explain the path to failure.

Indexed inspection

Check:

Whether the page is indexed.
The Google-selected canonical.
Last crawl and page-fetch state.
Detected video-indexing details in the Search Console interface.
Detected Video rich-result items and issues.

If Search Console detected a video, the interface displays a Video indexing section. If there is no section, Google did not detect a video for the inspected evidence.

Live test

Use the live test to verify the current response, rendered HTML, screenshot, resource loading, and structured data. A clean live test does not prove that Google has recrawled or indexed the new version.

The Last crawled date on a Video indexing issue page refers to the page crawl, not a separate timestamp for fetching the video asset.

Do not confuse three video reports

Evidence	Question answered
Video indexing report	Did an indexed page have one selected video indexed, and if not, why?
Videos rich-result report	Is detected `VideoObject` markup valid for Google's structured-data feature?
Performance report	Did the property record impressions and clicks in a selected search context?

Valid VideoObject markup does not prove video indexing. A video indexed status does not prove that a result received impressions. Performance traffic does not prove that every watch page is indexed as video.

Measure video search performance separately

In Performance → Search results, the Search type filter can select Web, Image, Video, or News. Use Video to measure results from Google's video search context.

Do not equate the Video indexing chart's impression overlay with a Performance total. Google warns that the report families aggregate impressions differently; the Video indexing report is page-oriented, while Performance can aggregate by property or page depending on the view and filters.

When evaluating a release, track separately:

Indexed watch pages with an indexed video.
No-video-indexed pages by reason.
Video search clicks and impressions.
Web search video appearances where available.
Discover video performance when relevant.

Indexing is a prerequisite and diagnostic outcome, not a traffic guarantee.

Third-party video hosts

An embedded YouTube, Vimeo, or other third-party video can be indexed on the publisher's watch page and on the hosting platform's own page. Both can appear in video features when each page meets the criteria.

For the publisher's page:

Keep a dedicated, indexable watch page.
Add accurate VideoObject data.
Include the page in a video sitemap when useful.
Confirm that the host allows Google to access the player and, where needed, the media file.
Expect the host's page to compete or coexist rather than assuming the publisher page receives exclusive attribution.

A reliable troubleshooting workflow

1. Build an expected watch-page inventory

Export canonical watch-page URLs from the CMS or video platform. Record video ID, page template, player host, thumbnail host, publication state, canonical, sitemap, and expected availability.

2. Reconcile page indexing first

Compare the inventory with Page Indexing and URL Inspection. Remove redirects, duplicates, noindex pages, expired pages, and non-canonical URLs from the expected video-indexing population.

3. Reconcile detection

For indexed pages absent from Video indexing, inspect live rendering. Confirm the player exists without interaction and the video is represented consistently in HTML, VideoObject, and sitemap metadata.

4. Segment report reasons

Group by page template, player provider, thumbnail host, language, publish period, and release version. A shared resource or component often explains many URLs.

5. Compare a successful control page

Compare one indexed-video page with one failure from the same template. Review rendered player position, metadata, response headers, resource access, canonical, and media URL stability.

6. Fix the generating layer

Repair the template, video platform integration, CDN rule, metadata service, or sitemap generator. Avoid URL-by-URL patches that leave the shared cause in place.

7. Verify current and indexed evidence

Run the Rich Results Test and live URL Inspection after deployment. Then wait for recrawl and processing before judging the indexed status. Track whether the issue population and representative last-crawl dates move after the release.

Common mistakes

Counting videos instead of pages

The report counts indexed pages with detected video status. One video on five pages can contribute five pages; five videos on one page contribute at most one indexed-video status.

Treating an absent URL as “No video indexed”

An absent URL might not be indexed or might have no detected video. It reaches No video indexed only after both page indexing and video detection succeed.

Trying to turn every embedded video into a watch page

A supporting video on an article or product page can be useful without qualifying for video indexing. Create dedicated watch pages only when that format serves users and the business.

Fixing structured data while the player is click-loaded

Perfect VideoObject markup does not make an interaction-gated player measurable in rendered layout. Fix player discovery and initial rendering.

Rotating signed URLs too frequently

Short-lived thumbnail, player, or media URLs interrupt processing. Expose stable URLs to verified Google crawlers.

Reading examples as a complete export

The example list can stop at 1,000 URLs even though the chart reports comprehensive totals. Maintain a first-party inventory for reconciliation.

Expecting instant recovery

The page, thumbnail, and video can be crawled or processed at different times. A clean live test and a recent page crawl do not guarantee immediate video reprocessing.

Automation boundaries

The public Search Console API does not expose the property-level Video indexing report or its issue populations.

The URL Inspection API returns indexed page status and rich-results information, but its documented response does not include the Video indexing section available in the Search Console interface. It also cannot run a live test through the API.

Automation can still:

Maintain an expected watch-page and video-ID inventory.
Validate VideoObject output in build or crawl pipelines.
Test watch-page, player, media, and thumbnail response codes.
Detect expiring or inconsistent URLs.
Query Search Analytics with the Video search type.
Inspect general indexed status and canonical evidence for selected URLs through the URL Inspection API.
Compare server logs for Googlebot access to pages and media resources.

UI review remains necessary for the Video indexing issue report, selected video details, rendered live-test evidence, and report-specific diagnosis.

What Search Console can and cannot conclude

It can show:

Indexed pages where Google detected a video.
Whether Google indexed one selected video from each reported page.
A reason when no video was indexed.
The selected candidate's video URL, thumbnail, watch-page classification, and metadata sources when available.
Representative affected URLs and page-oriented trends.

It cannot prove:

The number of unique videos indexed across the site.
That every video asset or watch page appears in the examples.
Every indexed page associated with one video.
That the video displayed or received traffic.
That the selected candidate is the video the publisher intended.
That a live fix has reached Google's index.
That a third-party host grants the publisher page exclusive video-result attribution.

Review checklist

The expected inventory contains canonical watch pages, not every page with an embed.
Each watch page has one clearly primary video.
The player exists in rendered HTML without interaction.
The page itself is indexable and Google-selected canonical.
Video, player, thumbnail, and watch-page URLs are distinguished correctly.
VideoObject required fields are accurate and consistent.
The thumbnail is valid, stable, crawlable, and meaningful.
The video or stream uses a stable, supported, fetchable URL.
Page, CDN, player, and thumbnail hosts can serve Googlebot.
Sitemap filtering is not mistaken for video-tag validation.
Report totals are interpreted as pages, not unique video assets.
Video indexing, Video rich results, and Performance are measured separately.
Fixes are validated in live rendering and later in indexed evidence.