Bot intelligence record
Ahrefs Site Audit
Review firstUse the Ahrefs Site Audit identifier to recognize Ahrefs crawler traffic in Botcrawl logs and the Botcrawl bot directory.
- Operator
- Ahrefs
- Family
- Ahrefs
- Type
- Search
- Source type
- Documented
- Last checked
- 2026-05-20
User-Agent Pattern
AhrefsAhrefsSiteAudit
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: AhrefsSiteAudit
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Search indexing, content discovery, rendering, or search-result freshness checks.
Record Details
Structured data- Operator
- Ahrefs
- Family
- Ahrefs
- Type
- Search
- Purpose
- Indexing
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Documented
- Verification
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- IP ranges
- https://ahrefs.com/robot
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
Ahrefs Site Audit is a Botcrawl bot directory entry for automated traffic associated with Ahrefs. The primary identifier used for log review is AhrefsSiteAudit.
Identification
- Identifier pattern:
AhrefsSiteAudit - Aliases:
Ahrefs audit crawler - Operator: Ahrefs
- Family: Ahrefs
- Type: Search
- Kind: Crawler
- Robots token:
AhrefsSiteAudit
Common use
Search indexing, content discovery, rendering, or search-result freshness checks.
Verification and handling
Confirm matches against the request user agent and compare with supporting signals such as IP ownership, reverse DNS, published operator documentation, authentication headers, or observed behavior when available. User-agent strings can be copied or spoofed.
Botcrawl marks this as normal-risk traffic; decide based on site policy, traffic behavior, and verification signals. Confidence is marked as medium, verification status is yes, identity type is verified-bot, and robots.txt behavior is recorded as no.
Evidence and Source
- Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
- Match the identifier against request logs and verify with supporting signals such as IP ownership, reverse DNS, authentication headers, published operator documentation, or observed behavior where available. Do not rely on the user-agent string alone.
- Search indexing, content discovery, rendering, or search-result freshness checks.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.