Promptwatch Logo

Moz rogerbot

Rogerbot is Moz's site audit crawler for Moz Pro Campaigns.
Mozrogerbot-crawler
SEO

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.

Indirectly relevant

Is Moz rogerbot relevant for AI search?

Indirectly. Moz rogerbot has no AI product of its own, but its output can end up in the systems that AI answers draw on.

Moz rogerbot is an SEO auditing crawler. It has no direct effect on search rankings or AI answers, but the reports it feeds are used to fix crawlability and content issues that do affect how search and AI systems see your site.

How to handle Moz rogerbot

Allow Rogerbot when your team or an authorized agency expects Moz Pro to audit the site. If no one should be running that audit, blocking it avoids spending server capacity on a report you will not use.

Use Moz's documented robots.txt product token, not the contact text stored in this directory's detection field:

User-agent: rogerbot
Disallow: /

A blank Disallow: allows the whole site. You can instead exclude selected paths or add a moderate Crawl-delay when audit traffic is causing load. Put the Rogerbot record above User-agent: * so it is read as the specific policy.

Do not try to authenticate Rogerbot with a fixed IP allowlist. Moz says its addresses are dynamic, and the supplied Cloudflare entry has no signed-agent URL. Match the full request pattern for operations work, but keep protected areas behind normal authentication.

Examples

  • An agency launches an On-Demand Crawl for a client and asks the client to allow `rogerbot` so Moz can inspect the intended pages.
  • A large documentation site adds a 10-second crawl delay after a scheduled Campaign audit begins competing with visitor traffic.
  • A firewall analyst sees `rogerbot-crawler` inside the contact email but uses `rogerbot` in robots.txt, following Moz's distinction between the two strings.

Frequently asked questions about Moz rogerbot

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Moz says Rogerbot supports Campaign Site Crawl and On-Demand Crawl, along with page optimization and on-page grading reports in Moz Pro.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard