Two metrics define brand visibility inside AI answers: mention share and answer share. They sound similar, get used interchangeably, and mean different things. Reading only one of them, or treating them as the same, misses half the picture — and leads to the wrong weekly move.
Liftable definition: mention share measures whether AI assistants are naming your brand at all. Answer share measures whether you are the named recommendation when AI returns one. Mention share is the consideration read; answer share is the win read. Both are diagnostic inputs into the Trends Desk's weekly read on position.
Key terms in one place
- Mention share:
- The share of tracked prompts where AI assistants (ChatGPT, Gemini, Claude, Perplexity, Grok) name your brand anywhere in the answer. Counts presence, not position.
- Answer share:
- Of the prompts where AI returns a recommendation, the share where you are the named recommendation rather than a rival. Counts winning the slot, not just appearing.
- Co-mention:
- When AI names your brand alongside one or more rivals in the same answer. Counts toward mention share but not toward answer share unless you are the lead.
- Recommendation event:
- An AI answer that picks a specific brand or set of brands as the recommendation. Not every answer is a recommendation event; some are definitional or comparative without recommending.
- Trends Desk:
- The weekly operating surface that tracks brand-configured trends, pulls evidence across the four pillars, and produces three moves to ship. Mention share and answer share are two of the diagnostic reads underneath it.
1. Mention share vs. answer share at a glance
| Dimension | Mention share | Answer share |
|---|---|---|
| What it measures | Presence: did AI name your brand anywhere in the answer | Winning: are you the named recommendation when AI gives one |
| Numerator | Prompts where your brand is mentioned at all | Prompts where your brand is the lead recommendation |
| Denominator | All tracked prompts | Prompts where any brand is recommended |
| SEO analogue | "Did we appear on the SERP at all?" | "Did we get position #1?" |
| Brand-tracking analogue | Unaided awareness | First-choice preference |
| Funnel stage | Top-of-funnel: are we in consideration? | Mid-funnel: when AI picks one, is it us? |
| Moves with | Listicle inclusions, third-party coverage, broad SEO presence | Decisive proof, comparison wins, sharp positioning for specific buyers |
2. The four quadrants — and the move each one calls for
Reading mention share and answer share together creates a 2×2 that maps your visibility position cleanly. Each quadrant tells the Trends Desk which of the three moves to recommend for the trend driving it:
| Position | What it means | The Trends Desk move |
|---|---|---|
| High mention share High answer share |
Leading the category. AI both knows you and picks you when it picks anyone. | Defend a Strength. Ship reinforcing proof that holds the position when a rival approaches. |
| High mention share Low answer share |
You're in the consideration set but losing the pick. Buyers see you alongside rivals; AI doesn't crown you. | Close a Gap. Ship decisive proof for the specific buyer or use case where the rival is winning the slot. |
| Low mention share High answer share |
When AI does name you, you win. But AI rarely names you at all. | Amplify a Signal. The model is already picking up something of yours — feed it more, in more places, where the model can find it. |
| Low mention share Low answer share |
You don't exist in AI answers for this category. | Foundation work. Earn baseline presence first — analyst coverage, third-party citations, listicle inclusion. There's no answer share to lift until the model knows you exist. |
The grid is read every week against the brand-configured trends moving your category. The quadrant tells the Trends Desk which move to recommend; the underlying trend tells it which evidence to ship against.
3. Why you need both metrics
Mention share alone is misleading because it counts every mention equally. A brand named once in a five-vendor list scores the same as a brand named as the single recommendation. That equates "in consideration" with "winning" — which is wrong, especially on engines like ChatGPT that often pick a single winner.
Answer share alone is also misleading because it ignores the prompts where you weren't mentioned at all. If AI names a rival as the answer on a prompt you weren't even in, that prompt doesn't count against your answer share — but it absolutely matters: you're missing from that buyer's consideration set entirely.
Together they tell you which problem you have. High mention share with low answer share means "we're visible but losing the pick." Low mention share with high answer share means "we win when named but we're not named often enough." Same brand, opposite playbooks, different weekly moves.
4. The two metrics behave differently across the five AI assistants
Mention share and answer share are not equally meaningful on every engine. Each major AI assistant skews the relationship between the two:
| Engine | Behavior | What this means for the metrics |
|---|---|---|
| ChatGPT | Decisive: often picks one or two clear winners | Answer share is the more meaningful read; mention share without answer share signals you're losing |
| Claude | Multi-vendor hedging: names several options per answer | Mention share is the more meaningful read; multi-vendor inclusion is the win, not solo recommendation |
| Gemini | AI Overviews often present structured lists | Both matter; mention share for "in the list," answer share for "the lead position" |
| Perplexity | Citation-first with multi-source synthesis | Mention share matters but cited-source share matters more; the citation is the visibility win |
| Grok | Real-time, X-weighted: pulls from creators, founders, and operators in the open | Mention share is the early-warning read; brands invisible on Grok are usually about to lose mention share on the others next |
Read all five together, not just one. A brand that wins answer share on ChatGPT but loses mention share on Claude has very different work to ship than a brand with the opposite pattern.
5. How these metrics fit into the Trends Desk read
Mention share and answer share are not the operating output. They are two of the diagnostic reads inside the broader Trends Desk read on position. The Trends Desk pulls evidence across four pillars and produces the weekly trend set; the two metrics tell you which kind of move each trend calls for.
| Pillar (Trends Desk) | What it reads | Which metric it most affects |
|---|---|---|
| Direct AEO Strategies | Your team's proactive AEO work (comparison pages, structured data, response artifacts) | Lifts answer share for the specific buyer the work targets |
| Primary Brand Amplification | Your brand's organic signal in the open (launches, founder posts, PR, customer wins) | Lifts mention share by broadening the surface the model reads from |
| Rival Competitors | What named rivals are publishing and earning inside the answer | Pressures answer share — every rival win is a slot lost |
| Analyst Stats and Thought Leaders | External authority voices and numbers the model treats as load-bearing | Shifts the bar for what proof your team has to publish to hold answer share |
This is why a weekly read beats a daily snapshot. Mention share and answer share rotate run to run on individual prompts. The Trends Desk reads them over the 7-day window, anchors the movement to the trend driving it, and hands your team one move per trend.
6. How to read both metrics weekly
Single readings on either metric are noisy. AI answers rotate among credible sources between runs, and sometimes name you, sometimes don't, on the same prompt. Read both metrics over time, not in snapshots:
- Define your prompt set: 20 to 40 prompts your target buyers actually ask, written in their language. Mix definitional, comparison, evaluation, and how-to queries.
- Run against all five engines: ChatGPT, Gemini, Claude, Perplexity, and Grok. The Trends Desk automates this — manually sampling 100 to 200 prompts across five engines is impractical.
- Calculate both metrics weekly: Mention share = prompts where you're named / total prompts. Answer share = prompts where you're the lead / prompts where any brand was recommended.
- Read 30-day trend lines, not 1-day snapshots: A single day is too noisy. The rolling window separates real position movement from prompt-level rotation.
- Map to the quadrant, then to the move: Plot the week's numbers on the 2×2. The quadrant calls the move; the underlying trend tells you which evidence to ship.
Common mistakes
Four patterns trip up marketers reading these metrics for the first time:
- Reporting only mention share. Looks better than answer share for most brands because the bar is lower. Mention share alone hides whether you're winning the recommendation. Always pair it with answer share.
- Averaging across all five engines. Different engines have different baselines. Claude's mention share will always be higher than ChatGPT's for the same brand because Claude names more vendors per answer. Read each engine separately.
- Reading single-day snapshots. Single readings can swing 20 to 40 percentage points run-to-run on the same prompt. Always read trend lines over 7 to 30 days, not screenshots.
- Treating the metrics as the operating output. They are diagnostic reads, not the move. The output is which of the three moves to ship this week — anchored to the trend driving the metric movement.
Bottom line
Mention share tells you whether AI knows you exist for a category. Answer share tells you whether AI picks you when it picks anyone. Reading only one of them gets you the wrong weekly move: low mention share calls for amplifying a signal the model is already picking up; high mention share with low answer share calls for closing the gap on the buyer the rival is winning; high on both calls for defending a strength before the rival approaches.
The TrendsCoded workstation reads both metrics weekly across ChatGPT, Gemini, Claude, Perplexity, and Grok, plots your 30-day trend on the four-quadrant grid, and the Trends Desk ships a weekly AEO Strategic Plan naming whether the next move is close-gap, defend-strength, or amplify-signal — anchored to the brand-configured trend driving the read. Product Position scoring reads which buyers each metric covers, so you know not just which metric is moving but which buyer is moving it.
