In short. Googlebot-Video obeys robots.txt for automatic crawling, while separate indexing and preview instructions control how video resources appear in Search.

Definition: As of 17 October 2026, Google lists Googlebot-Video as a common crawler whose crawl controls affect video-related Google Search features and other products dependent on videos. Its automatic crawls obey robots.txt, the file that specifies which URLs a crawler may access.

Key facts

Google's common crawlers documentation lists Googlebot-Video/1.0 as the HTTP request user agent and both Googlebot-Video and Googlebot as robots.txt tokens.
Google's robots.txt specification selects the most specific matching user-agent group. A specific group and the wildcard group are handled separately.
Google's video SEO documentation requires access to the actual video bytes for features such as moving previews and key moments, which link to segments within a video.
Google's robots meta tag specification defines max-video-preview in seconds. A value of 0 permits at most a static image, subject to max-image-preview.

How does robots.txt control Googlebot-Video?

The token identifies the crawler in the User-agent line. This example applies a crawl restriction to every path for Googlebot-Video:

User-agent: Googlebot-Video
Disallow: /

Google's common crawlers list documents both the specific video token and the broader Googlebot token for this crawler. A video-specific group therefore provides a separate place to configure its crawl permissions.

Under Google's group-selection rules, the most specific matching group takes precedence over other groups. Restrictions in a wildcard group need to be included in a video-specific group if they are also intended to apply there.

The same specification limits a robots.txt file to its host, protocol and port. A rule on the watch-page host therefore has a separate scope from rules on a video-hosting subdomain.

Which resources and preview controls matter?

A watch page is a page whose main purpose is to show a single video. Google's video guidance requires that page to be indexed for video-feature eligibility. It also requires a valid thumbnail accessible to Googlebot and Googlebot Images. Access checks therefore cover the embedding page, the thumbnail and the video file at their respective URLs.

For preview control, the following tag belongs in the HTML page's head:

<meta name="robots" content="max-video-preview:0">

Google's robots meta specification gives this setting its static-image limit. For indexing instructions on a video file itself, the documentation specifies the X-Robots-Tag HTTP response header. For example, an indexing exclusion can be expressed as:

X-Robots-Tag: noindex

Google must crawl the URL to read its indexing or serving instructions. A robots.txt restriction that prevents that fetch also prevents Google from reading those instructions.

How is a Googlebot-Video request checked?

An HTTP user-agent string can be spoofed. Google's request-verification documentation describes matching the request's source IP address against its published common-crawler IP ranges. It also documents reverse DNS lookup followed by forward lookup: the resulting hostname must resolve back to the original requesting address. Common-crawler hostnames follow Google's documented googlebot.com patterns.

FAQ

Can I use Googlebot-Video as the name of a robots meta tag?

Google's meta tag documentation supports the crawler-specific names googlebot and googlebot-news; other names are ignored. You can use name="robots" for the preview example above.

Where can I check video indexing problems?

Google's video documentation points to Search Console's Video indexing report. You can see which indexed watch pages contain an indexed video and the reasons other videos remain unindexed.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer