Insight · 22 min
Visibility vs mention rate, recommendation rate, citation share, and why neutral citations still matter — plain English.
If you open a MentionX scan and stare at Visibility, Mention rate, Recommendation rate, and Citation share, you are not alone — they sound like the same idea (“does AI like us?”) but they measure different moments in a buyer answer.
This guide matches what the product actually computes: stored engine responses, structured extraction, and versioned formulas in code — not a model guessing a score.
Who this is for
| Audience | How to use this page |
|---|---|
| Marketing / PMM | Decode Overview after a scan; pair metrics with Intent Coverage by prompt family. |
| SEO / AEO leads | See what transfers from SEO (crawl, structure, links) vs what only shows up in answer inclusion. |
| Outbound / sales | Pull honest headlines (mention vs recommend gap) and attach evidence runs — no fabricated volumes. |
| Leadership / board | Use Visibility as the rollup; insist on Recommendation Rate + gap before green-lighting “we’re winning AI.” |
Most teams already have rank trackers, Search Console, and analytics. Those tools answer: Did our URL win a SERP slot and get a click?
MentionX answers: When a buyer asks an AI engine for advice in our category, does our brand appear in the generated answer — and in what role?
| Question | Typical SEO stack | MentionX scan dashboard |
|---|---|---|
| Did we rank? | Keyword position for a URL | Not the primary unit — brand entity in the answer |
| Did we get traffic? | Sessions / clicks | Not measured — many answers are zero-click |
| Are we “visible”? | Impressions on SERP | Mention rate + recommendation rate on buyer prompts |
| Who beats us? | Share of SERP top 10 | Share of voice + per-engine breakdown on the same prompts |
| Why does the model trust them? | Backlinks / DA (proxy) | Citation share + Citations tab (domains engines actually linked) |
| Can we prove it in a deal? | Screenshots of SERPs | Stored Answers + exports tied to metric definitions |
What SEO still does for AI visibility
What SEO metrics cannot replace
Deep comparison: AI visibility vs SEO.
Most dashboard percentages ask:
In how many engine runs did this happen?
An engine run = one buyer-style prompt on one engine (ChatGPT, Gemini, Perplexity, etc.) in that scan.
total_engine_runs ≈ prompts × engines (for the scope you are viewing)
Filter Overview by one engine and the same definitions apply — only for that engine’s runs.
Every metric links to evidence: the stored answers that produced it. Open Answers or export citations when you need to show the room why a number moved.
| Metric | One-line meaning |
|---|---|
| Visibility score | Composite AI presence: mentions + rank quality + citation share |
| Mention rate | They said our name |
| Recommendation rate | They put us on a ranked shortlist |
| First-choice rate | They put us first on that list |
| Mention → Recommend gap | Known but not chosen |
| Share of voice | Who gets talked about most (you vs tracked rivals) |
| Average position | How high on the list when ranked (1 is best) |
| Citation share | Who gets credited proof links vs tracked rivals |
Recommendation rate is the lead USP metric on the dashboard for a reason: buyers care when engines shortlist, not only when they name-drop.
These two are related but not interchangeable.
mention_rate = runs_where_your_brand_is_mentioned / total_engine_runs
Plain English: “What share of answers referenced us at all?”
Examples count: listed in a comparison, passing reference, product name, footnote — if extraction finds your entity in that run, it counts once for that run (not once per sentence).
visibility_score =
0.40 × mention_rate
+ 0.35 × normalized_position
+ 0.25 × citation_share
Displayed as 0–100 on Overview (the ring). Internally it is a 0–1 composite multiplied by 100.
Plain English: “Overall, how strong is our AI presence on this scan?”
| Signal | Weight | What it rewards |
|---|---|---|
| Mention rate | 40% | Showing up |
| Normalized position | 35% | Ranking high when lists appear |
| Citation share | 25% | Owning credited proof vs rivals |
Typical story: Mention rate 39%, visibility 52. You show up often, but rivals outrank you or take more credited citations — visibility reflects that drag.
Typical story (reverse): Mention rate moderate, visibility strong. You appear less often but win lists and earn links when you do.
Assume 100 engine runs (e.g. 25 prompts × 4 engines). Your Overview might show:
| Metric | Value | Meaning |
|---|---|---|
| Mention rate | 42% | Named in 42 runs |
| Recommendation rate | 28% | Ranked shortlist in 28 runs |
| Mention → Recommend gap | 14 pts | Named but not shortlisted in ~14 runs |
| First-choice rate | 11% | #1 in 11 runs |
| Share of voice | 31% | Your mentions vs you + tracked rivals |
| Citation share | 22% | Your credited proof vs rivals’ credited proof |
| Visibility score | 54 | Composite of mention + position + citation share |
Outbound-safe headline: “We show up in 42% of buyer-style answers, but only get recommended in 28% — a 14-point gap between awareness and shortlist.”
That sentence is defensible because each number traces to stored runs — not a LLM vibe check.
Modern buyer answers are not binary (“mentioned / not”). Engines often output ordered recommendations.
recommendation_rate = runs_where_you_have_a_list_position / total_engine_runs
A recommendation means extraction found you in a ranked shortlist (position 1, 2, 3…). A paragraph that names you without a list position counts toward mention rate, not recommendation rate.
first_choice_rate = runs_where_your_position_is_1 / total_engine_runs
At most one brand wins #1 per run.
mention_recommend_gap = max(0, mention_rate - recommendation_rate)
Plain English: “Engines know our name but don’t put us on the shortlist.”
That gap is where proof content, comparison pages, review presence, and third-party citations usually matter — positioning without evidence.
| Pattern | Mention | Recommend | Likely story | First move |
|---|---|---|---|---|
| A — Invisible | Low | Low | Category answers skip you | Category + comparison content; review presence |
| B — Famous, not chosen | High | Low | Name known; proof or fit weak | Comparison pages, case studies, citation gaps |
| C — Shortlist, not default | High | Medium | On lists, rarely #1 | Differentiation prompts; first-choice content |
| D — AI favorite | High | High | Strong shortlist position | Defend citations; monitor rivals on same prompts |
Pattern B is the most common in outbound: incumbents get named from training; challengers win recommendations with fresher proof.
Mention, recommendation, and first-choice rates split by prompt family — category discovery, use cases, buying criteria, competitive, alternatives, brand evaluation.
Use it when aggregate scores hide a weakness: strong on “vs Competitor X,” weak on organic “best tools for …” prompts.
Trend of visibility (and related history) across scans — same definitions, compared longitudinally.
Per-engine tables repeat mention rate, visibility, average position, and citation share because ChatGPT ≠ Gemini ≠ Perplexity on the same prompts.
Structure that converts without hype:
Template (fill from your dashboard):
We ran buyer-style prompts on {engines} for {category}. {Brand} appears in {mention}% of answers but is recommended in only {recommend}% — a {gap}-point gap between name recognition and shortlist. {Rival} leads on recommendation rate for the same prompt set. The underlying engine answers are stored if your team wants to see the evidence.
Do not claim query volume, “ChatGPT search share,” or scores without a scan — MentionX does not fabricate those.
| Prospect question | Answer with metrics |
|---|---|
| “Are we in ChatGPT?” | “On {n} buyer prompts we tested, mention rate {x}%, recommendation {y}% — want to see two answers?” |
| “Is this just SEO?” | “SEO wins pages; this measures inclusion in the answer and shortlist rate on the same questions buyers ask AI.” |
| “Why should I trust the number?” | “Every KPI links to stored runs; methodology is public at mentionx.ai/methodology.” |
| “What do we fix first?” | “Start with gap — usually proof (citations) and comparison content for prompts where rivals win Intent Coverage.” |
Lead with Recommendation Rate, not the ring alone:
Boardroom decks in MentionX follow the same hierarchy — recommendation up front, evidence-backed.
Then open Answers for the runs that hurt and attach them to Actions — that is the closed loop MentionX is built for.
| Day | Action |
|---|---|
| After scan completes | Screenshot 3 painful Answers; note engine + prompt family |
| PMM | Map weak Intent Coverage slices to comparison or use-case pages |
| SEO/AEO | Prioritize citation-gap domains (reviews, publishers) over random keywords |
| Outbound | Refresh one paragraph with updated mention vs recommend gap |
| Before board | Visibility trend + recommendation rate delta vs last scan |
| Metric | Formula (conceptual) | SEO cousin (imperfect) | Outbound phrase |
|---|---|---|---|
| Mention rate | Mentions ÷ engine runs | Brand SERP visibility | “They say our name in X% of AI answers” |
| Recommendation rate | Ranked shortlist ÷ runs | — (no direct SEO equivalent) | “We make the shortlist X% of the time” |
| First-choice rate | #1 ÷ runs | — | “We’re the top pick X% of the time” |
| Gap | Mention − recommend | — | “Known but not chosen — X points” |
| Share of voice | Your mentions ÷ all tracked mentions | Share of SERP mentions (manual) | “We own X% of the AI conversation vs rivals” |
| Avg position | Mean list rank | Average rank for a keyword | “When listed, we’re usually #X” |
| Citation share | Your proof credit ÷ tracked proof credit | Share of linking domains (rough) | “Engines cite us vs rivals X% of credited proof” |
| Visibility | 40/35/25 composite | — | “Overall AI presence score: X/100” |
Weights, extraction rules, and reproducibility notes live in MentionX Methodology. When we change scoring, we version it — historical scans keep the scorer version they ran under.
Category framing without the dashboard: What is AI visibility?