Googlebot: User Agent, robots.txt Rules & Safety Rating

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

The official user-agent string for Googlebot is: Googlebot . 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 by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Q: Is Googlebot safe?

Yes, Googlebot 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 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 hurt my SEO?

⛔ Critical Impact - Blocking Googlebot 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, remove the rule immediately and request re-indexing via Google's webmaster tools.

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

Add the following lines to your /robots.txt file: User-agent: Googlebot Disallow: / This instructs Googlebot 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 is crawling my site?

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

Quick Facts

User-Agent:: Googlebot
Category:: Search Engines
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 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?

Googlebot is Google's primary web crawling bot. It discovers and indexes new and updated pages to be added to the Google Search index. Blocking this bot will remove your site from Google Search results.

Googlebot is Google's primary web crawling bot. It discovers and indexes new and updated pages to be added to the Google Search index. Blocking this bot will remove your site from Google Search results.
Googlebot is a production-grade search engine crawler operated by Google. It uses a distributed crawl infrastructure that respects crawl-delay directives, follows RFC 9309 (robots.txt) spec, and processes Sitemaps to prioritise fresh content. The user-agent string Googlebot must be whitelisted if your site uses rate-limiting or WAF rules. Blocking impact is Critical - Blocking removes you from search results.

What happens if you block Googlebot?

⛔ Critical Impact - Blocking Googlebot 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, 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 with robots.txt

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

Block completely (robots.txt)

User-agent: Googlebot
Disallow: /

Allow all (robots.txt)

User-agent: Googlebot
Allow: /

Block private only (robots.txt)

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

Nginx server block

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

Apache .htaccess

# Apache: Hard-block Googlebot
SetEnvIfNoCase User-Agent "Googlebot" 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 safe to allow?

Yes, Googlebot 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 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 requests resolve to google's domain.

What does Googlebot do?

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

Crawls and indexes web pages for search results
Discovers new and updated content on your website
Analyzes page structure, content, and links for ranking
Renders JavaScript to understand dynamic content
Checks for mobile-friendliness and page speed

Googlebot in context

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

Its safety rating is safe and its blocking impact is critical. So Googlebot 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

In our own study of robots.txt files across the Tranco top 10,000 sites (fetched October 20, 2026, 5,583 valid files), 528 files (9.5%) name Googlebot in a User-agent line, and 154 (2.8%) block it from the homepage. 13 of those blocks come from a group written for this crawler by name, and 141 come from a broad User-agent: * rule that catches it by accident. Larger sites are stricter: 3.6% of the top 1,000 block it, against 3.1% of the middle band and 2.4% of the tail.

Does it follow robots.txt?

Googlebot's operator says it follows robots.txt, so a correctly written Googlebot group is enough to control it.

Google crawlers and close alternatives

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

Googlebot: 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 the same answer as its siblings, stack User-agent: Googlebot with their lines above one set of rules; to treat Googlebot differently, give it its own group.

Other search engines that do the same job (builds a search or answer index) include Amzn-SearchBot from Amazon, Applebot from Apple, baidu from Baidu, Baiduspider from Baidu, Baiduspider-favo from Baidu, Baiduspider-image from Baidu. Deciding about Googlebot is usually a decision about the whole group, so check how your file treats these too.

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

Which rule Googlebot actually follows

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

User-agent: *
Disallow: /private/

User-agent: Googlebot
Disallow: /drafts/

Find the group. Googlebot looks for a group naming Googlebot. 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, 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 if the file also has a User-agent: Googlebot group?

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

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

Often, yes. Googlebot 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 the same as User-agent: Googlebot?

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

Should you allow Googlebot? Decide by situation

Recommended setting for Googlebot 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 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 on your own site

Open /robots.txt on your domain and search for Googlebot. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Googlebot 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 even when robots.txt allows it, and that never shows in the file.
Run our AI bot crawlability test to see how Googlebot and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Googlebot

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

Blocking Googlebot 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 group to add one rule for Googlebot and accidentally dropping every rule it used to follow under User-agent: *.
Disallowing CSS and JavaScript folders, which can stop Googlebot rendering your pages properly.

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

Spotting Googlebot in your logs

robots.txt says what Googlebot 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" /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" /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 user-agent, so confirm the source before acting on a match:

Googlebot: compare each address with the ranges at developers.google.com/static/crawling/ipranges/common-crawlers.json. A request claiming to be Googlebot from outside them is not genuine.

Frequently Asked Questions

What is the official user-agent string for Googlebot?

The official user-agent string for Googlebot is: Googlebot. 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 by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Is Googlebot safe?

Yes, Googlebot 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 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 hurt my SEO?

⛔ Critical Impact - Blocking Googlebot 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, remove the rule immediately and request re-indexing via Google's webmaster tools.

How do I block Googlebot in robots.txt?

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

User-agent: Googlebot
Disallow: /

This instructs Googlebot 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 respect robots.txt?

Yes - Googlebot 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 is crawling my site?

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

What is the crawl frequency of Googlebot?

Critical-impact search crawlers like Googlebot 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 from specific pages only?

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

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

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

How do I check if Googlebot is blocked by my robots.txt?

Use Google's robots.txt Tester in Search Console, or a third-party checker to simulate a Googlebot request. You can also manually check by opening https://aicrawlercheck.com/robots.txt and scanning for Googlebot entries. If a block exists, immediately test it against your most important URLs using the Google Search Console URL Inspection tool.

My site is blocked by Googlebot in Search Console - what do I do?

1. Open yourdomain.com/robots.txt and look for any User-agent: Googlebot or User-agent: * Disallow rules covering your key pages.
2. Remove or restrict the blocking rules.
3. Validate via Google Search Console → robots.txt Tester.
4. Request re-indexing using the URL Inspection tool.
5. Wait 1-2 weeks for re-crawl. Monitor Coverage report for recovery.