How agencies report AI visibility to clients
Build an agency AI visibility report with saved answers, clear denominators, reporting dates, completed changes, caveats and a practical next-action template.
What should an agency AI visibility report include?
Show the client what was sampled, what changed and which action follows. Include exact questions, dates, collection methods, saved answers and the numerator and denominator behind each metric. Connect findings to completed page edits and the next work list, with caveats stated clearly in one place.
Lead with the decision the client needs to make
An AI visibility report should help a client approve useful work. Begin with the most consequential finding, the evidence behind it and your recommended response. “The saved answers describe our deposit policy incorrectly; approve a correction to the product guide” gives the client a concrete decision.
Write the opening after reviewing the underlying answers. Choose one main finding and, at most, two supporting observations. State whether the client needs to approve a change, supply missing product facts or simply review completed work. Keep the detailed evidence available immediately below the summary.
Agree on the reporting question at the start of the engagement. It might concern category discovery, competitor comparisons or accurate explanations of a feature. Put the client's business, market and language in the report header. Each reported number should help answer that agreed question.
Put the scope and dates beside the results
State the reporting period, comparison period and latest collection date. Identify the interface, model when exposed, search mode and location settings. Give the question set a version and distinguish branded questions from questions that ask for category recommendations without naming the client.
Show scheduled observations, completed eligible answers and failures together. Break failures into useful categories such as timeout, refusal or incomplete response. Record retries and your replacement rule. This lets the reviewer reconcile the collection log with the sample used in the report.
If you include search data, show its reporting dates separately. Google defines clicks, impressions and position for its search performance reports. Preserve the originating report and filters when including those figures beside your answer observations. Google's search performance definitions.
Show counts before percentages
Define mention rate as completed eligible answers naming the client divided by all completed eligible answers. Count a brand once per answer. If you report position, state whether it is recommendation order or first appearance. Show the number of answers eligible for that calculation.
For share of voice, list the comparison brands and counting rule. For source presence, say whether you counted unique pages, domains or answers containing a link. Use the same definitions in the headline, table and supporting evidence. Our AI visibility measurement guide provides a worked calculation.
Here is a hypothetical reporting table for example.com. Both periods use the same ten questions, each collected four times through one method. All observations complete. The numbers illustrate presentation and are not results from a customer account.
| Item | August 1–28, 2026 | September 1–28, 2026 | Report wording |
|---|---|---|---|
| Completed observations | 40 of 40 scheduled | 40 of 40 scheduled | Same planned coverage |
| Answers naming example.com | 12 of 40 | 18 of 40 | Six additional answers named the brand |
| Mention rate | 30% | 45% | Increase of 15 percentage points |
| Question-set version | Version 1 | Version 1 | Same ten questions and collection method |
Keep the underlying rows beside the summary. The 15-point change comes from subtracting 30 percent from 45 percent; calling it a 15 percent increase would describe a different calculation. Use the explicit wording consistently in charts, commentary and the presentation to the client.
Include samples that explain the finding
Choose an answer where the brand appears, one where a relevant rival appears and one that illustrates the issue requiring action. Keep full responses in the evidence appendix. Put the exact question, observation date and collection method beside each excerpt.
Explain why each sample was selected. A useful note might say that the answer omits a refund condition documented on the product page. Link the reader to that page and quote only the passage needed to understand the finding. Preserve the rest of the answer for review.
Use a consistent sample-selection rule each month. Include an unchanged or unfavorable observation as well as an improvement when both exist. Assign evidence identifiers so a client can move from the summary to the exact answer without searching through an unrelated export.
Connect findings to changes and responsibilities
Maintain a change log with the page URL, issue, approved change, publication date and responsible role. Keep proposed edits separate from published ones. A draft awaiting product confirmation is useful progress, but it belongs in the pending-work column until the page actually changes.
Attach each edit to the questions it addresses and the source of the correct facts. For example, a refund-policy clarification should point to the approved policy and the answer that prompted the review. Schedule the next observation using the existing question wording and recorded method.
Use a repeatable report outline
Copy this outline into your own reporting format and replace every placeholder with a defined observation or decision. Keep the summary short enough to read before the meeting. Put detailed methodology and evidence in the sections that follow.
- Decision summary: main finding, recommended action and required approval.
- Scope: brand, market, language, dates, collection method and question-set version.
- Coverage: scheduled observations, completed answers, failure categories and retries.
- Results: counts, denominators, definitions and comparable period changes.
- Answer samples: selection reason, exact questions, excerpts and evidence identifiers.
- Work completed: page changes, publication dates and supporting product facts.
- Interpretation limits: sample scope, missing evidence and comparison caveats.
- Next work: prioritized actions, responsible roles, dependencies and review dates.
- Appendix: full answers, returned URLs, calculation sheet and change log.
Set a cadence the agency can maintain
Use a weekly internal review to catch collection failures, incorrect labels and urgent factual problems. Use a monthly client review to discuss the stable question set, completed work and next decisions. Treat this as a starting schedule and adjust it to the client's publishing pace.
Anthropic documents that identical API inputs can produce different outputs even at temperature zero. Keep planned repeats in the collection schedule and preserve their evidence. Anthropic's glossary on output variability. Before the meeting, reconcile the reported totals and open every answer used to support a recommendation.
Put the caveats in one place
The report describes sampled questions and collection conditions, not every customer's experience. API and browser samples can differ. Small or uneven samples and method changes can weaken comparisons; returned links alone do not establish visits or sales. Before-and-after observations do not prove a page edit caused movement. State any missing evidence and the practical effect on the decision here.
SearchSeal monitors AI Overview, ChatGPT, Gemini and Perplexity today, saving tracked answers with brand mentions, position, rivals and returned source links. Agencies can use its REST API to export JSON evidence into their own reporting process, keeping questions and observation dates attached. See the agency workflow for organizing client brands and preparing the evidence for review.
Frequently asked questions
What should go on the first page of the report?
Show the main finding, its supporting count or answer example, the action you recommend and any decision the client needs to make. Include the reporting period and a direct path to the underlying evidence.
How should an agency choose answer examples?
Use a written selection rule tied to the finding. Include relevant positive, negative and unchanged observations where available, and attach the full question, date, method and saved answer to each excerpt.
How should pending client work appear?
List it separately from published changes. Name the page, missing approval or product fact, responsible role and next review date so the client can resolve the specific dependency.
What should the agency check before presenting?
Reconcile counts and denominators, confirm that comparison periods use the stated question set and method, verify publication dates, and open each saved answer used in the recommendation.