rogerbot user agent
Operated by Moz
rogerbot is the Moz crawler that runs site crawls for Moz Pro campaigns.
The rogerbot bot at a glance
- rogerbot is operated by Moz and fetches pages to power a specific product feature.
- The robots.txt token for rogerbot is rogerbot.
- Blocking an SEO tool crawler has no effect on Google or Bing rankings.
- rogerbot robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Allow.
What is rogerbot?
rogerbot audits a site when a Moz Pro user sets up a campaign for it, and Moz states it obeys robots.txt.
Allow it on your own site if you track it in Moz Pro.
Should you block rogerbot?
Allow rogerbot unless it causes a measurable load problem.
| Effect on search rankings | Blocking an SEO tool crawler has no effect on Google or Bing rankings. |
|---|---|
| Effect on AI visibility | No effect on AI answers. Blocking hides your pages and backlinks from that SEO tool, including from competitors who use it, and breaks your own audits in that tool. |
| Follows robots.txt | Yes |
| Recommendation | Allow |
How to block or allow rogerbot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token rogerbot is matched case-insensitively.
robots.txt: block
# Block rogerbot
User-agent: rogerbot
Disallow: /robots.txt: allow
# Allow rogerbot
User-agent: rogerbot
Allow: /robots.txt: partial
# Keep rogerbot out of private areas only
User-agent: rogerbot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to rogerbot
if ($http_user_agent ~* "(rogerbot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to rogerbot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (rogerbot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "rogerbot")How to verify real rogerbot traffic
Moz publishes no IP list or reverse DNS pattern for rogerbot, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find rogerbot in your server logs
Search the web server access log for the token. The command below counts rogerbot requests per URL on Nginx or Apache.
grep -i "rogerbot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
rogerbot FAQ
rogerbot uses the robots.txt token "rogerbot". Moz does not publish a full user-agent string, so match the token inside the User-Agent header.
Yes. Moz states that rogerbot follows robots.txt rules written for the "rogerbot" token.
Blocking an SEO tool crawler has no effect on Google or Bing rankings. No effect on AI answers. Blocking hides your pages and backlinks from that SEO tool, including from competitors who use it, and breaks your own audits in that tool.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: rogerbot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Moz publishes no IP list or reverse DNS pattern for rogerbot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "rogerbot", for example with: grep -i "rogerbot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Moz crawler documentation. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
