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

serpstatbot

Serpstat · SEO and backlink crawlers · json

User-agent: serpstatbot
Disallow: /


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

What it is

Serpstat's backlink crawler. It documents support for Crawl-delay up to 20 seconds, including a delay set on the * group.

What blocking it costs you

You leave Serpstat's link index. Try Crawl-delay first — they honour it, and a slow crawler is cheaper to keep than to fight.

Full user-agent string

serpstatbot/2.1 (advanced backlink tracking bot; https://serpstatbot.com/; abuse@serpstatbot.com)

Allow it instead

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

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