LiftRank
Back to blog
MeasurementTutorial

AI Share of Voice: How to Compute It and Why It Beats Other Metrics

Share of voice is the single AI search metric that contextualizes your performance against the market. Here's the formula, the gotchas, and why it beats raw mention rate.

By Julian Hernandez ยท


The short answer

AI share of voice (SOV) is your brand's mention rate divided by the total mention rate of you plus your 3โ€“5 closest competitors on the same prompt set, measured per AI engine. It's the only AI search metric that contextualizes your performance against the actual market, which is why it's the metric that wins budget conversations and exposes the most important competitive blind spots. The exact formula, computed per engine: your mentions รท (your mentions + competitor mentions) ร— 100. A 30% SOV is good or terrible depending on how many competitors you're up against and what your trajectory is. This post is the practical guide to computing it, weighting it, and acting on it.


What's the exact formula for AI share of voice?

The formula is simple; the application is where teams get it wrong.

SOV per engine = (your brand mentions across the prompt set) รท (total mentions of you + your N competitors across the same prompt set) ร— 100

The inputs:

  • Your brand mentions: count of monitored prompts in which your brand appears in the AI engine's answer.
  • Competitor mentions: count of monitored prompts in which each tracked competitor appears, summed across all tracked competitors.
  • Same prompt set: critically, your brand and your competitors are measured on the identical set of prompts. Different prompt sets produce non-comparable SOV numbers.
  • Per engine: computed separately for ChatGPT, Perplexity, Gemini, Google AI Overviews, etc. The aggregated cross-engine SOV is useful as a headline number but the engine-level data drives the actions.

Worked example: you monitor 30 prompts across 4 competitors (so 5 brands total) on Perplexity. Across the 30 prompts, you're mentioned in 12. Competitor A in 15, Competitor B in 18, Competitor C in 8, Competitor D in 7. Total mentions across the 5 brands = 60. Your SOV on Perplexity = 12 รท 60 = 20%.

That 20% is the comparable number. It tells you that of the AI engine attention going to the 5 brands in your competitive set on these 30 prompts, you're capturing 1 in 5. The other 4 in 5 go to the four competitors.


How is it different from share of voice in traditional media?

Traditional SOV measures paid impressions or earned media coverage relative to competitors. AI SOV measures how often your brand appears in AI engine answers relative to competitors. The conceptual analogy is clean; the practical inputs are completely different.

Three differences worth understanding.

Difference one: the denominator is engine-mediated, not media-mediated. Traditional SOV's denominator is the universe of advertising or earned-media impressions in your category. AI SOV's denominator is the universe of AI engine answers your prompt set produces. The AI engine is making the inclusion decision; you're not buying the slots.

Difference two: AI SOV is more sensitive to short-term signal changes. A traditional SOV calculation typically reflects 90+ days of media activity. AI SOV can shift week-over-week because AI engines update their citation behavior in response to engine releases, training-data refreshes, and third-party-source changes. The cadence is faster.

Difference three: AI SOV maps to consideration earlier in the funnel. Traditional SOV correlates with eventual market share over multi-year time horizons. AI SOV correlates with research-stage consideration in the current quarter. The lag from SOV to revenue is shorter in the AI version because AI engines mediate consideration at the moment of intent.

The historical pattern from traditional media โ€” share of voice eventually leads share of market โ€” appears to be holding in early AI-search data. Brands gaining AI SOV today appear to be capturing more research-stage consideration that converts in the following quarters.


Which competitors should you include in the calculation?

This is where most SOV calculations go wrong.

The right competitor set: 3โ€“5 brands that a buyer would realistically consider against yours. Not the largest companies in your category. Not the brands you most envy. Not the brands with the loudest marketing. The brands a real buyer would put on a shortlist alongside you.

For a B2B SaaS team selling project management software for 20โ€“50 person teams, the right set is probably Asana, Notion, ClickUp, and one or two others in the same buyer-shortlist range. It's not Microsoft Project (enterprise) or Trello (too small) or Salesforce (different category).

Why this matters: SOV is meaningful only when the competitor set reflects the actual choice the buyer is making. If you include irrelevant brands, your SOV looks artificially high (because the irrelevant brands rarely get mentioned) but tells you nothing about whether you're winning the relevant comparisons.

A practical test: would the same buyer realistically read about you and Competitor X in the same AI engine answer? If yes, include them. If no, leave them out.

Common mistakes to avoid:

  • Including too many competitors (more than 5) โ€” dilutes the signal and creates noise from rarely-relevant brands
  • Including too few (1โ€“2) โ€” produces unstable SOV that swings on small mention changes
  • Including different competitors per engine โ€” breaks comparability across engines
  • Changing the competitor set frequently โ€” breaks trend comparability over time

Lock the competitor set, monitor weekly, and revisit the set quarterly.


How should you weight share of voice across engines?

SOV computed per engine isn't directly comparable across engines because each engine names brands at different base rates. A 30% SOV on Perplexity (which mentions 1โ€“3 brands per query) is structurally different from 30% SOV on Gemini (which mentions 4โ€“7 brands per query).

Two approaches to the cross-engine read.

Approach one: weighted aggregate by audience. Weight each engine's SOV by the share of your category's AI-search activity that engine serves. If 50% of your category's relevant AI search happens on ChatGPT, 25% on Gemini, 15% on Perplexity, 10% on Google AI Overviews, then aggregate SOV = (ChatGPT SOV ร— 0.50) + (Gemini SOV ร— 0.25) + (Perplexity SOV ร— 0.15) + (AI Overviews SOV ร— 0.10). The weights should be specific to your category, not the global engine market share.

Approach two: track per-engine and trend each separately. Don't aggregate; report SOV per engine and watch each one's trend. A brand winning on Gemini and losing on ChatGPT needs different action than a brand winning on both, and the aggregate number hides that distinction.

In practice, most teams use both: an aggregate number for leadership reporting, per-engine numbers for action. LiftRank ships both views; if you're rolling your own measurement, build the per-engine view first and the aggregate second.


What are the common mistakes that produce misleading numbers?

Five mistakes that produce SOV numbers that look fine but tell you nothing actionable.

Mistake one: comparing aggregate SOV to a single-engine benchmark. "Our SOV is 25% โ€” is that good?" Without knowing the engine, the prompt set, and the competitor count, the number is uninterpretable. Always compare like-to-like.

Mistake two: celebrating SOV gains driven by competitor losses. Your SOV can rise because you got better OR because a competitor's coverage dropped. The two are different outcomes. Pair SOV with absolute mention rate to know which one is moving.

Mistake three: ignoring the prompt set. SOV on a prompt set of 10 well-chosen decision-intent prompts is meaningful. SOV on a prompt set of 50 random category terms is decorative. Quality of prompts matters more than volume.

Mistake four: cross-engine averaging without weighting. Simple-averaging SOV across 4 engines treats them as equally important. They're not. A B2B brand whose buyers are 60% Microsoft 365 users should weight Copilot more heavily than a brand whose buyers are 60% Google Workspace users.

Mistake five: not tracking SOV trend over time. A single SOV snapshot tells you almost nothing actionable. The trend over 8+ weeks is what reveals whether your AI search program is working.

The five mistakes are common enough that most SOV dashboards we see in 2026 violate at least one of them.


How should share of voice drive actual decisions?

Three decisions that AI SOV should inform directly.

Decision one: where to invest content effort. If your SOV is meaningfully lower than competitors on a specific topic cluster (you're at 15% on "API integration" prompts while a competitor is at 40%), that's where your next quarter's content investment goes. SOV per topic cluster is more actionable than aggregate SOV alone.

Decision two: which third-party citation surfaces to prioritize. Pull the source-insights data for the prompts where competitors are out-citing you. Which third-party domains do AI engines cite for those competitors that they don't cite for you? Those domains are your next quarter's earned-media targets.

Decision three: when to escalate to leadership. A SOV trend that crosses certain thresholds should trigger a leadership conversation. Specifically: a 15+ percentage point loss to a competitor in a single quarter, or the entry of a new competitor into your top 5 SOV ranking. Both signal market-share shifts that warrant strategic attention.

The decisions don't get made automatically from the SOV data alone โ€” they require pairing SOV with absolute mention rate, sentiment, and source-insights. But SOV is the metric that surfaces the right questions to ask in the first place. Without it, the questions don't come up.


What to read next