curl -s https://www.pathwren.workers.dev/crawler/rogerbot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

rogerbot

Moz · SEO and backlink crawlers · json

User-agent: rogerbot
Disallow: /


robots.txt token	`rogerbot`
User-agent contains	`rogerbot`
Operator	Moz
Category	SEO and backlink crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Moz's Campaign crawler, which audits a site its own owner registered. Moz states there is no IP range for it — identification is by user-agent only.

What blocking it costs you

Moz Pro site audits of your domain stop. If the domain is yours and you use Moz, blocking this breaks your own reports.

Full user-agent string

rogerbot/1.2 (http://moz.com/help/pro/what-is-rogerbot-, rogerbot-crawler@moz.com)

Allow it instead

User-agent: rogerbot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=rogerbot&s=client-dossiers'

/tools/verification-methods?crawler=rogerbot
How do I prove a request really is rogerbot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://moz.com/help/moz-procedures/crawlers/rogerbot
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-seo-tools