curl -s https://www.pathwren.workers.dev/crawler/dotbot.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

DotBot

Moz · SEO and backlink crawlers · json

User-agent: dotbot
Disallow: /


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

What it is

Moz's crawler for Link Explorer. Moz documents that it respects robots.txt and that dotbot is the token to name.

What blocking it costs you

You leave Moz's link index, so Domain Authority and link reports about your site get thinner. Nothing a reader or an assistant sees changes.

Full user-agent string

Mozilla/5.0 (compatible; DotBot/1.2; +https://opensiteexplorer.org/dotbot; help@moz.com)

Allow it instead

User-agent: dotbot
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=dotbot&s=client-dossiers'

/tools/verification-methods?crawler=dotbot
How do I prove a request really is dotbot? 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/dotbot
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-seo-tools