Moz
DotBot
Collects links for Moz’s link index.
SEO analysisPurposeSEO analysis
HTTP identifierrogerbot
IdentityVerify beyond the name
THE SIGNAL
What this visit tells you
Scheduled site audits can produce concentrated bursts of page requests.
Crawled URLs
Broken destinations
Crawl duration
Your next move
Match the burst to a Moz campaign and inspect errors in the corresponding audit.
The technical details
MarkdownHow to identify it
Look for the rogerbot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.
How to check identity
Moz does not publish static IP ranges for Rogerbot. Correlate the request with an authorized Moz audit; the User-Agent alone remains unverified.
Access and robots.txt
The operator documents robots.txt rules for this identifier.
Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.
User-agent: rogerbot
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 PulseSee rogerbot in context
See their requests. Find the pages that matter.
See your agent trafficKEEP EXPLORING
Different bots, different intent
Semrush
SemrushBot
Collects web and link data for Semrush analysis tools.
SEO analysis
Ahrefs
AhrefsBot
Collects link and web data for Ahrefs and the Yep search engine.
SEO analysis