WordPress.com is Automattic’s other bot

robots.txt

# WordPress.com has no documented robots.txt token and does not read robots.txt.
# Use a Cloudflare, nginx or Apache rule instead.

Cloudflare

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

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

WordPress

# WordPress.com has no documented robots.txt token and does not read robots.txt.
# Use a Cloudflare, nginx or Apache rule instead.

nginx

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

Apache

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

robots.txt

# WordPress.com has no documented robots.txt token and does not read robots.txt.
# Use a Cloudflare, nginx or Apache rule instead.

Cloudflare

# Security › WAF › Custom rules › Create rule
Expression: (http.user_agent contains "WordPress.com")
Action:     Block

WordPress

# WordPress.com has no documented robots.txt token and does not read robots.txt.
# Use a Cloudflare, nginx or Apache rule instead.

nginx

# In your server { } block:
if ($http_user_agent ~* "WordPress\.com") {
    return 403;
}

Apache

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