Counting mentions tells a client you showed up. It doesn’t tell them who’s actually winning the recommendation, or why.
The Mention Trap: Why “AI Visibility Reports” Mislead Clients
Most AI visibility reports look the same. A count of how many times the brand showed up across ChatGPT, Perplexity, and Google AI Overviews last month. A chart trending up and to the right. A client on the call nodding because the number went from 32 to 47.
None of that tells the client anything about whether the brand is winning.
Here’s what those reports leave out: a brand can appear in an AI answer as a footnote. Named once, listed third, cited as an alternative to whatever the model actually recommends. That still counts as a “mention.” It still shows up in the visibility dashboard as a win. But the client’s competitor is the one getting the “best choice for…” sentence, and the client is the “you might also consider” afterthought.
Ask ChatGPT “what’s the best project management tool for a 50-person marketing team” and watch what happens. Three or four tools get named. One gets the actual recommendation, with a clear reason. The others get mentioned in the same breath, as options, not answers. If your client is one of the others, a mention-count report will tell them they’re visible. They are. They’re also losing.
Presence vs. Narrative Share: What Actually Moves Recommendations
Presence answers one question: did the brand show up. Narrative share answers the question clients are actually paying you to answer: whose story is the model telling about this category, and is it ours.
AI search doesn’t rank brands the way a search engine ranks pages. It recommends them, based on a frame it’s learned from the sources it trusts. That frame decides who gets named first, who gets the confident recommendation, and who gets the hedge (“you could also look at X”). Two brands can have identical mention counts and completely different outcomes, because one owns the frame and the other is just present inside someone else’s.
This is the gap agencies aren’t reporting on. A client can be mentioned in every AI Overview for their category and still be losing, because the model has learned a story about the category that puts a competitor at the center of it. Fixing that isn’t an AEO tweak. It’s a narrative problem, and it needs a different kind of report to even see it.
What to Show Clients Instead: The Narrative Intelligence Report
A narrative-first report answers four questions a mention count never touches:
Whose frame is the model using when it answers questions about this category. Where is the client’s representation accurate, and where has the model invented a version of them that doesn’t match reality. Which sources are actually shaping the answer. And what specific shift, in positioning or in the sources feeding the model, would move the client from cited to recommended.
That’s a different document than a visibility dashboard. It’s not a bigger number. It’s a diagnosis, followed by a short list of what to ship.
Building the Report: 4 Proof Points That Matter
Four things belong in every report, regardless of format:
Narrative Share. Not “were we mentioned” but “whose story did the model tell.” Run the core prompts in the category and note who gets the primary recommendation versus who gets listed as an alternative.
Perception Gap. Where the model’s description of the client diverges from how the client actually wants to be seen. This is often the most useful section for a client meeting, because it surfaces things like “the model still describes us as an enterprise-only tool” three years after the company launched a self-serve tier.
Source Intelligence. Which sites, reviews, and articles the AI is actually pulling from to build its answer. A client losing the frame to a competitor almost always has a source problem upstream: outdated G2 comparisons, a Reddit thread from 2022, a competitor’s own content ranking in the sources the model trusts.
Explain-why. For every recommendation or omission, a plain-language reason. Not “we appeared 12 times” but “the model recommends Competitor A because it associates them with faster onboarding, based on three review sites it keeps citing.”
Together these four turn a report from a scoreboard into something a client can act on.
Case Study: How Brand X Moved from Mentioned to Recommended
Picture a mid-market HR software company, call it Brand X, that shows up in almost every AI answer about “best HR platforms for remote teams.” Good mention count. Bad outcome: the model consistently recommends a competitor first, and describes Brand X as “a solid option for smaller teams,” a positioning the company dropped two years ago.
A narrative audit would show the gap immediately. The perception check flags the outdated “smaller teams” framing. Source intelligence traces it to two review aggregator pages the model keeps citing, both written before Brand X’s enterprise features shipped. The fix isn’t more AI-answer monitoring. It’s getting updated proof onto the sources the model already trusts, and shipping content that repositions the frame at the source, not just on the brand’s own site.
That’s the difference between a report that says “we’re mentioned 40 times a month” and one that says “here’s why we’re the second choice, and here’s what changes that.”
Operationalizing It: Quarterly Narrative Dashboards That Stick
Monthly mention counts create a habit of reporting noise. Narrative shifts move slower and matter more, so a quarterly cadence usually fits better: track Narrative Share and Perception Gap every quarter, watch for drift as new sources get published or old ones age out, and keep a running list of what’s been shipped against what moved.
The report clients remember isn’t the one with the biggest number. It’s the one that told them why they were losing and what to do about it.
If you’re still handing clients a mention count and calling it AI visibility reporting, it’s worth seeing what a narrative-first version looks like. That’s the report Mavel is built to produce.
