Safe Official docs Google Bots

Google Safety

Operated by Google

Quick Facts

User-Agent:
Google-Safety
Category:
Google Bots
Operator:
Google
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10

Confirmed by the operator

Google names Google-Safety on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on September 22, 2026.

What is Google Safety?

Google Safety is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.

Google Safety is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Google Safety uses the user-agent token Google-Safety. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Google Safety?

🔶 AI Visibility Trade-off - Blocking Google Safety will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Google Safety with robots.txt

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

Block completely (robots.txt)
User-agent: Google-Safety Disallow: /
Allow all (robots.txt)
User-agent: Google-Safety Allow: /
Block private only (robots.txt)
User-agent: Google-Safety Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Google Safety if ($http_user_agent ~* "Google-Safety") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Google Safety SetEnvIfNoCase User-Agent "Google-Safety" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Google Safety safe to allow?

Yes, Google Safety is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Google Safety requests resolve to Google's domain.

What does Google Safety do?

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

  • Validates pages, ads, or policy compliance
  • Performs automated quality and safety checks
  • Does not collect training data
  • No impact on search rankings
  • Generally safe to allow

Frequently Asked Questions

What is the official user-agent string for Google Safety?
The official user-agent string for Google Safety is: Google-Safety. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Google Safety by performing a reverse-DNS lookup on the source IP.
Is Google Safety safe?
Yes, Google Safety is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Google Safety hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Google Safety will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Google Safety in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Google-Safety
Disallow: /

This instructs Google Safety not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Google Safety respect robots.txt?
Google Safety is operated by Google and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Google Safety is crawling my site?
Search your web server access logs for the string Google-Safety (case-insensitive: grep -i "Google-Safety" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).