SEO analysis

AhrefsSiteAudit

Runs site audits configured in Ahrefs.

See your agent traffic
PurposeSEO analysis
HTTP identifierAhrefsSiteAudit
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

A scheduled audit can explain a burst of requests. It should not be counted as organic discovery or user demand.

Audit URL coverage
Failed responses
Crawl duration

Your next move

Check your audit schedule and crawl settings before investigating a traffic spike as an external incident.

The technical details

Markdown
How to identify it

Look for the AhrefsSiteAudit identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Correlate with an authorized audit and the operator’s published network guidance.

Access and robots.txt

Ahrefs Site Audit follows robots.txt by default. A verified site owner can configure an override for an authorized audit.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: AhrefsSiteAudit
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See AhrefsSiteAudit in context

See their requests. Find the pages that matter.

See your agent traffic