How to report AI visibility to clients

AI visibility is straightforward to sell and awkward to report. The work is real, the number often takes a quarter to move, and clients arrive with instincts from rank tracking where positions shift weekly. A report that ignores that gap either overpromises early or quietly stops being read.

This guide covers what to include, what to leave out, and how to show progress honestly in the months before the headline figure moves, using Visibility AI’s reporting and Performance layers.

Why the usual reporting template fails here

An SEO report leans on numbers that move continuously: positions, impressions, clicks. AI visibility does not behave that way. A brand can sit at zero for six weeks while every underlying signal improves, then appear in four answers in a fortnight once a source updates. Plotted alone, that looks like nothing happened and then luck happened.

The second problem is volatility in the wrong direction. Answers vary with phrasing and model updates, so a single-engine dip can look like a regression when nothing changed. If your report presents one number with no context, you will spend the call explaining variance instead of discussing work.

The fix is not to hide either fact. It is to build the report so the leading indicators carry the story until the headline number catches up.

Step 1: Fix the question set before the first report

Everything downstream depends on this. Agree a set of buyer questions with the client, write them down, and do not change them. That set is the measuring instrument, and swapping questions mid-engagement makes every comparison meaningless - including the favourable ones.

Twenty to forty questions covering category, comparison and problem phrasings is usually enough to be stable. Show the client the list in the first report and get their agreement on it, because “you were measuring the wrong questions” is the easiest objection in the world to raise in month three.

Step 2: Lead with one number, in context

Open with presence or share of voice against the fixed set, the change since last month, and the competitor set alongside it. One number, one comparison, one context. Measuring AI share of voice covers which of the two to lead with for a given client.

Two things to state plainly every time:

• What the number is measured against. “Named in 18% of answers across 32 tracked questions and 7 engines” is defensible. “18% AI visibility” invites the client to invent their own definition.
• What counts as a real change. Give them a sense of normal variance up front so a two-point dip does not become an emergency email.

Step 3: Report the leading indicators, not just the outcome

This is what carries the first quarter. The headline number is the last thing to move; the signals underneath it move first, and they are honest evidence that work is landing:

• Crawler access: which AI bots now reach the site that previously could not.
• Page readiness: audit scores on the pages you optimized, before and after.
• Citations and sources: new appearances in the sources engines actually cite for the client’s questions.
• Competitor movement: who is gaining, and where.

Presented as a sequence, these tell a coherent story: we made the site readable, we made the pages quotable, we earned two placements, and here is the first movement in the answers. That reads as progress. A flat headline number with nothing underneath reads as a stalled retainer.

Step 4: Attribute the change to the work

Clients pay for causation, and honest attribution is what separates a report from a dashboard. Line up what you changed against what moved: the pages you published, the listings you fixed, the sources you earned, and the questions or engines that shifted afterwards.

Be careful with the claim. Answer engines are influenced by many things at once, and a competitor’s misstep can lift you as easily as your own work can. Present it as evidence rather than proof - “these four questions began naming the client in the three weeks after the service pages were rewritten” - and you will keep the client’s trust when a month goes the other way. Visibility AI’s Optimization Impact view sets the before and after against the actions you took, which is the shape this section wants.

Step 5: End with the next three things

Close every report with a short, ranked list of what happens next and why, drawn from the gaps in the data rather than from a generic checklist. Three items, each with the reason attached: this question set is where the client loses most often, this source keeps appearing behind a competitor’s mentions, this page scores worst on the audit.

Finding your optimization opportunities covers how to rank that list by impact against effort, so the three items you commit to are the three that matter.

Make the report repeatable

The reporting job is not writing a document each month, it is running the same measurement each month and explaining what changed. Scheduled reports and white-label output mean the client sees your brand on a consistent format they learn to read, and you spend the time on the analysis rather than the assembly.

If you run AI visibility for several clients, keeping each in its own workspace with its own question set and competitor set keeps the numbers clean and the reports honest. See how we set this up for agencies, or run a free Visibility Check on a client’s site to see what the first baseline would look like before you pitch it.

Frequently asked questions

What should an AI visibility report actually contain?

Four things: the presence or share number against a fixed question set, the change since last month, which competitors are being named instead, and what you did about it. Anything beyond that is usually decoration, and decoration is what makes clients stop reading.

What do I report in month one, when the number is zero?

Report the zero, and report the diagnosis underneath it. A baseline plus a named cause plus the work queued against it is a strong first report. A zero on its own, or a zero dressed up with vanity metrics, is not.

How often should these go out?

Monthly for clients, weekly for your own team. AI answers move week to week, but a client-facing report that arrives weekly turns normal fluctuation into a conversation about noise, and trains them to read every dip as a problem.