You can track how often ChatGPT and Perplexity cite your brand with a spreadsheet and a frozen list of buyer questions in about an hour a week. Most teams who try still end up with a number they cannot trust, and the failure is statistical before it is ever clerical. SparkToro's research found AI engines are highly inconsistent when recommending brands, and Search Engine Land's coverage of the same study notes the recommendation lists rarely repeat exactly across runs of the same prompt. A tracker that records one answer per question is logging noise with a date attached.
The protocol that survives those findings is short. Write down 10 to 25 questions your buyers actually ask, ask each in two or three phrasings on every engine once a week, and log who was mentioned, who was cited, and who was recommended in every answer. Then compute rates per question per engine, rerun the identical set monthly, and compare waves. A 2026 variance-components study found run-to-run noise large enough to swamp real differences in small samples, and work on quantifying uncertainty in AI visibility shows why a rate without a sample size attached is not yet a measurement.
The hour is worth spending. G2's research found AI chatbots and review sites are now the two biggest influences on B2B shortlists, 51% of software buyers now start research with an AI chatbot more often than with Google, and ChatGPT alone reached roughly 800 million people by spring 2025. The engines are already sampling your brand for buyers every day. The open question is whether anyone on your side is counting.
Why is one ChatGPT answer not a measurement?
Because the same question produces materially different answers across runs, and the spread is wide enough to reverse your conclusion. The variance has two mechanical sources. When ChatGPT decides to search, it issues one or more targeted queries against its retrieval backend, so different runs can pull different pages before a single word is generated. The model then samples during generation, so even identical retrieved context can name a different set of vendors.
Sample size is the only defense. The platform medians in the uncertainty analysis differ engine by engine, which means the run count that stabilizes a ChatGPT rate may not stabilize a Perplexity rate. Pool answers across phrasings and weeks rather than rerunning one prompt, and treat close rates as ties until more data separates them.
This is also why a screenshot of one good answer belongs in a slide deck and never in a decision. A single citation proves you can appear. Only a base rate over repeated trials tells you how often you do.
What exactly should you count in each answer?
Three separate events per answer: mention, citation, and recommendation, each in its own column. A mention is your name appearing in the answer text; a citation is your page linked or referenced as a source. A recommendation is the engine advising the buyer to choose you. The IAB's 2026 measurement guidance makes a similar cut, grouping AI visibility into Presence, Prominence, Portrayal, and Persuasion instead of one blended figure.
Record the answer's sources even when none are yours. Profound's citation research found more than 4 in 10 AI citations point to pages brands do not control, so the log needs a column for the third-party pages that carry or omit your name. A competitor can win an answer entirely through a review site while your domain never enters the citation list.
Keep the recommendation column strict, because that rung carries the revenue. 6sense found buyers evaluate roughly five vendors and most of that list is set before contact. If citations rise while recommendations stay flat, you have earned sourcing without earning the shortlist, and only a log that separates the two events can show you that gap.
What does a working manual tracking protocol look like?
A frozen question set plus repeated runs, logged so mention and citation never blend, executed on a calendar. The table is the protocol; the rest of this piece is the reasoning behind its rows.
| Step | What to do | What it protects against |
|---|---|---|
| 1. Freeze the question set | Write 10 to 25 questions a real buyer would ask, in buyer language, and lock them for the quarter | Rotating questions destroys trend comparability between waves |
| 2. Repeat and vary | Ask each question in two or three phrasings on every engine, weekly for at least three weeks, with web search active | Single runs read variance as a verdict |
| 3. Log events separately | Record mentioned, cited, and recommended in their own columns, plus every source URL the answer used | Conflating mention with citation inflates the number |
| 4. Archive the answers | Save full answer text with date, engine, account, and search mode | A rate with no underlying answers cannot be audited later |
| 5. Compute per-question rates | Appearance and citation rate per question per engine, with no blended score | An average across questions hides which questions you are losing |
| 6. Rerun monthly, identically | Same questions, same engines, same run counts, same account setup | Changed conditions between waves masquerade as market movement |
Three execution details do most of the work. Run ChatGPT with web search active, because without retrieval it answers from training memory and its citations of current pages thin out. Use a clean account and a fresh chat per run, since engines adapt to conversation history and stored context, and a personalized answer is yours rather than your buyer's. Save the full answer text every time, because the sources cited in March are the only way to explain a rate that moves in April.
Budget honestly before committing. Fifteen questions in three phrasings across three engines is 135 answers a week, more than an hour of logging even at 30 seconds per answer. Vendors automate this grind at scale: Semrush's expanded AI Visibility Index analyzed 126 million AI search prompts. Your 135 answers a week do not need that breadth; they need consistency, which is the one thing a spreadsheet delivers for free.
How do you confirm your pages can be cited at all?
Before reading a zero citation rate as a verdict on your content, verify that the engines can retrieve your pages. Seer found 87% of SearchGPT citations matched Bing's top results, so weak Bing coverage is a real risk in ChatGPT's search layer, however well you rank on Google. Check index coverage there before changing a word of copy.
Then check who is actually reaching your server. OpenAI documents four relevant user agents for its crawling and retrieval, and Cloudflare's crawler analysis measured GPTBot's share of crawl requests rising from 2.2% to 7.7% in a year. If your robots rules block those agents, or your logs show they never arrive, your citation rate has a mechanical explanation.
Rendering is the quietest failure. Vercel's crawler research with MERJ documented that major AI crawlers read raw HTML and do not execute JavaScript, so client-rendered content is an empty shell to the engine you are measuring. Being retrieved is not being cited, either: AirOps' March 2026 analysis of 548,534 pages ChatGPT retrieved found only 15% were cited in the final answer. Fetch your key pages with JavaScript disabled and read what survives before blaming the model.
What will manual tracking miss no matter how careful you are?
Four things, and naming them is part of measuring honestly. The first is decay: models retrain, sources shift, competitors publish, and a wave from last quarter describes a market that has already moved. A protocol run once is a snapshot. Only the standing habit produces a trend.
The second is conversation shape. Tracked prompts are single questions, while real buyers ask follow-ups. A 2026 study of 8,133 multi-turn human-LLM conversations, including 670 English commercial multi-turn conversations, shows commercial research unfolding across turns that a fixed prompt list never reproduces. Your protocol measures the opening move of a longer game.
The third is scale. In Profound's 7.5 million-conversation en-US sample, the share of ChatGPT conversations classified commercial rose from 13.9% to 19.2% in a year, and 25 tracked questions is a keyhole view of that activity. Profound's "more than doubled" volume figure is an extrapolation from estimated weekly users. The fourth is vantage: engines shape answers with account context and history, so a tracking account sees one version of a personalized surface.
None of this makes the spreadsheet worthless. It makes the output directional evidence with known blind spots, which is more than most teams have today, and it defines exactly what an automated system has to add to earn its cost.
How does Trovance track AI citations without the spreadsheet?
Trovance runs this article's protocol as a standing system instead of a monthly chore. You define the tracked questions your buyers actually ask, and it sweeps them across AI engines every week, preserving every answer as a snapshot with its full context: who was mentioned, who was cited, who was recommended, and which sources carried the answer.
Because every snapshot is preserved, share of answer becomes a base rate instead of an anecdote. You can compare waves and see how often you appear for each question on each engine, with the variance visible rather than hidden inside an average. When a rate moves, the archived citations let you diagnose the cause: a source that dropped you, or a competitor page that displaced yours.
The record then feeds decisions. The Brain keeps the claims you are entitled to make with the proof behind each one, and recommended actions name the specific asset the evidence record says is missing for a question you are losing. Drafts are written in your voice from your voice guidance and research sources, a person edits and approves everything before it publishes, and the next analysis cycle reruns the same questions to verify whether the answer actually moved.
What Trovance will not promise is a citation, because the engines are probabilistic and rerunning a question is observation, not control. It also will not compress your visibility into one universal score, since run-to-run variance is exactly what a single number hides. What it keeps is the evidence: every answer with its sources, wave after wave, so decisions rest on current data instead of a screenshot from last quarter.
What should you do this week?
Write the question set today and freeze it: 10 to 25 questions a buyer would ask before choosing in your category. Run the first wave across ChatGPT, Perplexity, and Claude, two or three phrasings per question, and log every answer against the table above. Before interpreting a single number, run the retrievability checks, from Bing coverage to a JavaScript-disabled fetch of your key pages.
When the data shows a question you are losing, spend on substance before phrasing. The GEO study (Aggarwal et al., KDD 2024) found adding statistics, quotations, and citations lifted citation visibility by roughly 30 to 40% in its benchmark, while C-SEO Bench (NeurIPS 2025) found most rewrite methods largely ineffective and often harmful to citation rank, with gains shrinking as more sites adopted them. Those rewrite conditions included adding statistics, quotations, and citations, so evidence on the page is the better bet, not a proven lever. Rewording has even less behind it.
Accept the timeline the variance imposes: even a real improvement needs two or three waves to show above the noise, and anyone promising a guaranteed citation is selling against the published data. If you want the base rates without the weekly spreadsheet, start a free Trovance trial and put your buyer questions on a standing schedule with every answer preserved.
Measure without fooling yourself
How to measure AI search visibility without one score: why per-question rates beat a blended index
There is no such thing as an AI visibility score: the case against single-number dashboards
The 10-minute audit of what ChatGPT tells buyers about you: the fast first pass before a full protocol
The prompt panel is measuring the wrong question: what tracked prompts can and cannot represent
Act on what the log shows
Why your business isn't showing up in ChatGPT: the diagnosis to run when your rate is zero
Why ChatGPT recommends your competitor: five failure modes behind a lost recommendation
Where AI citations come from: the third-party sources that decide most answers
A visibility gap is not a content brief: how to turn a low rate into the right work
