Googlebot-Image: User Agent, robots.txt Rules & Safety

Q: What is the official user-agent string for Googlebot-Image?

The official user-agent string for Googlebot-Image is: Googlebot-Image . This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Googlebot-Image by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Q: Is Googlebot-Image safe?

Yes, Googlebot-Image is a safe and legitimate crawler. It is operated by Google, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Googlebot-Image is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Q: Will blocking Googlebot-Image hurt my SEO?

⛔ Critical Impact - Blocking Googlebot-Image will stop Google from crawling and indexing your pages. Within days or weeks you may see pages drop out of Google's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Googlebot-Image, remove the rule immediately and request re-indexing via Google's webmaster tools.

Q: How do I block Googlebot-Image in robots.txt?

Add the following lines to your /robots.txt file: User-agent: Googlebot-Image Disallow: / This instructs Googlebot-Image not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/ ). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt .

Q: How do I verify if Googlebot-Image is crawling my site?

Search your web server access logs for the string Googlebot-Image (case-insensitive grep: grep -i "Googlebot-Image" /var/log/nginx/access.log ). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Googlebot-Image specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

Quick Facts

User-Agent:: Googlebot-Image
Category:: Google Bots
Operator:: Google
Safety:: Safe
Blocking Impact:: Critical - Blocking removes you from search results
SEO Impact Score:: 10/10
Official docs:: developers.google.com

Confirmed by the operator

Google names Googlebot-Image on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Googlebot-Image?

Googlebot-Image is the specific version of Googlebot designed to discover and index images for Google Images search.

Googlebot-Image is the specific version of Googlebot designed to discover and index images for Google Images search.
Googlebot-Image is one of Google's specialised crawlers, distinct from the general Googlebot. It serves a specific Google product (Images, Video, News, etc.) and uses the user-agent Googlebot-Image. Selectively blocking it disables the corresponding Google feature for your site (e.g., blocking Googlebot-Image removes your images from Google Image Search). Always verify which Google product is affected before blocking.

What happens if you block Googlebot-Image?

⛔ Critical Impact - Blocking Googlebot-Image will stop Google from crawling and indexing your pages. Within days or weeks you may see pages drop out of Google's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Googlebot-Image, remove the rule immediately and request re-indexing via Google's webmaster tools.

Never block - it will remove your site from major search results.

How to block Googlebot-Image with robots.txt

<code>User-agent: Googlebot-Image</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: Googlebot-Image
Disallow: /

Allow all (robots.txt)

User-agent: Googlebot-Image
Allow: /

Block private only (robots.txt)

User-agent: Googlebot-Image
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block Googlebot-Image
if ($http_user_agent ~* "Googlebot\-Image") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Hard-block Googlebot-Image
SetEnvIfNoCase User-Agent "Googlebot\-Image" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is Googlebot-Image safe to allow?

Yes, Googlebot-Image is a safe and legitimate crawler. It is operated by Google, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Googlebot-Image is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Verify by reverse-DNS lookup: legitimate Googlebot-Image requests resolve to google's domain.

What does Googlebot-Image do?

Understanding Googlebot-Image's purpose helps you decide whether to allow or block it.

Specialized Google crawler for specific features
May handle images, videos, or other media types
Supports Google Search features and rich results
Works alongside main Googlebot for comprehensive indexing
Respects robots.txt and crawl-delay directives

Googlebot-Image in context

Googlebot-Image is a search engine crawler operated by Google. In plain terms, it builds a search or answer index. Our database files it under Google crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 20 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So Googlebot-Image is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat Googlebot-Image

Our robots.txt study of the Tranco top 10,000 did not track Googlebot-Image as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Googlebot-Image's operator does not clearly document how it treats robots.txt. Write the Googlebot-Image rule anyway, then confirm in your logs that its requests stop.

Google crawlers and close alternatives

Googlebot-Image is one of 32 Google crawlers in our database. A User-agent: Googlebot-Image group controls Googlebot-Image only; the other Google tokens below need their own lines.

Googlebot-Image: this crawler (Tier 3)
AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
AdsBot-Google-Mobile: Google Ads Quality (Mobile), checks pages for an SEO, uptime or analytics service (Tier 3)
APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
Gemini-Deep-Research: Gemini-Deep-Research, fetches a page when a person asks an assistant or app to open it (Tier 3)
Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)

To give Googlebot-Image the same answer as its siblings, stack User-agent: Googlebot-Image with their lines above one set of rules; to treat Googlebot-Image differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes Googlebot-Image an unusual case: decide about it on its own merits.

We first recorded Googlebot-Image on March 17, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule Googlebot-Image actually follows

Googlebot-Image reads exactly one group in robots.txt, the most specific one that names Googlebot-Image, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Googlebot-Image
Disallow: /drafts/

Find the group. Googlebot-Image looks for a group naming Googlebot-Image. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to Googlebot-Image, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to Googlebot-Image if the file also has a User-agent: Googlebot-Image group?

No. Once a group names it, Googlebot-Image reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Googlebot-Image remove your pages from AI answers?

Often, yes. Googlebot-Image is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: googlebot-image the same as User-agent: Googlebot-Image?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Googlebot-Image? Decide by situation

Recommended setting for Googlebot-Image by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Allow it. It is how this search engine finds your pages.
You license content and want to stop AI training	Blocking it does not stop training, because Googlebot-Image is a search engine crawler. Block the operator's training crawler instead.
You run an online shop	Allow it unless it is overloading your servers.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check Googlebot-Image on your own site

Open /robots.txt on your domain and search for Googlebot-Image. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Googlebot-Image follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse Googlebot-Image even when robots.txt allows it, and that never shows in the file.
Run our AI visibility checker to see how Googlebot-Image and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Googlebot-Image

The errors we see most often with Googlebot-Image in the files and firewalls we test:

Blocking Googlebot-Image to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
Writing a User-agent: Googlebot-Image group to add one rule for Googlebot-Image and accidentally dropping every rule it used to follow under User-agent: *.
Disallowing CSS and JavaScript folders, which can stop Googlebot-Image rendering your pages properly.

All three hide inside a file that looks correct, so check Googlebot-Image from outside after every change.

Spotting Googlebot-Image in your logs

robots.txt says what Googlebot-Image may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Googlebot-Image" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Googlebot-Image" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Googlebot-Image user-agent, so confirm the source before acting on a match:

Googlebot-Image: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Googlebot-Image request with caution.

Frequently Asked Questions

What is the official user-agent string for Googlebot-Image?

The official user-agent string for Googlebot-Image is: Googlebot-Image. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Googlebot-Image by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Is Googlebot-Image safe?

Yes, Googlebot-Image is a safe and legitimate crawler. It is operated by Google, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Googlebot-Image is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Will blocking Googlebot-Image hurt my SEO?

⛔ Critical Impact - Blocking Googlebot-Image will stop Google from crawling and indexing your pages. Within days or weeks you may see pages drop out of Google's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Googlebot-Image, remove the rule immediately and request re-indexing via Google's webmaster tools.

How do I block Googlebot-Image in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: Googlebot-Image
Disallow: /

This instructs Googlebot-Image not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.

Does Googlebot-Image respect robots.txt?

Yes - Googlebot-Image is a well-behaved bot operated by Google. It fetches and parses /robots.txt before crawling any page, following RFC 9309.

How do I verify if Googlebot-Image is crawling my site?

Search your web server access logs for the string Googlebot-Image (case-insensitive grep: grep -i "Googlebot-Image" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Googlebot-Image specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

What is the crawl frequency of Googlebot-Image?

Critical-impact search crawlers like Googlebot-Image typically crawl popular pages daily and less popular pages weekly. You can manage crawl rate via the crawl-delay directive or via the search console.

Can I block Googlebot-Image from specific pages only?

Yes. Instead of a global Disallow: / you can restrict Googlebot-Image to specific paths:

User-agent: Googlebot-Image
Disallow: /private/
Disallow: /staging/
Allow: /

This allows Googlebot-Image everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.