DataForAEO · the registry of AI-search data
How often ChatGPT, Claude and Perplexity read your pages because someone asked, what they answer, whom they cite, and how much demand there is for a keyword. Measured where it can be, labelled where it is modelled, served as one API.
POST /api/collect/ai-bots
Authorization: Bearer aeoc_…
{ "events": [{
"ua": "…; ChatGPT-User/1.0; +https://openai.com/bot",
"path": "/pricing",
"ip": "104.210.139.200"
}] }202 Accepted
{ "stored": 1, "ignored": 0 }
→ stored row
{ "day": "2026-11-12", "path": "/pricing",
"bot": "ChatGPT-User", "kind": "user",
"verification": "verified", "hits": 1 }01 · In figures
02 · Datasets
Each entry says what it answers, where the data comes from, and whether you can use it today.
How often AI assistants read a page because a person asked them something, per page per day.
A collector on participating sites. Each hit is checked against the vendor’s published IP ranges.
day · path · bot · kind · verification · hits
Weekly Bing search volume for a keyword, and an estimate of AI-assistant demand for it.
Bing Webmaster keyword stats (measured) × intent share (modelled, always labelled an estimate).
keyword · market · week · bing · ai_estimate
What each engine answers for a prompt, which brands it names, which URLs it cites, and at what rank.
Live calls to 3 AI engines, the same pipeline as the weekly AEO Toolkit tracker.
prompt · engine · model · brands · citations[rank, url]
Which domains and pages get cited for a topic, and how that share moves week to week.
Every answer above, combined across workspaces. Published only as aggregates over 5 or more.
topic · domain · share · rank distribution · week
Visits from chatgpt.com, perplexity.ai, Gemini, Copilot and claude.ai. Paired with C, the click-through rate from AI answers.
GA4, through the site owner’s own connection.
week · referrer · sessions · landing page
03 · Definition
Answer engine optimization (AEO) is the work of getting named and cited by AI assistants instead of only ranking in a list of links. Search engine optimization has had data for twenty years: keyword volume, rankings, backlinks. AEO has had almost none, because AI companies publish no query volume and every tool keeps its answers to itself.
Data for AEO is the missing evidence: how often an assistant actually reads a page because a person asked (measured on the server, not guessed), what the assistants answer and whom they cite across 3 engines, and keyword demand that says plainly which part is measured and which is an estimate. DataForAEO collects it and serves it as an API.
04 · Method
When someone asks an assistant a question and it reads a page to answer, the site serves a request from ChatGPT-User, Claude-User or Perplexity-User. Each one is a person’s question landing on that page. We count them separately from search-index refreshes and training crawls.
A User-Agent is a claim, so the IP behind it is checked against the published ranges of 3 vendors. Every count carries verified, unverified or unknown, and every modelled number carries the word estimate. The full list of agents, what each one does and how to verify it is in the AI crawler list.
advancelabs.dev · first hours · 2026-11-12
| Bot | Kind | Hits |
|---|---|---|
| PerplexityBot | search | 10 |
| Amazonbot | search | 8 |
| ChatGPT-User | user | 3 |
| OAI-SearchBot | search | 2 |
| GPTBot | training | 1 |
| Bytespider | training | 1 |
| Meta-ExternalAgent | training | 1 |
One site, a few hours, collected before IP checks went live, so every row is unknown. A sample of the shape, not a market figure.
05 · Collector
A few lines in a Next.js proxy or a Cloudflare Worker. It sends only AI-bot requests, after the response, so pages never wait. Your own pages’ AI demand shows up in AEO Toolkit, and the anonymous aggregate feeds the registry.
export function proxy(req, event) {
const ua = req.headers.get('user-agent') ?? '';
if (!AI_BOTS.test(ua)) return;
const events = [{
ua,
path: req.nextUrl.pathname,
ip: req.headers.get('x-real-ip'),
}];
event.waitUntil(fetch(COLLECT_URL, {
method: 'POST', headers,
body: JSON.stringify({ events }),
}));
}06 · Questions
Data for AEO (answer engine optimization) is evidence about how AI assistants like ChatGPT, Claude, Perplexity and Gemini find, read and cite the web: how often they fetch a page because someone asked, what they answer, and whom they cite. DataForAEO collects it and serves it as an API.
Both, and every number says which. Bot fetches are measured: each one is a request a site served. Keyword AI volume is modelled from Bing volume and is labelled an estimate. No AI company publishes query volume, so anyone selling it as measured is estimating too.
A User-Agent can be faked, so each hit from OpenAI, Anthropic or Perplexity is checked against the IP ranges those 3 vendors publish and counted as verified, unverified or unknown. Bots whose vendors publish no list stay unknown.
Daily counts per page, bot, kind and verification. No IP addresses, no query strings, no cookies and no human traffic: the snippet on your site only sends requests whose User-Agent names an AI bot.
Both are built by Advance Labs. DataForAEO is the data; AEO Toolkit is the dashboard where you install the collector, see your own pages’ AI demand, and track whether AI names your brand.
No. DataForAEO is built and run by Advance Labs Inc. in London, Ontario. It is not affiliated with, endorsed by or connected to DataForSEO OÜ.
API access will be pay per request, prepaid, with a ceiling you set. The collector is free for your own site, because every site that runs it makes the dataset better. Prices are not published yet; request access and we will send them.