Google-Safety is Google’s monitoring bot

robots.txt

User-agent: Google-Safety
Allow: /

Cloudflare

# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "Google-Safety")
Action:     Skip › All Super Bot Fight Mode rules

# Also check Security › Bots: "Block AI bots" can block it regardless of robots.txt.

WordPress

# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: Google-Safety
Allow: /

nginx

# nginx serves every user agent by default.
# Make sure no rule like this blocks it:
# if ($http_user_agent ~* "Google\-Safety") { return 403; }

Apache

# Apache serves every user agent by default.
# Make sure .htaccess has no rule like this:
# RewriteCond %{HTTP_USER_AGENT} Google\-Safety [NC]
# RewriteRule .* - [F,L]

robots.txt

# Google-Safety has been reported to ignore robots.txt.
# Add a Cloudflare, nginx or Apache rule as well.
User-agent: Google-Safety
Disallow: /

Cloudflare

# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "Google-Safety")
Action:     Block

WordPress

# WordPress serves a virtual robots.txt. Edit it with your SEO plugin:
# Yoast: SEO › Tools › File editor · Rank Math: General Settings › Edit robots.txt
User-agent: Google-Safety
Disallow: /

nginx

# In your server { } block:
if ($http_user_agent ~* "Google\-Safety") {
    return 403;
}

Apache

# .htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} Google\-Safety [NC]
RewriteRule .* - [F,L]
</IfModule>