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

AhrefsSiteAudit

Ahrefs · SEO and backlink crawlers · json

User-agent: AhrefsSiteAudit
Disallow: /
robots.txt tokenAhrefsSiteAudit
User-agent containsAhrefsSiteAudit
OperatorAhrefs
CategorySEO and backlink crawlers
robots.txtobeys robots.txt (documented)
Verify bypublished IP ranges
Published ranges81 IPv4 + 0 IPv6 · json · source

What it is

Ahrefs' site-audit crawler, separate from AhrefsBot. Ahrefs documents that it obeys robots.txt by default, and that a verified site owner can ask for it to be allowed to ignore robots.txt on their own site so the audit can see disallowed sections.

What blocking it costs you

Site owners auditing your domain get an incomplete report. Blocking it saves bandwidth and costs you nothing in search.

Full user-agent string

Mozilla/5.0 (compatible; AhrefsSiteAudit/6.1; +http://ahrefs.com/robot/site-audit)

Allow it instead

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

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://ahrefs.com/robot
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-seo-tools