What is Moz rogerbot?
Rogerbot reads a site for Moz Pro audits. Moz uses the crawl to populate Campaign Site Crawl and On-Demand Crawl results, giving the Moz customer reports about problems found in the site's code and pages.
It is not Moz's web-wide link indexer. That job belongs to Dotbot. Rogerbot works on a site selected for a Moz Pro Campaign or an on-demand audit, while Dotbot follows the web to build data for Link Explorer and the Moz Links API.
A configured Campaign may bring Rogerbot back on a weekly schedule, and an On-Demand Crawl can start at a user's request. Moz says the crawler uses thousands of changing addresses rather than a static range. A firewall rule based on one observed address will not remain useful.
The supplied directory token, rogerbot-crawler, appears in the contact address inside Cloudflare's full user-agent example. Moz's Rogerbot guide tells robots.txt authors to use the actual product token rogerbot. Logs can show rogerbot/1.2 followed by the help URL and a rogerbot-crawler email address, so detection and robots control should not be treated as the same string.
Moz says Rogerbot obeys robots.txt and supports allow, disallow, and crawl-delay. A Rogerbot-specific record should appear before a wildcard record. Moz advises against delays above 30 seconds because the audit may not finish.
This crawler produces SEO audit data for the Moz customer who initiated or configured the crawl. It does not index pages for a public search engine, generate AI answers, or have a documented model-training purpose. Blocking it can make Moz Pro audit reports incomplete, but it does not remove a page from Google or another search index. Cloudflare publishes no signature key directory for the bot.
