{"id":2615,"date":"2026-09-24T03:29:03","date_gmt":"2026-09-24T03:29:03","guid":{"rendered":"https:\/\/maxaeo.ai\/blog\/calculate-share-of-voice-in-llm-responses\/"},"modified":"2026-09-24T03:29:03","modified_gmt":"2026-09-24T03:29:03","slug":"calculate-share-of-voice-in-llm-responses","status":"publish","type":"post","link":"https:\/\/maxaeo.ai\/blog\/calculate-share-of-voice-in-llm-responses\/","title":{"rendered":"Calculate Share of Voice in LLM Responses: Formula, Method, and Metrics"},"content":{"rendered":"<p><em>By maxaeo.ai \uff5c Published 2026-09-24 \uff5c Updated 2026-09-24<\/em><\/p>\n<p>To <strong>calculate share of voice in LLM responses<\/strong>, divide your brand\u2019s tracked mentions by the total tracked brand mentions in the same AI answers, then multiply by 100. The result shows how much of the visible competitive conversation belongs to your brand across a defined prompt set, engine list, competitor group, and time period.<\/p>\n<h2>What is share of voice in LLM responses?<\/h2>\n<p>Share of voice, or SOV, is the percentage of brand presence your company receives compared with the total presence of tracked brands in AI-generated answers. Unlike a simple mention rate, it is a competitive metric: it tells you whether your visibility is growing relative to alternatives.<\/p>\n<p>A practical baseline formula is:<\/p>\n<pre><code class=\"language-text\">LLM SOV (%) =\nYour brand mentions \u00f7 Total tracked brand mentions \u00d7 100\n<\/code><\/pre>\n<p>For example, if your brand appears 42 times and all tracked brands appear 140 times across the same answer set:<\/p>\n<pre><code class=\"language-text\">42 \u00f7 140 \u00d7 100 = 30% SOV\n<\/code><\/pre>\n<p>Industry definitions differ on whether to count mentions, answers, citations, or weighted prominence. That is why every report should state its counting rule before showing the percentage. (<a href=\"https:\/\/blimpp.com\/ai-search-index\/ai-share-of-voice\/\" target=\"_blank\" rel=\"noopener\">blimpp.com<\/a>)<\/p>\n<figure class=\"wp-block-image size-large\" style=\"margin:1.5em 0;\"><img decoding=\"async\" src=\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/09\/backend-3544-1.jpg\" alt=\"calculate share of voice in LLM responses across competing SaaS brands\" style=\"max-width:100%;height:auto;\"><\/figure>\n<h2>What should be included in the SOV denominator?<\/h2>\n<p>The denominator is the most important part of the calculation. Include only brand observations collected from the same scope:<\/p>\n<ul>\n<li>The same prompt set<\/li>\n<li>The same AI engines<\/li>\n<li>The same competitor list<\/li>\n<li>The same market and language<\/li>\n<li>The same observation window<\/li>\n<li>The same counting method<\/li>\n<\/ul>\n<p>Suppose a SaaS company tracks 50 buyer prompts across ChatGPT, Perplexity, Gemini, and Claude. If the monitored brands produce 500 total mentions and your brand receives 75, your SOV is 15%.<\/p>\n<p>Do not mix that result with a second report that uses different prompts or adds ten more competitors. The percentage may change even when your underlying visibility does not.<\/p>\n<p>A useful reporting convention is to publish both:<\/p>\n<ol>\n<li><strong>Tracked-set SOV:<\/strong> your share among named competitors.<\/li>\n<li><strong>Open-market SOV:<\/strong> your share among every recognizable brand appearing in the answers.<\/li>\n<\/ol>\n<p>Tracked-set SOV is better for direct competitive decisions. Open-market SOV is better for discovering unexpected alternatives that AI engines introduce into the category.<\/p>\n<h2>How to calculate LLM share of voice step by step<\/h2>\n<h3>1. Define the commercial prompt universe<\/h3>\n<p>Build prompts around real buyer intent rather than only product names. Include categories such as:<\/p>\n<ul>\n<li>\u201cBest project management tools for remote teams\u201d<\/li>\n<li>\u201cAlternatives to [competitor]\u201d<\/li>\n<li>\u201cAffordable CRM for a growing SaaS company\u201d<\/li>\n<li>\u201cWhich analytics platform is easiest to implement?\u201d<\/li>\n<li>\u201cTools with strong integrations for [use case]\u201d<\/li>\n<\/ul>\n<p>A strong prompt set normally combines category discovery, comparison, alternatives, use-case, and evaluation questions. The goal is to measure the market conversations where a buyer could realistically encounter your brand.<\/p>\n<h3>2. Select engines and repeat the same prompts<\/h3>\n<p>Run the same prompt set on each selected engine. Report engines separately before combining them because ChatGPT, Perplexity, Gemini, Claude, and other systems can use different retrieval sources, answer structures, and recommendation patterns.<\/p>\n<p>For every response, store:<\/p>\n<ul>\n<li>Prompt text<\/li>\n<li>Engine name<\/li>\n<li>Date and time<\/li>\n<li>Full answer<\/li>\n<li>Mentioned brands<\/li>\n<li>Citation URLs or domains<\/li>\n<li>Mention position<\/li>\n<li>Sentiment or recommendation context<\/li>\n<\/ul>\n<p>Keeping the raw answer is essential. It allows a team to verify whether a brand was merely listed, actively recommended, criticized, or cited as evidence.<\/p>\n<h3>3. Choose a counting unit<\/h3>\n<p>There are three common counting units.<\/p>\n<div style=\"overflow-x:auto;\">\n<table style=\"width:100%;border-collapse:collapse;margin:1.5em 0;font-size:0.95em;\">\n<thead>\n<tr>\n<th style=\"border:1px solid #e3e6ea;padding:8px 12px;background:#f6f8fa;text-align:left;font-weight:600;\">Counting unit<\/th>\n<th style=\"border:1px solid #e3e6ea;padding:8px 12px;background:#f6f8fa;text-align:left;font-weight:600;\">What it measures<\/th>\n<th style=\"border:1px solid #e3e6ea;padding:8px 12px;background:#f6f8fa;text-align:left;font-weight:600;\">Best use<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Mention-level<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Every explicit brand naming<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Detailed competitive presence<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Answer-level<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Whether a brand appears at least once in an answer<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Simple visibility rate<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Citation-level<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Every source that supports or references a brand<\/td>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Authority and source coverage<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Mention-level SOV is usually the clearest starting point. If one answer names a brand three times, it contributes three mentions. Answer-level measurement prevents verbose answers from dominating the result, but it may understate prominence.<\/p>\n<p>The important rule is consistency. Never compare a mention-level score with an answer-level score and call the difference a performance change.<\/p>\n<h3>4. Apply the formula<\/h3>\n<p>Assume a 30-day sample contains:<\/p>\n<ul>\n<li>100 prompts<\/li>\n<li>4 AI engines<\/li>\n<li>400 total answers<\/li>\n<li>620 total brand mentions<\/li>\n<li>93 mentions for your brand<\/li>\n<\/ul>\n<p>Your raw SOV is:<\/p>\n<pre><code class=\"language-text\">93 \u00f7 620 \u00d7 100 = 15%\n<\/code><\/pre>\n<p>If the competitor totals are:<\/p>\n<div style=\"overflow-x:auto;\">\n<table style=\"width:100%;border-collapse:collapse;margin:1.5em 0;font-size:0.95em;\">\n<thead>\n<tr>\n<th style=\"border:1px solid #e3e6ea;padding:8px 12px;background:#f6f8fa;text-align:left;font-weight:600;\">Brand<\/th>\n<th style=\"text-align:right\">Mentions<\/th>\n<th style=\"text-align:right\">SOV<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Your brand<\/td>\n<td style=\"text-align:right\">93<\/td>\n<td style=\"text-align:right\">15.0%<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Competitor A<\/td>\n<td style=\"text-align:right\">155<\/td>\n<td style=\"text-align:right\">25.0%<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Competitor B<\/td>\n<td style=\"text-align:right\">124<\/td>\n<td style=\"text-align:right\">20.0%<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Competitor C<\/td>\n<td style=\"text-align:right\">93<\/td>\n<td style=\"text-align:right\">15.0%<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #e3e6ea;padding:8px 12px;vertical-align:top;\">Other tracked brands<\/td>\n<td style=\"text-align:right\">155<\/td>\n<td style=\"text-align:right\">25.0%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>This table reveals more than your score alone. It shows whether the problem is low overall visibility, one dominant competitor, or a fragmented category.<\/p>\n<h2>Should citations and recommendation position be weighted?<\/h2>\n<p>A raw SOV score should remain unweighted so that it is easy to reproduce. However, a second prominence score can explain the quality of your visibility.<\/p>\n<p>One practical framework is the <strong>Visibility\u2013Prominence\u2013Evidence model<\/strong>:<\/p>\n<ul>\n<li><strong>Visibility:<\/strong> Was the brand mentioned?<\/li>\n<li><strong>Prominence:<\/strong> Where did it appear and was it recommended?<\/li>\n<li><strong>Evidence:<\/strong> Was it supported by a citation or trusted source?<\/li>\n<\/ul>\n<p>For example, assign internal diagnostic values:<\/p>\n<pre><code class=\"language-text\">Visibility = 1 if mentioned\nProminence = 1 to 3 based on position or recommendation strength\nEvidence = 1 if supported by a relevant citation\n<\/code><\/pre>\n<p>Do not silently merge these values into official SOV. Instead, show:<\/p>\n<pre><code class=\"language-text\">Raw SOV: 15%\nRecommended-answer rate: 8%\nCitation-supported mention rate: 11%\nAverage recommendation position: 2.4\n<\/code><\/pre>\n<p>This separation is an important measurement improvement. A brand can have high mention SOV but weak buyer influence if it appears late, without evidence, or only in negative comparisons.<\/p>\n<p>For broader measurement guidance, an <a href=\"https:\/\/maxaeo.ai\/blog\/ai-search-visibility-dashboard\/\">AI search visibility dashboard framework<\/a> can help organize these metrics into recurring reports.<\/p>\n<h2>How large should the sample be?<\/h2>\n<p>There is no universal sample size that guarantees a reliable SOV benchmark. A small sample can identify obvious gaps, but it is sensitive to prompt selection and answer variation.<\/p>\n<p>For a practical SaaS baseline:<\/p>\n<ul>\n<li>Use at least 25\u201350 commercially relevant prompts.<\/li>\n<li>Run them across at least 3 engines when possible.<\/li>\n<li>Compare the same prompts for at least four weekly cycles.<\/li>\n<li>Keep a separate view for each engine.<\/li>\n<li>Label results as directional until the trend is stable.<\/li>\n<\/ul>\n<p>The main source of error is usually not the arithmetic. It is sampling bias. If all prompts are written around your own positioning, your SOV may look stronger than it is in neutral buyer language.<\/p>\n<h2>How can teams improve their SOV after measuring it?<\/h2>\n<p>First, identify the prompts where competitors appear and your brand does not. Then classify the gap:<\/p>\n<ol>\n<li><strong>Entity gap:<\/strong> The AI system does not recognize your product category or use case.<\/li>\n<li><strong>Proof gap:<\/strong> Your brand is mentioned but lacks supporting evidence.<\/li>\n<li><strong>Source gap:<\/strong> Competitors are backed by review sites, comparisons, documentation, or community discussions that the model retrieves.<\/li>\n<li><strong>Positioning gap:<\/strong> Your product is described inaccurately or associated with the wrong buyer need.<\/li>\n<li><strong>Recommendation gap:<\/strong> You appear in lists but are not selected as a strong option.<\/li>\n<\/ol>\n<p>Track these gaps alongside citations and sentiment. MaxAEO supports daily monitoring across eight AI engines, including ChatGPT, Perplexity, Gemini, Claude, Copilot, Grok, Google AI Mode, and Google AI Overviews. It also compares brand and competitor mention rates, citation sources, sentiment, and recommendation position.<\/p>\n<p>You can begin with a <a href=\"https:\/\/maxaeo.ai\/\">free AI visibility diagnosis<\/a> or review an <a href=\"https:\/\/maxaeo.ai\/blog\/ai-visibility-optimization-for-citations\/\">AI citation optimization framework<\/a> to connect SOV findings with specific content actions.<\/p>\n<h2>What is the difference between mention rate and SOV?<\/h2>\n<p>Mention rate measures how often your brand appears across answers. SOV measures how much of the competitive mention volume belongs to your brand.<\/p>\n<p>For example:<\/p>\n<pre><code class=\"language-text\">Mention rate = 80 appearances \u00f7 400 answers = 20%\nSOV = 80 mentions \u00f7 500 total mentions = 16%\n<\/code><\/pre>\n<p>The brand appears in one-fifth of answers, but owns only 16% of all brand mentions because several answers contain multiple competing brands.<\/p>\n<p>Use mention rate to measure reach. Use SOV to measure competitive share. Use citation rate, recommendation rate, sentiment, and position to understand the quality of that share.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Is LLM share of voice the same as SEO share of voice?<\/h3>\n<p>No. SEO SOV is generally based on rankings, search visibility, impressions, or estimated clicks. LLM SOV measures brand presence inside generated answers. A company can perform well in traditional search and still receive little AI recommendation visibility.<\/p>\n<h3>Should repeated mentions in one answer count multiple times?<\/h3>\n<p>They can, but the rule must be declared. Mention-level counting captures textual prominence; answer-level counting gives every response equal weight. For executive reporting, publish both when repeated mentions are common.<\/p>\n<h3>Should citations count as extra mentions?<\/h3>\n<p>Not in raw SOV. A citation is evidence of source support, not necessarily another brand mention. Keep citation rate as a separate metric so the score remains interpretable.<\/p>\n<h3>What is a good LLM SOV score?<\/h3>\n<p>There is no universal good score. Compare your result with the same competitors, prompts, engines, and time period. A lower score in a highly fragmented category may be strategically healthier than a higher score based on a narrow prompt set.<\/p>\n<h3>How often should SOV be monitored?<\/h3>\n<p>Daily collection is useful because AI answers can change, but weekly or monthly analysis is usually easier to interpret. Keep the raw daily data and use fixed reporting windows for trend comparisons.<\/p>\n<figure class=\"wp-block-image size-large\" style=\"margin:1.5em 0;\"><img decoding=\"async\" src=\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/09\/backend-3544-2.jpg\" alt=\"LLM share of voice dashboard showing mentions, citations, competitors, and recommendation position\" style=\"max-width:100%;height:auto;\"><\/figure>\n<p><script type=\"application\/ld+json\">\n{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"author\":{\"@type\":\"Organization\",\"name\":\"maxaeo.ai\"},\"dateModified\":\"2026-09-24\",\"datePublished\":\"2026-09-24\",\"description\":\"Learn how to calculate share of voice in LLM responses using a reproducible prompt, engine, and competitor framework. Measure mentions, citations, and prominence with confidence.\",\"headline\":\"Calculate Share of Voice in LLM Responses: Formula, Method, and Metrics\",\"image\":\"https:\/\/maxaeo.ai\/blog\/wp-content\/uploads\/2026\/09\/art-6962-cover.jpg\",\"publisher\":{\"@type\":\"Organization\",\"name\":\"maxaeo.ai\"}}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to calculate share of voice in LLM responses using a reproducible prompt, engine, and competitor framework. Measure mentions, citations, and prominence with confidence.<\/p>\n","protected":false},"author":1,"featured_media":2614,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2615","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/2615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/comments?post=2615"}],"version-history":[{"count":0,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/posts\/2615\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media\/2614"}],"wp:attachment":[{"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/media?parent=2615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/categories?post=2615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/maxaeo.ai\/blog\/wp-json\/wp\/v2\/tags?post=2615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}