# AI crawler analytics: a census of 109 listings

> Source: CitedIndex — https://citedindex.com/blog/crawler-analytics-census (sourced research)
> By CitedIndex Editorial · Published 2026-09-06 · Updated 2026-09-10

_27 of 109 listings answer yes for “AI crawler analytics”. Counted from our own datasheet, with the query that reproduces every figure._

## 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.

| Listings | Count | Share of 109 |
| --- | --- | --- |
| Yes | 27 | 25% |
| Qualified | 27 | 25% |
| No | 46 | 42% |
| Not established | 9 | 8% |

Denominator: 109 Published listings whose datasheet settles “AI crawler analytics”. Method: Counted from the stored datasheet answer for “AI crawler analytics” across every Published listing, excluding the 6 without a recognised stored answer on that row.

## 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

1. 27 of the 109 settled listings answer “Yes” for “AI crawler analytics”. That is 25% of the settled set.

2. 27 of the 109 settled listings answer “Qualified” for “AI crawler analytics”. That is 25% of the settled set.

3. 46 of the 109 settled listings answer “No” for “AI crawler analytics”. That is 42% of the settled set.

4. 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](/llm-clicks) carries the stored answer and links to [the source recorded for it](https://llmclicks.ai/llm-traffic-tracker/). 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.

---

Tags: data-report, census