How to Track Brand Mentions in AI Search

How do you track brand mentions in AI search?

Tracking brand mentions in AI search means running a fixed set of prompts against each AI assistant on a schedule and reading every answer that comes back. There is no index to query and no alert to subscribe to. The only way to know what an assistant says about your brand is to ask it and record what it said.

A working setup has four parts, and the order matters:

1. A prompt set. The questions your buyers actually ask, not your keywords. A keyword is what someone types into Google; a prompt is a whole question, and prompt research is a different exercise from keyword research.
2. A schedule. Every prompt asked repeatedly, so a result can be read as a trend rather than an anecdote.
3. A record per answer. Whether the brand was named, where it sat among the brands listed, which sources the answer cited, and which competitors appeared beside it.
4. An honest denominator. How many checks ran, over what period, and how many produced no readable answer at all.

Most guides stop after the third part. The fourth is the one that decides whether the first three produce a number worth acting on, and it is where this article spends its time. Getting started is easy. Knowing whether your tracker is telling you the truth is not.

What’s the difference between an AI mention and an AI citation?

An AI mention is an answer that names your brand in its text. An AI citation is an answer that links one of your pages as a source. They are different events, they are recorded separately, and a brand-monitoring setup that conflates them will misread its own data.

They come apart constantly, in both directions. An answer can cite your page while recommending a competitor, which reads as a win in a citation report and is a loss in the market. An answer can name your brand from the model’s training with no link at all, which a link-based tracker never sees.

For brand monitoring, the mention is the event that matters. Being named in the answer is what a reader takes away; a citation is a link in a list most readers never open. Pick the AI mention as your primary metric and treat citations as evidence of how the mention was earned.

Being cited still pays, and the size of it is measurable. In its April 2026 update, covering 53 brands, 5.47 million queries and 2.43 billion organic impressions, Seer Interactive found that being cited in an AI Overview delivers 120 per cent more organic clicks per impression than not being cited. That is the argument for tracking both, and for never merging them into one figure.

Read the companion figure carefully. On informational queries, Seer found a cited result still earns 38 per cent fewer organic clicks than a query that shows no AI Overview at all. The comparison that tells you what a citation is worth is cited against uncited, on the same kind of query. Search Console impressions with no clicks sets out what a falling rate does and does not prove.

It is also why an unlinked brand mention is worth more in AI search than it was in classic SEO. The assistant doesn’t need a link to name you.

Why can’t you set an alert for AI answers?

You can’t set an alert on an AI answer because the answer isn’t a document. Google Alerts, Mention and Brandwatch all watch a corpus of published pages: a page exists at a URL, a crawler finds it, a match fires. An assistant’s answer has no URL, is generated at the moment it is asked, and is never published anywhere a crawler can reach.

Three consequences follow, and each breaks a habit carried over from classic brand monitoring:

• There is no backfill. A page published last March can be found today. An answer given last March was never stored by anyone and cannot be recovered. Monitoring starts the day you start asking, which is the argument for starting before you need the data.
• Coverage is a choice, not a given. A web monitor sees whatever it crawls. An AI monitor sees only the questions it thought to ask, so your prompt set *is* your coverage, and a question nobody put to the assistant has no answer at all.
• The same question doesn’t give the same answer. Asking twice is two samples, not one confirmed reading.

That third point is not a rounding error. Ahrefs tracked more than 43,000 keywords carrying at least sixteen recorded AI Overviews each. It found an AI Overview has a 70 per cent chance of changing between observations, that 45.5 per cent of its cited sources are entirely new when it does, and that the average one is rewritten every 2.15 days.

Assistants behave the same way. Vismore’s 750-response audit across five engines in March 2026 found the same prompt asked three times returned a meaningfully different brand list in 38 per cent of runs. SparkToro and Gumshoe put the stricter version at under a 1 in 100 chance that two runs of one prompt return the identical brand list.

So the question isn’t whether to sample repeatedly. It’s how many samples you need, and that has an arithmetic answer rather than an opinion.

How many checks do you need before the number means anything?

More than almost anyone recommends. Published advice on this ranges from quarterly to daily and is, as far as we can find, asserted every single time rather than derived. It is derivable, and the answer is uncomfortable.

Start with the base rate, because it is the input everything else needs and almost nobody publishes it. Measured across prompt runs in RankX AI production on 27 August 2026, 87.8 per cent contained no answer mentioning the brand at all. Not a failed check. A real answer, read, with the brand absent. A typical mention rate in that data sits near 12 per cent.

A mention rate is a proportion, so its margin of error is the standard one: plus or minus 1.96 times the square root of p(1-p)/n, where p is the mention rate and n is the number of checks. At a 12.2 per cent mention rate that gives:

One check is one prompt put to one assistant once, so the arithmetic is prompts multiplied by assistants multiplied by runs. The widely repeated advice of thirty prompts, checked monthly, on a handful of assistants lands somewhere near 100 to 150 checks a month. Read the table: that carries roughly plus or minus 6 to 9 points of noise, and needs a swing near 9 points before a month-on-month move is distinguishable from nothing happening.

Here is why that matters more than it sounds. At the sample size the standard advice produces, a month-on-month move of 8 or 9 points is inside the noise band, so a change in the schedule or the prompt set can pass for a real competitive shift. Most reporting does not try to tell the two apart.

Two honest caveats, because a table like this gets quoted. The maths assumes checks are independent, and they are not quite: the same prompt repeated correlates with itself, so real intervals are a little wider than shown. And a mention rate far from 12 per cent shifts the numbers, most at 50 per cent and least near the extremes. Treat the table as a floor on how much data you need, not a ceiling.

The practical read: 40 prompts across 5 assistants, run weekly, is about 200 checks a week and is roughly where week-on-week reporting starts being defensible. Pool four weeks and you are at 800 checks, where a 3-point move is real. Below about 100 checks in a window, report the direction and the count, and don’t quote a percentage to one decimal place.

How do you tell “not mentioned” from “we couldn’t check”?

You store them as different values. This is the single most important design decision in any brand-mention tracker, and collapsing the two is how a provider outage renders as your brand disappearing from AI search.

Four states are needed, not two:

The third state is not a rare edge case. Assistants rate-limit, time out, refuse, and occasionally return something no parser can read, so any tracker running at volume records a share of checks that produced no verdict.

The fix lives in the arithmetic rather than the chart: a mention rate must divide by the checks that produced a verdict, not by the checks that were attempted. If only a third of the checks on an assistant carried a verdict, dividing by every attempted check would report a mention rate around a third of its true value and present a guess as a measurement. Where nothing carries a verdict, the honest output is no number at all, not a zero.

So when you evaluate a tool, ask this first: show me a day when a provider was down, and show me what the dashboard said that day. If the chart dipped, the tool is measuring its own reliability and labelling it your visibility.

How do you stop a tracker counting mentions that aren’t mentions?

You bound what the tracker is allowed to record, in code, rather than trusting a language model’s judgement about what it just read. The failure mode isn’t the model missing a mention. It’s a model, or a naive string match, confidently recording mentions that never happened.

Two shapes cover most of it, and both are false positives generated by the question itself:

• A competitor whose name is a place, such as Leeds, on a project whose prompts read “best web design agencies in Leeds”. A naive match fires on nearly every answer, because the answers contain the word the question used.
• A competitor whose name is a generic phrase, such as Automation Agency, on a project whose prompts read “which AI automation agency should I hire”. A naive match catches ordinary prose like “if you’re hiring an AI automation agency in the UK”, which names no company at all.

Neither is fixable with a stoplist, because the offending words are perfectly good brand names on a different project. “Leeds” is distinctive for a brand that isn’t in Leeds. The rule that does work is contextual: a term that is ambient to the check, meaning it appears in the prompt itself or is the brand’s own city or market, carries no signal when it turns up in the answer.

There is a deliberate trade-off in that rule and it is worth stating. On a comparison prompt such as “how does X compare to Acme?”, Acme is ambient, so a mention of Acme in the answer does not count. That loses a real mention. It is still right: a model naming a brand it was explicitly told to discuss is not evidence of organic visibility, and counting it inflates exactly the prompts a vendor would most like to look good on.

Can you track how an assistant talks about your brand?

Yes, and the honest version is narrower than most tools imply. Sentiment in AI answers is worth tracking, but only when it is anchored to text that is genuinely about your brand, and only when “we can’t tell” is an available answer.

The naive approach sends the whole answer to a model and asks for a label. It produces a number for every check and it is close to meaningless, because an answer that praises three competitors and lists your brand in a table is not a positive mention of your brand.

RankX AI resolves brand sentiment from verbatim spans, and a proposed span clears six deterministic gates before it counts. The model proposes a label; the gates decide whether it stands:

• Verbatim. The span appears word for word in the stored answer.
• Anchored. The span is tied to the brand rather than floating in the answer.
• Subject. The brand is what the span is about, so a sentence praising a rival is discarded.
• Not a listing. A brand name in a table cell with punctuation round it is not an opinion.
• Length. The span carries enough content to be informative.
• Confidence. The proposal clears a floor, below which the model is guessing.

Two design choices follow, and both are worth copying whatever tool you use. There is no neutral bucket, because a large confident “62 per cent neutral” slice teaches nobody anything; the fourth outcome is undetermined, and it is a real stored answer rather than a failure. And there is no coverage floor, because a floor is an instruction to guess. AI brand sentiment covers what the measurement can and can’t support.

One further test applies to any tool: ask what its sentiment figure is computed from, and what it shows when it can’t tell. A field that nothing writes looks exactly like a working one until somebody checks, and a confident “0% positive” on a screen proves nothing about whether anything was measured.

Which AI assistants can you track, and what does each expose?

Track the assistants your buyers actually use, and expect them to disagree. The important caveat first: the assistants are not reached the same way, and citation coverage differs with the method, so no single figure describes all of them.

RankX AI tracks brand mentions across six AI assistants: ChatGPT, Gemini, Claude, Perplexity, Grok and Microsoft Copilot, on the assistants you choose for each prompt.

What differs between them, and what to plan around:

• Overlap is low, and it is the reason to pick rather than to cover everything. Across 100,000 identical prompts put to both, only 11 per cent of the domains cited by ChatGPT were also cited by Perplexity. Being named by one assistant is weak evidence about the others.
• Citation coverage varies widely. Some assistants return structured sources on almost every answer, some rarely, some never. A citation-based metric will look strong on one and empty on another for reasons that have nothing to do with your visibility.
• Market coverage is not universal. Not every assistant serves every market, and an unserved market should be recorded as unsupported rather than quietly answered from somewhere else.

Google AI Overviews is deliberately not in that list. An AI Overview is triggered by a search rather than prompted like an assistant, so RankX AI tracks it through the rank-tracking pipeline against your tracked keywords, and the free AI Overview Checker shows whether a keyword triggers one and who is cited inside it. Treating a search feature and an assistant as one surface produces a number nobody can interpret.

Five questions to ask any AI brand-monitoring tool

Every vendor in this category will show you a share-of-voice chart. These five questions separate the ones measuring your brand from the ones measuring their own pipeline. We would expect a good answer to all five, including from us.

1. What does the chart do on a day a provider is down? If it dips, failed checks are being counted as absences. Ask to see a real outage day.
2. What is the denominator? A mention rate must divide by checks that produced a verdict. Ask what happens when none did: the right answer is no number, not zero.
3. Can a brand be recorded as mentioned when its name is not in the answer text? If yes, a model’s guess is being stored as a fact. Ask how fabrications are bounded.
4. Is a competitor credited when the prompt named that competitor? If yes, comparison prompts are inflating everyone, including you.
5. How many checks sit behind this number? Cross-check it against the table above. Under about 100 in the window, a percentage to one decimal place is decoration.

A sixth, if the tool reports sentiment: ask what it is computed from and what it displays when the evidence does not support a verdict.

To see how the tools on the market answer the practical half of these questions, which assistants each entry plan covers, how many prompts and how often, our roundup of AI visibility tools compares ten of them from their own pricing pages.

What do you do when the mention is wrong?

Treat a wrong mention as a source problem rather than an AI problem. An assistant saying something false about your brand almost always read it somewhere, and the record of which sources an answer cited is what turns a complaint into a task.

The sequence that works: find the answers carrying the error, read the sources those answers cited, correct the claim at source where you can, and publish a clearer statement of the fact on a page of your own that is easy to extract. Then keep checking, because a correction only surfaces once the assistant next retrieves that source. Given the volatility figures above, that is days rather than minutes, and it is not instant even then.

This is reputation work rather than measurement work, and online reputation management covers the full sequence, including what to do when the source is one you don’t control.

How RankX AI records a brand mention

RankX AI asks each assistant the question and records the answer it gives. One check is one prompt, put to one assistant, once. Scheduled checks run at 1, 3, 7, 14 or 30 day intervals, set per prompt rather than per website, so a handful of high-value questions can run daily while a long tail runs monthly. Daily is available on every paid plan.

From each stored answer, RankX AI records whether the brand was mentioned, where it sat among the brands named, which sources the answer cited, which competitors appeared beside it, and how the answer talked about the brand. The stored answer sits behind every one of those numbers, so any figure can be checked against the text it came from.

Three properties decide whether a number is trustworthy, rather than whether a dashboard looks full:

• A brand whose name does not appear in the answer text cannot be recorded as mentioned. That is structural in the code, not a filter someone remembers to switch on.
• “We did not look” and “we looked and you were not there” are different values everywhere in the product, and they are drawn differently.
• Cadence and assistant targeting are set per prompt, so the set behind any two periods can differ, and a comparison states the set it is actually comparable across.

AI Visibility carries the assistant side of this, and AI share of voice covers how individual mentions aggregate into a number you can report. If you are starting from nothing, start with the prompts rather than the tooling. A small set of questions your buyers genuinely ask, checked consistently, beats a large set checked once.