How we measure
AI visibility is easy to make sound impressive: a percentage, a ranking, a screenshot of an answer. None of those means much without a baseline, a defined question, a consistent method and a connection to the business.
We measure the work in layers: Visibility → Evidence → Behavior → Business. That keeps three things apart: what changed in an AI answer, what changed in the information underneath it, and what changed for the company.
Each report shows what moved, what did not, what we believe caused it and what we would investigate next.
We build a representative set of questions around the decisions your buyers make, not just searches for your brand name.
We track how your business and competitors appear across those questions and how the answers change over time.
A single answer is an observation. A repeated pattern is a signal.
Visibility tells us what happened. Evidence helps us understand why it may be happening.
For important answers, we trace the information underneath them. We look at the claims being made, the sources associated with those claims, the entities involved and the consistency of that information across the wider web.
Without this layer, a visibility change is hard to act on: you can see that something moved, but not what to do about it. Accuracy, consistency and coverage are measured in their own right, below.
A business can be highly visible and still be badly represented.
So we measure whether the facts that matter most are right.
Appearing more often is only half the job. The other half is being described correctly when you do.
An AI mention is not a business outcome. Wherever the data allows, we connect AI visibility to what people actually did.
We distinguish what we can directly attribute from what we can only reasonably observe.
It needs to know whether the work is paying off. Every engagement starts by agreeing what the business is trying to improve.
AI visibility is then treated as one layer of the measurement system, not the final objective.
The question we answer is not whether a number on a dashboard went up. It is:
Did the work produce a meaningful change in the outcomes we agreed to improve?
Models are updated, answers shift from one day to the next, sources come and go, and attribution is never complete. So we are careful about what the data can actually prove.
A report should tell you what we know and, just as plainly, what we don’t know yet.
When we make a meaningful change, we want to know why we made it and what we expect to learn. A typical cycle looks like this.
Something in the information environment stands out.
We propose a reason it may be happening.
We change the relevant part of the system.
We return to the relevant questions and measurements.
We determine what changed and how confident we should be in the explanation.
We either build on the finding, revise the hypothesis or move somewhere else.
This prevents the program from becoming a collection of disconnected deliverables.
What is being said? Mentions, recommendations, descriptions, citations and competitive presence.
What supports it? Claims, sources, entities, corroboration, conflicts and information coverage.
What did people do? AI referrals, engagement, inquiries, applications, bookings and conversions.
Did it matter? Pipeline, customers, revenue, acquisition cost and the business metric that matters to you.
The layers should connect, but they should not be confused.
A visibility increase is not automatically a revenue increase. A citation is not automatically a lead. A lead is not automatically a customer.
We measure each step on its own terms.
We don’t use the same dashboard for every client. What we measure follows the problem.
Illustrative scenario, not a client result
Trace which comparison pages, reviews and analyst summaries the answers lean on, then earn a credible place in those sources instead of publishing more blog posts.
What we would measure
Illustrative scenario, not a client result
Build an answer-first content model with a review workflow compliance can live with, and roll structured data out at template level.
What we would measure
Illustrative scenario, not a client result
Correct the record at the source: clear, current brand facts on the site, and a disclosed expert presence in the communities models read.
What we would measure
Illustrative scenario, not a client result
Fix call and form tracking first, so every lead has a source. Then correct the Google Business Profile and location-page facts, build them around the reasons customers give in reviews, and work toward being the business local AI answers name for the services that turn into booked jobs.
What we would measure
The cadence depends on the engagement. The questions don’t.
The objective is not a prettier dashboard. It is a clearer decision.
And no client result is published until the client has approved it. Until then, every scenario on this site is labeled illustrative.
AI visibility feels hard to measure because every answer is generated on the spot and the systems behind it keep changing. That doesn’t make measurement impossible. It makes discipline essential.
Then decide what to do next.
Free strategy call
On a free 30-minute call we take a first look at how you show up in search and AI answers and what your site gives them to cite. Then we tell you plainly whether a full audit is worth it.