Your first 5 pages, free. Approve every change or run on autopilot.
Search engine Operated by Google

Googlebot-Image

Googlebot's image-fetching counterpart, which populates Google Images.

At a glance

Operator
Google
Category
Search engine

A classic search crawler whose index also feeds that company's AI answers. Blocking it removes you from both the blue links and the AI summaries above them.

User-Agent token
Googlebot-Image
robots.txt token
Googlebot-Image
Respects robots.txt
Documented as compliant

What Googlebot-Image does

Googlebot-Image requests image files it discovered while crawling your pages and indexes them for Google Images and the image results embedded in ordinary search. It sends its own user agent, so its traffic is separable from the page crawl in your logs.

Should you block Googlebot-Image?

Blocking it drops your images from Google Images while leaving your pages indexed. For a catalogue, a recipe site or anything visual, that is a meaningful traffic loss for no gain.

Our take

Don't. Blocking Googlebot-Image removes you from Google altogether — the ordinary results and the AI answers built on top of them. If what you actually want is to stay in search while staying out of model training, that is a separate token, and it's the one to reach for. MetaPilot shows Googlebot-Image in your crawler analytics but won't write a block for it from the dashboard.

The robots.txt rules for Googlebot-Image

Add the rule below to the robots.txt file at the root of your domain (yourdomain.com/robots.txt). Use the Googlebot-Image token rather than the raw User-Agent string, and repeat the rule on every subdomain you want covered. New to the file? Read what robots.txt is first.

The allow rule is the one you want. The disallow variant is documented below for completeness, but it removes your site from Google entirely. Don't paste it unless that is genuinely what you intend.

Allow Googlebot-Image explicitly

robots.txt
User-agent: Googlebot-Image
Allow: /

Block Googlebot-Image — removes you from Google

robots.txt
User-agent: Googlebot-Image
Disallow: /

A note on what this does and doesn't do. robots.txt is a request, not a lock — it works because well-behaved crawlers choose to read it. It also isn't retroactive: anything already fetched stays fetched. If you need a hard stop, block at your firewall or CDN as well.

How MetaPilot handles Googlebot-Image

MetaPilot detects Googlebot-Image in your edge logs, so you see its real hits on your real pages rather than a guess: how often it visits, which URLs it takes, and how that trend moves week to week. From the same screen you flip Googlebot-Image between allow and deny with one click — MetaPilot rewrites only its own managed section of your robots.txt and serves it at the edge, so the change is live on the crawler's next visit with no deploy and no touching your own rules. See AI-crawler analytics or follow the guide to monitor and control AI crawlers.

Related crawlers

Browse every AI crawler

FAQ

What is Googlebot-Image?

Googlebot's image-fetching counterpart, which populates Google Images.

Googlebot-Image requests image files it discovered while crawling your pages and indexes them for Google Images and the image results embedded in ordinary search. It sends its own user agent, so its traffic is separable from the page crawl in your logs.

Does Googlebot-Image respect robots.txt?

Yes — Google documents that Googlebot-Image honours robots.txt. A Disallow for the Googlebot-Image token is respected.

Should I block Googlebot-Image?

Almost certainly not. Disallowing Googlebot-Image removes you from Google's search results, and because those same results feed Google's AI answers, you lose both at once.

If you want to stay in search but out of generative AI, that is a different token — see the training opt-out for Google in the related crawlers below. MetaPilot will not write a block for Googlebot-Image from the dashboard for this reason.

Will blocking Googlebot-Image hurt my traffic?

Blocking it drops your images from Google Images while leaving your pages indexed. For a catalogue, a recipe site or anything visual, that is a meaningful traffic loss for no gain.

Ask an AI whether to block Googlebot-Image