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

SemrushBot-ESI

Semrush · SEO and backlink crawlers · json

User-agent: SemrushBot-ESI
Disallow: /


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

What it is

The crawler for Semrush Enterprise Site Intelligence, the enterprise tier's own site analysis.

What blocking it costs you

Enterprise customers lose analysis of your domain. Nothing user-facing.

Full user-agent string

Mozilla/5.0 (compatible; SemrushBot-ESI; +http://www.semrush.com/bot.html)

Allow it instead

User-agent: SemrushBot-ESI
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=semrushbot-esi&s=client-dossiers'

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