Most AI visibility tools lead with one number: the share of answers that name your brand. If you track 25 questions on 3 engines and 30 of the 75 answers name you, your score is 40%. It's simple and comparable week to week. It's also easy to misread.
What's a good score?
It depends almost entirely on which questions you track. Branded or narrow questions produce high scores; broad category questions produce low ones. As a rough guide for a balanced set of category, use-case and alternatives questions:
- Category leaders: 60–90%
- Established challengers: 25–60%
- New or niche brands: under 25%, often concentrated in a few use-case questions
Compare yourself against your own past and your direct rivals on the same questions, never against another company's score from another tool.
Why 100% can hide a problem
A score of 100% means you were named in every answer. It doesn't mean you were recommended first. If a rival is named ahead of you in most answers, buyers read their name first and may stop there. A perfect score on easy questions can also mean your question set is too narrow. If you see 100%, look at:
- Position. Average position and how often a rival is named before you.
- Harder questions. Add “alternatives to [leader]”, comparison and use-case questions until you find where you're missing.
- Engines. A high average can hide one engine where you're absent.
Read it with three other numbers
| Number | Question it answers |
|---|---|
| Average position | When named, am I the recommendation or a footnote? |
| Share of voice | Am I gaining or losing against specific rivals? |
| Cited sources | Which pages shape these answers, and am I on them? |
Expect noise
AI answers vary from run to run. A move of a few points in one week is often noise; a move that holds for three weeks is real. Track enough questions (20+) and judge trends, not single runs.
Turn it into a to-do list
The useful output isn't the score; it's the list behind it: the questions where you're missing, who is named instead, and the pages those answers cite. That's why Seenby's dashboard opens on that list rather than on the percentage.