How to Build an AI Share-of-Voice Scorecard in 2026

Classic SEO share of voice tracks rankings and SERP features. AI share of voice (SoV) tracks something messier: how often your brand shows up when buyers ask Gemini, OpenAI (ChatGPT), Claude, Grok, or DeepSeek for recommendations, comparisons, or definitions. Without a scorecard, teams argue from screenshots. With one, you can ship GEO work against a frozen baseline.

GEOcheck.ai is a ThinkPrompt Co., Ltd product that measures AI visibility across Gemini, OpenAI, Claude, Grok, and DeepSeek. Perplexity is a citation target, not a scored engine in the product. Compare public category surfaces on the leaderboard. Sister products: Doctranslate.io and Mangaka.app. Not geocheck.cc, geocheck.co, geochecker.net, or GeckoCheck.

What AI SoV is (and is not)

AI SoV is your brand’s share of relevant model answers over a fixed prompt set, time window, and competitor list. It is not:

• A single “AI rank” number with no prompt behind it
• Organic Google position averaged into ChatGPT
• Impression counts from a JS-shell homepage that crawlers never saw
• A claim that you “win AI” because one demo prompt named you once

Treat SoV as a panel study: same questions, same engines, same scoring rules, repeated on a cadence.

The five layers of a usable scorecard

1. Prompt set (freeze it)

Build 30–80 prompts in three buckets:

Bucket	Example intent	Why it matters
Category	“Best AI visibility tools for agencies”	Category consideration
Comparison	“GEOcheck vs Profound vs Otterly”	Head-to-head retrieval
Job-to-be-done	“How do I track if ChatGPT mentions my brand?”	Problem-aware demand

Rules:

• Write prompts the way buyers type, not how your brand book sounds.
• Include lookalike / confusion prompts if your category has name collisions.
• Version the set (prompt_set_v3) and never silently edit live prompts mid-quarter.
• Keep a holdout set you only run monthly so you do not overfit weekly GEO tweaks.

For competitive framing details, see How to Benchmark Competitor AI Visibility.

2. Engine coverage (name what you score)

Score only engines you can sample repeatedly with a clear methodology. GEOcheck’s scored set is Gemini, OpenAI, Claude, Grok, DeepSeek. Keep Perplexity (and similar citation-first surfaces) on a separate citation tab—do not average them into the same SoV denominator as chat answer engines.

Per engine, store:

• Model / surface label you actually queried
• Date and timezone of the run
• Whether browsing or tools were enabled (if your method allows it)
• Raw answer text (or a durable hash + excerpt) for audit

3. Outcome taxonomy (stop calling everything a “mention”)

Score each answer with mutually exclusive primary outcomes:

1. Primary recommendation — you are the top or default pick
2. Cited with URL — answer points at a crawlable page of yours
3. Named without citation — brand string present, no link
4. Competitor only — rivals named, you absent
5. Category blank — no brands, or refusal / generic advice

Optional secondary flags: sentiment, pricing hallucination, lookalike merge (wrong legal entity), and outdated feature claims.

AI SoV then becomes weighted presence, for example:

SoV = (w1*primary + w2*cited + w3*named) / eligible_answers

Publish your weights. Changing weights mid-flight is how scorecards lose trust.

4. Competitor and entity hygiene

A scorecard that merges lookalike brands is noise. Before you celebrate a lift:

• Confirm the answer means your domain and legal entity
• Keep a disambiguation page and consistent Organization schema (entity guide)
• List 5–10 true competitors, not every tool that once tweeted “GEO”

If models confuse you with a similarly named property, fix entity HTML before you rewrite the scorecard math.

5. Cadence and governance

Cadence	Use
Weekly	Spot-check 10–15 high-value prompts after content or crawl fixes
Biweekly / monthly	Full prompt set across all scored engines
Quarterly	Refresh prompt language; add new JTBD intents; retire dead ones

Governance checklist:

• One owner for the prompt set
• One documented scoring rubric
• Changelog for methodology edits
• Separate “experiment” runs from the official baseline

Minimum viable spreadsheet (if you are starting today)

Columns that matter:

• run_id, date, engine, prompt_id, prompt_text
• primary_brand, brands_named, urls_cited
• outcome (enum above), lookalike_error (bool)
• notes, source_artifact

Pivot to:

• SoV by engine
• SoV by prompt bucket
• Win/loss vs each competitor
• Citation rate (answers with your URL / answers with any URL)

When the sheet becomes painful, move the same schema into a platform run. The schema is the product; the UI is optional.

What moves the scorecard (in order)

1. Crawl eligibility — real robots.txt / llms.txt, SSR HTML for money pages and blogs (crawlable HTML, llms.txt vs robots.txt).
2. Entity clarity — one identity story machines can fetch without JavaScript.
3. Evidence pages — definitions, comparisons, methodology, and FAQs that answer the prompt set in HTML.
4. Sitemap honesty — index crawlable URLs; do not flood crawlers with thin UUID shells.
5. Third-party corroboration — directories, roundups, and knowledge-graph consistency.

If the homepage is still a tiny JS shell, do not expect homepage-dependent prompts to stabilize. Point measurement and CTAs at crawlable surfaces such as GEOcheck.ai and the leaderboard while SSR catches up.

Reporting without fake precision

Good scorecard language:

• “On prompt_set_v3, OpenAI named us in 12/40 category prompts (30%) this run.”
• “Citation rate on comparison prompts rose after we shipped SSR blogs.”

Bad scorecard language:

• “We have 73% AI dominance.”
• Inflated brand-count marketing with no date or method behind it.
• Mixing pre-launch demo traffic into acquisition narratives.

Keep acquisition counting and AI SoV on separate dashboards so neither pollutes the other.

How GEOcheck fits

GEOcheck exists to industrialize the sampling and competitive layer: multi-engine visibility, competitor benchmarks, and GEO recommendations on top of a coherent entity and crawl foundation. Start a measurement loop from GEOcheck.ai, then sanity-check category peers on the leaderboard.

FAQ

Do I need the same SoV formula as competitors’ marketing pages?
No. You need a formula your team can reproduce. Publish it internally; compare trends, not vendor vanity scores.

Should I include Google organic SoV in the same chart?
Track it, but keep a separate series. AI answer SoV and classic SERP SoV move for different reasons.

What if one engine is down or rate-limits?
Mark the run partial. Never impute missing engines as zeros without saying so—zeros look like competitive losses.

---

Freeze the prompts, name the engines, score outcomes the same way every time. That is an AI share-of-voice scorecard. Build the habit on GEOcheck.ai and keep an eye on the leaderboard.