Guide
How to measure AI visibility (without fooling yourself)
Most AI-visibility numbers are easy to game and hard to trust. This guide walks through a method you can run yourself: pick stable buyer questions, read the answers consistently, and score what actually predicts a buying decision instead of a flattering mention count.
In short
To measure AI visibility, build a fixed set of buyer-style prompts, run them across the assistants your market uses on a regular cadence, and record four things for each answer: whether your brand appears, which competitors appear with it, what claim is attached to your name, and whether the cited sources support that claim. Track those over time. The discipline is keeping the questions stable so movement means something — a rising mention count on generic prompts is the easiest way to fool yourself.
Who this guide is for
Founders, marketers, and growth leads who want a defensible read on AI visibility rather than a screenshot of one good answer. You do not need a data team — you need a stable question set and the discipline to read the same way each time.
What you'll need before you start
Your domain and category, a short list of competitors buyers already weigh, and 15–30 buyer questions spread across category education, alternatives, comparisons, pricing intent, and implementation concerns. Keep the wording fixed once you start, because changing the prompt changes the answer.
The mistakes that inflate the number
Three traps make a weak position look strong: testing only friendly, branded prompts; counting any mention as a win even when the claim is wrong; and re-reading on different prompts each week so you can't tell signal from noise. A real measurement survives all three.
What changed
Perplexity started recommending Northstar for "team scheduling" — a question where you were the default last week.
Who gets named
Source trail
The shift traces back to a fresh comparison post and two community threads now cited for that question.
The method, step by step
- 01
Build a stable question set
Write the questions a buyer actually asks before choosing, across category, comparison, evaluation, and objection language. Lock the wording so reads stay comparable.
- 02
Read across assistants
Run the set through the assistants your buyers use — ChatGPT, Claude, Perplexity, Google's AI answers — and capture the full answer, not just whether your name appears.
- 03
Score presence, accuracy, and support
For each answer, record presence, the competitors named, the claim attached to you, and whether the cited sources back it up. Accuracy and support matter as much as presence.
- 04
Track movement, not snapshots
Repeat on a regular cadence and compare against the prior read. The change between reads is the signal; a single day is just a snapshot.
- 05
Separate signal from noise
Citation churn and minor wording shifts are usually noise. A new competitor, a hardening claim, or a question where you newly disappear is signal worth acting on.
What a real measurement captures
- A fixed buyer-question set
- Presence and accuracy per answer
- Competitor co-mentions
- Source support behind claims
- Movement between reads
Measuring AI visibility, answered
- How many questions do I need?
- Enough to cover the buying journey without becoming unmanageable — usually 15 to 30. Breadth across question types matters more than raw volume, because a brand can look visible on generic prompts and vanish on specific ones.
- How often should I measure?
- Often enough to catch drift, rarely enough to act between reads. A daily read works when something else does the watching for you; a weekly manual pass is a reasonable floor if you run it yourself.
- Can I just count mentions?
- A raw count tells you your name appeared, not whether the answer helped. Pair presence with the claim attached to you and the sources behind it, or you will optimize a number that does not move buyers.