Safe Official docs SEO Tools

Moz Campaign Crawler

Operated by Moz

Quick Facts

User-Agent:
Rogerbot
Category:
SEO Tools
Operator:
Moz
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
moz.com

Confirmed by the operator

Moz names Rogerbot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Moz Campaign Crawler?

Moz Campaign Crawler is a monitoring and validation agent operated by Moz. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.

Moz Campaign Crawler is a monitoring and validation agent operated by Moz. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Moz Campaign Crawler uses the user-agent token Rogerbot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Moz Campaign Crawler?

🔶 AI Visibility Trade-off - Blocking Moz Campaign Crawler will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Moz Campaign Crawler with robots.txt

<code>User-agent: Rogerbot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: Rogerbot Disallow: /
Allow all (robots.txt)
User-agent: Rogerbot Allow: /
Block private only (robots.txt)
User-agent: Rogerbot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Moz Campaign Crawler if ($http_user_agent ~* "Rogerbot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Moz Campaign Crawler SetEnvIfNoCase User-Agent "Rogerbot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Moz Campaign Crawler safe to allow?

Yes, Moz Campaign Crawler is a safe and legitimate crawler operated by Moz. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Moz Campaign Crawler requests resolve to Moz's domain.

What does Moz Campaign Crawler do?

Understanding Moz Campaign Crawler's purpose helps you decide whether to allow or block it.

  • Validates pages, ads, or policy compliance
  • Performs automated quality and safety checks
  • Does not collect training data
  • No impact on search rankings
  • Generally safe to allow

Moz Campaign Crawler in context

Moz Campaign Crawler is a utility crawler operated by Moz. In plain terms, it checks pages for an SEO, uptime or analytics service. Our database files it under SEO tools and ranks it Tier 4, specialist crawlers that matter to particular sites or markets. 19 of the 19 SEO tools in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Moz Campaign Crawler rests on what you want from Moz, not on its behaviour. How we rate safety and impact.

How site owners treat Moz Campaign Crawler

Our robots.txt study of the Tranco top 10,000 did not track Rogerbot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Moz Campaign Crawler's operator does not clearly document how it treats robots.txt. Write the Moz Campaign Crawler rule anyway, then confirm in your logs that its requests stop.

Moz crawlers and close alternatives

Moz Campaign Crawler is one of 2 Moz crawlers in our database. A User-agent: Rogerbot group controls Moz Campaign Crawler only; the other Moz tokens below need their own lines.

  • Rogerbot: this crawler (Tier 4)
  • DotBot: Moz SEO, checks pages for an SEO, uptime or analytics service (Tier 4)

To give Moz Campaign Crawler the same answer as its siblings, stack User-agent: Rogerbot with their lines above one set of rules; to treat Moz Campaign Crawler differently, give it its own group.

Other SEO tools that do the same job (checks pages for an SEO, uptime or analytics service) include AhrefsBot from Ahrefs, AhrefsSiteAudit from Ahrefs, AwarioBot from Awario, AwarioRssBot from Awario, AwarioSmartBot from Awario, Chrome-Lighthouse from Google. Deciding about Moz Campaign Crawler is usually a decision about the whole group, so check how your file treats these too.

We first recorded Rogerbot on September 22, 2026. Moz documents it on moz.com, and we recheck that page before each release.

Which rule Moz Campaign Crawler actually follows

Moz Campaign Crawler reads exactly one group in robots.txt, the most specific one that names Rogerbot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Rogerbot
Disallow: /drafts/
  1. Find the group. Moz Campaign Crawler looks for a group naming Rogerbot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Moz Campaign Crawler, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Moz Campaign Crawler if the file also has a User-agent: Rogerbot group?

No. Once a group names it, Moz Campaign Crawler reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Moz Campaign Crawler remove your pages from AI answers?

Often, yes. Moz Campaign Crawler is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Related: how AI engines choose their sources

Test yourself: is User-agent: rogerbot the same as User-agent: Rogerbot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Moz Campaign Crawler? Decide by situation

Recommended setting for Moz Campaign Crawler by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because Moz Campaign Crawler is a utility crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless your logs show it is costly.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Moz Campaign Crawler on your own site

  1. Open /robots.txt on your domain and search for Rogerbot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Moz Campaign Crawler follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Moz Campaign Crawler even when robots.txt allows it, and that never shows in the file.
  4. Run our AI crawler tester to see how Moz Campaign Crawler and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Moz Campaign Crawler

The errors we see most often with Moz Campaign Crawler in the files and firewalls we test:

  1. Treating Moz Campaign Crawler as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when Moz Campaign Crawler is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking Moz Campaign Crawler by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check Moz Campaign Crawler from outside after every change.

Spotting Moz Campaign Crawler in your logs

robots.txt says what Moz Campaign Crawler may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Rogerbot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Rogerbot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Moz Campaign Crawler user-agent, so confirm the source before acting on a match:

  • Rogerbot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Moz Campaign Crawler request with caution.

Frequently Asked Questions

What is the official user-agent string for Moz Campaign Crawler?
The official user-agent string for Moz Campaign Crawler is: Rogerbot. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Moz Campaign Crawler by performing a reverse-DNS lookup on the source IP.
Is Moz Campaign Crawler safe?
Yes, Moz Campaign Crawler is a safe and legitimate crawler operated by Moz. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Moz Campaign Crawler hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Moz Campaign Crawler will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Moz Campaign Crawler in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Rogerbot
Disallow: /

This instructs Moz Campaign Crawler not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Moz Campaign Crawler respect robots.txt?
Moz Campaign Crawler is operated by Moz and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Moz Campaign Crawler is crawling my site?
Search your web server access logs for the string Rogerbot (case-insensitive: grep -i "Rogerbot" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us