Research report · data-report
AI crawler analytics: a census of 109 listings
27 of 109 listings answer yes for “AI crawler analytics”. Counted from our own datasheet, with the query that reproduces every figure.
On this page
AI crawler analytics, across 109 settled listings
Of the 109 Published listings whose datasheet settles “AI crawler analytics”, the largest group is “No” at 46 (42%). Measured 2026-09-09.
Explore the matching tools
AI crawler analytics · Datasheet criterion crawler_analytics · Report counted .
Current listings as of ; this set may differ from the report's original sample. Includes “Yes” and “Qualified” answers only. Read the conditions on qualified answers before treating them as a match. “No”, “Not applicable” and “Not established” answers are excluded.
View 54 current matching records
- Adobe Brand Visibility Yes
Agentic Traffic breaks CDN log hits down by user agent, page, market and success rate, but stays blank until CDN log forwarding is configured.
- AEOlens Yes
Server-side capture of AI bot hits, verified by ASN and reverse-DNS; basic tier free, full analytics from Starter.
Source retrieved 2026-09-02
- Ahrefs Brand Radar Yes
Bot Analytics shows AI crawler visits in real time and is free while in beta.
Source retrieved 2026-09-02
- AI Sightline Yes
Server-side AI bot crawl and referral tracking on every plan; 2 crawlers on Free rising to all 17 on Agency.
Source retrieved 2026-09-02
- AI Visibility Report Group Qualified
Checks whether named AI crawlers are permitted (OAI-SearchBot, GPTBot, robots.txt, llms.txt) and measures retrieval per platform; no server-log view of actual bot visits.
Source retrieved 2026-09-02
- Analyze AI Qualified
Not a first-class report: two of the vendor's own comparison tables mark AI crawler analytics as reachable only through workflow nodes, and AI Traffic Analytics measures GA4 referral sessions, not bot hits.
- ApexGEO Yes
Classifies AI-crawler fetches from server logs or a REST ingest endpoint and verifies each source IP against the operator's published ranges to flag spoofed bots.
Source retrieved 2026-09-02
- AthenaHQ Qualified
It diagnoses whether AI crawlers can reach your pages and manages their access, but nowhere claims a log of which AI bots actually crawled the site.
- Bloomiro Yes
AI Crawl classifies crawler hits and is metered at 1 credit per 100k hits; get_robots_txt reports rules for search and AI user agents.
Source retrieved 2026-09-02
- Brandlight Yes
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
- BrightEdge Yes
AI Agent Insights separates real-time answer fetches, learning crawls and indexing per engine; stated as available for enterprise customers.
- Canonry Yes
Ingests server logs from Cloudflare, Cloud Run, Vercel and WordPress and keeps AI crawler hits, user fetches, citations and referrals as separate events.
- CiteVista Qualified
It reports whether six named AI crawlers are permitted for a URL, including CDN rules that silently override robots.txt, but these are permission checks, not log-based counts of real bot hits.
Source retrieved 2026-09-03
- Cognizo Yes
Logs indexing, retrieval and training visits from AI bots and attributes GA4 sessions
Source retrieved 2026-09-02
- Conductor Qualified
Log file analysis shows AI bot crawling, but it is an add-on on Essentials/Growth and only included on Enterprise.
- EdenRank Qualified
A free robots.txt checker scores which AI crawlers are allowed or blocked; the vendor states no log-based view of crawls that actually happened.
- Evertune Qualified
Bot Analytics reports which AI bots crawled which pages, but the pricing page lists it only under Enterprise, on top of Pro.
- Finseo Qualified
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
- Foglift Yes
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
- Frase Qualified
AI bot/crawler monitoring starts on Professional; the Starter column in the pricing comparison table shows a dash.
- Gauge Yes
Reads Cloudflare or Vercel server logs and classifies AI bot and coding-agent requests by page.
- geoSurge Qualified
Crawls reports which AI bots reach the site and how often, but only on Enterprise.
Source retrieved 2026-09-02
- GEO Tool Qualified
It checks which AI crawlers robots.txt locks out: a directive check, not a log of which bots actually hit your site.
- GetCito Yes
A pixel-based product tracks AI bot visits, frequency and authenticity per page.
Source retrieved 2026-09-02
- Goodie Yes
Logs each AI bot visit with pages, frequency and errors.
- Indexly Yes
Logs each AI crawler hit by URL and frequency and links it to whether the resulting answer cited you.
- iPullRank Qualified
The free scan reports AI crawler access from robots.txt and raw HTML and states its own blind spots; no bot-traffic or log-file analytics dashboard is offered.
Source retrieved 2026-09-02
- Keyword.com AI Visibility Qualified
A free simulator sends real requests as 12 AI user-agents to test access; it does not report bots that actually crawled your site
- Knowatoa Qualified
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.
- Limy Yes
An AI Bot Traffic page reports named crawler hits per page with region-level crawl activity and blocker detection.
Source retrieved 2026-09-03
- LLMClicks.ai AI Visibility Tracker Yes
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
- LLM Pulse Qualified
Agent Analytics reads server logs for AI bots on Scale; per-URL breakdowns only on Enterprise.
Source retrieved 2026-09-02
- Minuttia Qualified
It checks robots.txt and whether AI search crawlers are blocked, but publishes no per-bot crawl log analytics.
- Omniscient Digital Qualified
The free tool tests whether each AI crawler can reach a URL, not which bots actually crawled the site; log-file analysis is sold separately and framed around search engines.
Source retrieved 2026-09-02
- OmniSEO Yes
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
- OMNIUS Yes
AI crawler auditing and monitoring are listed activities, with GPTBot indexability as a stated output.
Source retrieved 2026-09-02
- Orchly Yes
Reads hosting/CDN logs to show AI bot crawls in real time.
Source retrieved 2026-09-02
- OtterlyAI Qualified
Agent Analytics classifies real bot hits via a server/edge integration, but it is listed only from Standard upward, not on Lite.
- Peec AI Yes
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
- Prizvox Qualified
Shows which AI crawlers robots.txt allows or blocks (GPTBot, ClaudeBot, PerplexityBot, Google-Extended); it never reads server logs, so it cannot show which bots actually visited.
- Profound Yes
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
- Promptwatch Qualified
Crawler log ingestion is crossed out on Essential in the pricing comparison; Professional includes 25M crawler log events a month and Business 100M.
Source retrieved 2026-09-02
- Qwairy Qualified
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.
- Rankability Qualified
Reports whether AI bots are allowed by robots.txt, not observed bot hits from server logs.
- Rankscale Qualified
The audit detects and penalises AI bots blocked from a URL; it does not report crawler hits from your logs.
Source retrieved 2026-09-02
- Rankshift Yes
AI crawler logs with pages hit, frequency and errors; included on every plan.
Source retrieved 2026-09-02
- RankZero Qualified
Crawl and index health comes from Bing Webmaster, not AI-bot log analysis of your own site
- Scrunch AI Yes
Agent Traffic classifies training, indexer and retrieval bots; needs a CDN or hosting integration.
Source retrieved 2026-09-02
- Searchable Yes
Crawler log analysis is part of technical optimisation.
- Semrush AI Visibility Toolkit Qualified
The audit checks whether AI bots can crawl the site and what blocks them; the vendor does not claim a log of which bots actually crawled.
- SEORCE Qualified
The crawl audits whether named AI bots can reach your content and flags robots.txt rules blocking them; the vendor publishes no AI bot hit counts or server-log analytics.
- Trakkr Yes
AI bot requests tracked per bot and per page, with nine MCP tools and a Looker dataset for it
- VisibAI Qualified
Checks whether AI crawlers are allowed and how the site responds to each user agent; it does not report actual bot visits.
- Writesonic Yes
AI Bot Analytics is ticked on every tier and logs bot visits, bot types and failed crawls server-side.
Source retrieved 2026-09-02
The population
115 listings in this index are Published. This is the population as of 2026-09-09. 109 of the 115 published listings in this index carry a settled answer for “AI crawler analytics”. That row asks: Can you see which AI bots crawl the site and what they read? The other 6 have no recognised stored answer on this row and are left out of every figure below rather than counted as a no.
Findings
-
27 of the 109 settled listings answer “Yes” for “AI crawler analytics”. That is 25% of the settled set.
-
27 of the 109 settled listings answer “Qualified” for “AI crawler analytics”. That is 25% of the settled set.
-
46 of the 109 settled listings answer “No” for “AI crawler analytics”. That is 42% of the settled set.
-
9 of the 109 settled listings answer “Not established” for “AI crawler analytics”. That is 8% of the settled set.
1 of those yes answers is LLMClicks.ai AI Visibility Tracker, which still answers yes for “AI crawler analytics”. Its listing carries the stored answer and links to the source recorded for it. This is one worked example, not an independent audit of every source in the census.
What we counted, and how
Each figure above is a count over the “AI crawler analytics” row of the listing datasheet, taken from the same stored answer the listing page renders. The denominator is the 109 listings whose answer is settled, meaning one of yes, qualified, no, does not apply, not established. It is not the 115 in the index, because a missing answer is not evidence of absence. Every number here is stored with the read-only query that reproduces it and re-run every sixty seconds against the live corpus, so a figure that stops reproducing surfaces as drift rather than as a stale sentence nobody notices. Our full method covers how a datasheet row is settled in the first place.
Limitations
This counts stored datasheet answers, not independently tested capabilities. A sourced answer can record a vendor statement or our reading of published evidence; this census does not re-fetch those sources. “Not established” means we have not established an answer. That can reflect vendor nondisclosure, blocked evidence, or unfinished research, not a no. An absent or unrecognised answer is excluded rather than treated as a researched finding. The figures are restated when the stored corpus changes; the date above is the count used for this published version, not a new verification of the vendors.
Get the next report
New tools rankings and fresh data reports. One short email, one-click unsubscribe.