When the board asks about AI search, it is easy to bring a folder of screenshots and a long list of things the team has shipped. Neither necessarily answers the commercial question: are we being represented more accurately, and do we have evidence that the channel matters?
Start with one slide. Use a stable definition of visibility, a short account of factual corrections and the referral or conversion evidence you can observe. Put the supporting answers and work log in an appendix for anyone who wants to inspect them.
The aim is a discussion that leads to a decision. A report should make it easier to continue a useful effort, change direction or investigate a weak result. It should not depend on everyone in the room becoming an expert in a new dashboard.
Choose three numbers with clear definitions
Share of answer. Show how often the brand appears across a defined prompt set, using a comparable period. State whether the measure includes branded questions and whether it blends several engines. Keep the definition visible rather than assuming everyone remembers last quarter’s version.
Wrong facts found and fixed. Report the issues that could mislead a buyer: retired pricing, a missing integration or an incorrect product category. Separate a correction published on a source page from a correction observed in the answer. Both are useful milestones, but they are not the same event.
AI-referred visits or signups. Use the referral evidence your analytics can identify and explain its limits. Where you also ask customers how they found you, show that as a separate source of information. Do not quietly add the two together and risk counting the same person twice.
These measures describe different parts of the story. Visibility concerns the answers. Accuracy concerns the information in them. Referrals concern an observable action after exposure. One should not be presented as a substitute for another.
Show the trend and the denominator
An isolated strong answer is an example, not a trend. Use repeated observations and keep the underlying question set stable. If the set changes, explain the break in comparability or show a consistent subset alongside the expanded coverage.
Always include the number of prompts and the period covered. A percentage without its denominator invites more confidence than the evidence may support. Record missing runs too, rather than making an incomplete period look like a full sample.
If the blended line improves, check the engine-level view before the meeting. Be ready to explain whether the change is broad or concentrated in one source of answers. That detail can change what the team should do next.
Show the trend, not the daily number. A single day’s answers are noise.
A practical one-slide outline
Use a plain headline that states what happened. For an illustrative example: “Visibility improved across the existing question set; pricing accuracy still needs work.” That gives the room a conclusion it can examine instead of a collection of unexplained charts.
Top row: the three measures, the previous period and the current period, with short definitions.
Middle: a small trend chart and one sentence on the most important engine or category difference.
Bottom: the work shipped, the unresolved issue and the decision needed for the next period.
Footnote: prompt coverage, testing period, material changes in method and attribution limits.
The appendix can hold representative answers, source URLs, issue statuses and the detailed changelog. A director should be able to verify a claim without the main slide becoming a wall of small text.
Connect the work to a hypothesis
Describe the question each task was intended to affect. “Updated the pricing reference and corrected recurring external listings” is more informative than “published five assets.” It explains the reason for the work and where you would expect to see a response.
Then distinguish observation from attribution. If several pages and sources changed during the same month, a later visibility increase does not identify the contribution of each one. You can report a credible sequence without pretending it was a controlled experiment.
Use the same discipline when the number is flat. A factual correction may still be valuable, but it should not be used to hide a lack of progress on the agreed discovery questions.
End with a decision, not a promise
Propose the next small set of actions and explain why the evidence supports them. That might mean continuing a source category that is producing useful changes, fixing a recurring factual error or improving the referral measurement before expanding the budget.
Avoid promising next quarter’s recommendation rate. The team can commit to a method, an observable work plan and honest reporting. It cannot commit another system to a particular answer.
For the measurement definitions behind the slide, see what share of answer measures. A useful board update is concise because the underlying work is well documented, not because the uncertainty has been left out.
Jonah Lind
Head of content. Runs our answer-ready page work.
