AI crawler analytics: a census of 121 listings

The Agentic Traffic dashboard breaks AI bot hits down by user agent, status code and content type, but it stays blank until CDN log forwarding is configured.

Source retrieved 2026-09-12

Server-side capture logs AI bot hits with ASN and reverse-DNS verification; the free tier sees three bot families and seven days, paid tiers all eight families and longer history.

Source retrieved 2026-09-19

AI crawler visits are shown, but through a separate Ahrefs product you install on the site rather than the Brand Radar add-on itself, and it is still labelled beta.

Source retrieved 2026-09-19

AI bot crawls are tracked server-side on every plan, but the number of crawlers is capped by tier — 2 on Free rising to all 17 only on Agency.

Source retrieved 2026-09-19

It checks whether named AI crawlers are permitted by robots.txt and meta directives, but never shows which bots actually visited your server.

Source retrieved 2026-09-20

It surfaces per-page AI chat traffic plus crawl errors and warnings, but never reports which AI bots requested your site or how often.

Source retrieved 2026-10-04

A REST ingest endpoint and nginx log tailer classify AI crawlers and verify each source IP against the operator's published ranges to flag spoofed bots.

Source retrieved 2026-09-20

You see whether each AI crawler is allowed or blocked, tested live, but this is access verification rather than a log of actual bot visits.

Source retrieved 2026-09-20

An AI Crawl feature classifies crawler hits and is metered separately per 100k hits, and a robots tool reports crawler rules for search and AI user agents.

Source retrieved 2026-09-21

The technical module identifies which AI crawlers and agents reach the site and where they are blocked, using raw server log analysis.

Source retrieved 2026-09-09

AI Agent Insights reports which AI systems reach the site, what they engage with and where they hit errors or blocks.

Source retrieved 2026-09-11

Server logs from supported hosts are read without a browser tag and grouped into AI bot visits, user-requested fetches and clicks arriving from AI links, with verification status kept.

Source retrieved 2026-10-03

It tests whether AI crawlers are permitted to fetch a URL, which is a robots-level check rather than log analytics of actual bot visits.

Source retrieved 2026-09-21

It reports whether each named AI bot is permitted by robots.txt and shows access badges, which is a permission check rather than a log of visits your site received.

Source retrieved 2026-10-08

Crawler analytics is checked on every plan and separates indexing, retrieval and training visits by bot, for one domain.

Source retrieved 2026-09-21

AI bot crawl reporting requires ingesting your server or CDN logs, and the plan table marks Log File Analysis merely Available on Essentials and Growth while only Enterprise has it included.

Source retrieved 2026-10-06

BotSight is a named Visibility capability for reviewing connected crawl logs, user agents, page paths, visit records and status codes, but Dageno publishes it only as an analysis structure explicitly marked as not customer data and lists it in no plan row.

Source retrieved 2026-09-15

The diagnostic checks whether AI crawlers are permitted and names the blocked bots per platform, but no log-level analytics of which bots actually crawled the site is offered.

Source retrieved 2026-09-23

A free tool reads robots.txt and reports which AI crawlers you allow or block, but no log-based analysis of actual bot hits on a customer site is documented.

Source retrieved 2026-09-13

Bot Analytics reports which AI bots hit which pages and with what response codes, but the plan table sells it as an Enterprise-only addition to Pro.

Source retrieved 2026-09-12

Server logs or a Cloudflare feed identify each AI crawler with status codes and top URLs, but Bot Analytics is not included on Starter.

Source retrieved 2026-09-08

A server-side or edge Sensor records AI bot hits per page, and the analytics are included at zero token cost on every tier including Free.

Source retrieved 2026-09-03

Logs of which AI crawlers reach your pages exist, but the comparison table marks AI crawler monitoring absent on the entry Starter plan and present from Professional up.

Source retrieved 2026-10-03

AI bot and coding-agent hits are reported per page, but only after you connect your own Cloudflare, Vercel or forwarded server logs.

Source retrieved 2026-10-05

The hosted workbench shows no bot traffic at all; AI crawler reporting exists only in the self-hosted GEOFlow system, whose data centre aggregates content, distribution, visits, top content, AI crawlers and trends.

Source retrieved 2026-09-19

AI crawler visibility exists as the Enterprise 'Crawls' feature; the comparison table shows a dash for it in the Free column, so self-serve users do not get it.

Source retrieved 2026-09-24

You learn which AI crawlers your robots.txt permits, not which ones actually hit your server; real log-file analysis appears only in the paid GEO Audit deliverable.

Source retrieved 2026-09-14

A dedicated pixel-based module reports bot visits, distinct crawler types, crawl frequency and spoofed-bot detection for your own site.

Source retrieved 2026-09-25

Crawl auditing is a documented service covering robots.txt, Search Console index coverage and crawl depth, but it addresses search engine crawling; no AI-bot log file or CDN bot reporting is offered as a deliverable.

Source retrieved 2026-09-14

Bot-level crawl logging exists, but the comparison table checks AGENTS & CRAWLERS ANALYTICS and Site 360 for Enterprise only; Core and Pro get traffic attribution instead.

Source retrieved 2026-09-15

A dedicated AI Traffic Analyzer reports which AI crawlers hit which pages and when, naming GPTBot, ClaudeBot, PerplexityBot and Google-Extended.

Source retrieved 2026-10-07

Crawler accessibility is diagnosed within the technical work and the team advertises modern log file auditing expertise, but the vendor publishes no standing AI-bot traffic report a client can watch, so this is audit work rather than ongoing analytics.

Source retrieved 2026-09-26

It claims to show which bots crawl you and how often, but the same page states the mechanism is active access testing rather than log analysis. This is reachability, not a crawl-log report.

An AI Bot Traffic page reports named crawler hits per page with region-level crawl activity and blocker detection.

Source retrieved 2026-09-03

A separate free WordPress plugin logs AI bot hits by date, page and model and feeds them to the dashboard: crawler analytics, not the visibility tracker itself.

Source retrieved 2026-09-03

Agent Analytics reads server logs to identify AI bots, but the vendor scopes it to Scale plans with per-URL breakdowns reserved for Enterprise.

Source retrieved 2026-09-27

The free report checks robots.txt for AI-crawler blocking, which is a configuration check rather than log-level visibility into which bots actually crawled the site.

Source retrieved 2026-09-27

A free public tool tests whether named AI crawlers can reach your pages, but the vendor calls results directional because probes come from its own server IP rather than verified crawler ranges.

Source retrieved 2026-09-28

A full bot-analytics surface reading server logs for named crawlers, with crawl frequency by page class and a crawl-to-citation lag model; no plan row rations it, so tier limits are undisclosed.

Source retrieved 2026-09-03

AI crawler access is audited and reported for the four named bots, but this arrives as an accessibility report inside the engagement rather than a self-serve bot-traffic view.

Source retrieved 2026-09-28

AI bot crawls are read from your own request logs and split by engine, but the feature is withheld from the entry tier: its comparison row reads Not included for Essential.

Source retrieved 2026-09-29

Agent Analytics reports which AI bots hit your pages, but it needs a log connector and starts from the Standard plan, not Lite.

Source retrieved 2026-09-29

It checks whether named AI crawlers are permitted by robots.txt and monitors crawler access over time, but publishes nothing about reading your server logs to show which bots actually fetched pages.

Source retrieved 2026-10-07

Agent Analytics ingests your own server or CDN logs through eight integrations and reports per-bot visits, response statuses and paths; the pricing tables never mention it, so tier availability is unstated.

Source retrieved 2026-09-03

Reads robots.txt to report which AI bots are allowed or blocked; it is an access check, not server-log analytics of crawls that actually happened.

Source retrieved 2026-09-29

Agent Analytics reads server or CDN logs to show verified AI bot hits, with unlimited tracked domains on every plan.

Source retrieved 2026-09-09

Crawler log ingestion and Agent Analytics are real but gated: the Crawler Logs row is crossed out on the entry Essential plan and starts at 25M log lines on Professional.

Source retrieved 2026-09-30

Business and Enterprise only. Classifies 13 published AI user agents from server or CDN logs via nine collectors, keeping bounded daily aggregates for 30 analytic days.

Reports whether AI bots are allowed by robots.txt, not observed bot hits from server logs.

The audit checks whether named AI bots are blocked on a URL and penalises each one, but no server-log or crawl-traffic view of actual bot visits is published.

Source retrieved 2026-09-30

Crawler analytics is listed on all three self-serve plans and reports which AI bots hit which pages, how often, and with what errors, in real time.

Source retrieved 2026-09-30

Crawl and index health comes from Bing Webmaster, not AI-bot log analysis of your own site

Agent Traffic classifies training, indexer and retrieval bots; needs a CDN or hosting integration.

Source retrieved 2026-09-02

Crawler log analysis is part of technical optimisation.

You see whether eight named AI bots are blocked by robots.txt and how many pages they cannot reach, which is a configuration check rather than log analysis of real crawler hits.

Source retrieved 2026-09-18

Robots.txt is parsed per diagnosis to name blocked AI search crawlers, and the API exposes per-page answer-crawler fetches and AI referrals.

Source retrieved 2026-10-03

The crawler audits which AI bots can and cannot reach each page and flags JS-blocked content, but the vendor never describes log-level reporting of actual AI crawler visits or hit counts.

Source retrieved 2026-09-15

Server-side crawler logs are classified into five purpose classes across thirty-plus signatures, but it needs a paid plan and a connected Cloudflare, Vercel or Netlify source.

Source retrieved 2026-09-16

It checks whether named AI crawlers are permitted to read the site, not which bots actually visited; no log-based crawl analytics is documented anywhere.

Source retrieved 2026-09-18

AI Bot Analytics is ticked on every tier and logs bot visits, bot types and failed crawls server-side.

Source retrieved 2026-09-02