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

DataForSeoBot

DataForSEO · SEO and backlink crawlers · json

User-agent: DataForSeoBot
Disallow: /


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

What it is

Builds the backlink and SERP datasets DataForSEO resells through its API, so one crawl reaches many downstream tools.

What blocking it costs you

You leave a dataset that a long tail of SEO products is built on. No user-facing effect.

Full user-agent string

Mozilla/5.0 (compatible; DataForSeoBot/1.0; +https://dataforseo.com/dataforseo-bot)

Allow it instead

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

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