Measuring AI citations means running the same question through ChatGPT, Perplexity, and Google’s AI Overviews on a schedule and logging whether each one names your site. There is no citation-tracking API from any of the three, so this stays a manual, sampled check: build a panel of 20-30 real buyer questions, ask each assistant every question, record who gets cited, and re-run the panel every one to two weeks to see the pattern move. This is a different measurement from AI-referral traffic in GA4, which only counts clicks – a citation with no click never shows up there at all.
“Are we getting cited by AI?” does not have a dashboard answer yet. OpenAI, Perplexity, and Google do not publish a citation-tracking API for any of their assistants, so the only direct signal is asking the assistant a question and reading what it says back. That is manual and does not scale past a sample – but it is the same signal every AI-SEO practitioner is working from right now, and it is worth doing on a schedule instead of once.
The query-panel method in four steps
The method is the capsule above, expanded. First, build a fixed panel of questions your actual buyers ask – not keyword-tool guesses. Second, run the full panel against each assistant you care about, same questions, same order, every time. Third, log the result for each question and engine: cited, not cited, and if cited, whether it was your page, a competitor’s, or a source you did not expect. Fourth, compare the log across runs to see whether citations are moving, and treat referral-traffic tracking in GA4 as a separate, complementary check rather than a substitute.
Building a 20-30 question panel from real buyer questions
Pull the panel from the same places a good keyword list comes from: sales call transcripts, support tickets, competitor comparison pages, and the questions your own content already tries to answer. A range of 20 to 30 questions is a reasonable starting size for most single-product or single-category sites – enough to catch a pattern across a topic, small enough to run by hand in under an hour. Write the questions the way a buyer would type them, not the way a keyword tool would phrase them; assistants are answering a question, not matching a query string. Keep the panel fixed once you set it, so later runs are comparable to earlier ones, and only add or retire questions deliberately, noting when you did it.
Logging and scoring citations across ChatGPT, Perplexity, and AI Overviews
Ask each panel question directly in ChatGPT and Perplexity, since both are conversational products built for exactly this kind of query. For Google, search the same question and check whether an AI Overview appears and who it cites – Google’s own documentation confirms AI Overviews and AI Mode pull from the same crawling and indexing pipeline as regular Search, and a page has to already be “indexed and eligible to be shown in Google Search with a snippet” before it can appear as a supporting link in either feature. There is no separate AI-only crawler to check the way there is for ChatGPT’s OAI-SearchBot or Perplexity’s PerplexityBot.
A simple log is enough: one row per question per engine per run, with columns for the date, whether your site was cited, which competitor (if any) was cited instead, and a short note on the answer’s framing. Score it however is useful to you – a raw citation rate per engine, a trend line over successive runs, or just a running list of which competitors keep showing up in your place. The scoring matters less than running the same panel consistently enough to compare one period to the next.
Separating citations from referral traffic – they are different metrics
A citation and a referral click are not the same event, and conflating them will make the picture look worse than it is – or better. GA4 added a native “AI Assistant” default channel group that automatically classifies referral sessions from ChatGPT, Gemini, and Claude, and I have written up how to check it and build a manual fallback separately. But that channel only counts a session created when someone clicks through from an assistant’s answer with an intact referrer header. An assistant can read your page, quote it, and name you as the source without the reader ever clicking – and that interaction creates no GA4 session at all, on any channel. The query-panel method above is the only way to see that side of it; GA4 referral tracking answers a different, narrower question about traffic that actually landed.
This site’s own numbers make the distinction concrete rather than theoretical. As of this piece’s most recent check, this property’s GA4 AI Assistant channel shows zero sessions, and the query panel behind this check (kept in this site’s own tracking file) has zero questions populated – the mechanism exists and the daily routine is built to run it, but it has not been seeded with real questions yet on this property. That is not a claim this site is invisible to AI assistants; it is what the two measurements actually show today, stated plainly rather than implied otherwise.
Limits, noise, and how often to re-run the panel
Treat every result as a sample, not a census. Assistants can answer the same question differently across runs even with no change on your end – model updates, retrieval randomness, and the assistant’s own session context all introduce noise a single check cannot separate from a real shift. A panel of 20-30 questions checked once tells you almost nothing about whether the underlying pattern is moving; the value comes from repeating the exact same panel and watching the trend across several runs. Re-running every one to two weeks is frequent enough to catch a real trend without turning an inherently manual process into a full-time job, though the right cadence depends on how much time you have and how quickly your content changes.
The other limit worth naming: this method cannot rule out a citation you did not think to ask about. A 20-30 question panel is a sample of your topic, not the whole thing, so a clean row of “not cited” answers only means the questions you tested were not cited – not that no question would be. Widening the panel over time, and retiring questions that stop being representative, keeps the sample honest.
Frequently asked questions
Is there a tool that tracks AI citations automatically?
Not from the assistants themselves. OpenAI, Perplexity, and Google do not publish a citation-tracking API for ChatGPT, Perplexity, or AI Overviews, so the direct signal – asking an assistant a question and reading the answer – stays manual. Third-party AI-visibility tools exist that automate parts of this same query-panel idea, but they are running the same manual check at scale on your behalf, not reading a citation feed the platforms provide.
Does a citation always show up as GA4 referral traffic?
No. GA4’s AI Assistant channel only counts sessions created when someone clicks through from an assistant’s answer with an intact referrer header. If an assistant cites or quotes your page but the reader never clicks, or clicks from an app that strips the referrer, that interaction creates no session in GA4 on any channel – not AI Assistant, not Direct, nowhere. Citation tracking and referral-traffic tracking answer different questions and need different methods.
How many questions should be in an AI-citation tracking panel?
20 to 30 real buyer questions is a reasonable starting size for most single-product or single-category sites – enough to reveal a pattern across a topic without making a manual check unmanageable. Keep the panel fixed between runs so results are comparable over time, and widen it deliberately as your content or product coverage grows.
For the tactics that actually move whether an assistant cites you in the first place – crawler access, extractable structure, entity clarity, and why schema markup and llms.txt do not reliably help – see how to get cited by ChatGPT and Perplexity. For the GA4 setup behind the referral-traffic side of this check, see how to track AI referral traffic in GA4. For the broader terminology this piece sits inside, GEO vs SEO vs AEO and what an AI SEO agent actually is both cover adjacent ground.
Leave a Reply