Short answer: an AI visibility report someone can act on puts the method before the numbers, leads with the questions where a competitor was named and you were not, reports each engine separately before any average, keeps mentions, recommendations and citations as separate measures, counts competitors with the same ruler as your own brand, and says plainly what was not measured. One property holds it together: every number can be opened and traced back to the answer text that produced it. Drop that, and nobody can tell a detection bug from a real change.
Most of the rules below exist because a measurement of ours once produced a confident, wrong number, found only by opening the answers behind it. The sections follow the order a reader should meet them in.
Method first: what an AI visibility report states before any number
A percentage without its denominator and its ruler is not a finding; it is a decoration. So the report opens with four or five plain sentences, before any chart:
- The question set and its version. How many questions, written how, and whether the set changed since the last report. Every percentage has the question set as its denominator, and adding easier questions raises the average while nothing improves.
- The engines and the date range. Which assistants were asked, and when the answers were collected.
- The methodology version. Adding a model, enabling web search or changing how brands are detected changes the measurement, not the brand. Enabling web search once moved a site from 3% to 13% while the site did nothing. Runs on different methodology versions are never compared, and the report says which version it uses.
- Whether brand-named questions were excluded. Ask an assistant whether a named company is any good and it will name it. In one of our own runs, 13 of 15 generated questions contained the brand name, and the score read 13% across five engines when the honest value was zero. State how many questions were excluded and why.
Published research faces the same drift, and disclosure is what keeps it usable. Ahrefs reported that 37.9% of URLs cited in Google's AI Overviews also appeared in the first 10 result blocks, against roughly 76% in its July 2025 study, and noted that it had improved its parsing methodology and that AI Overviews had moved to Gemini 3 in between. Readers can see the ruler moved, not only the thing measured. It also means most cited URLs came from outside the top 10, so a ranking report cannot stand in for an AI visibility report.
Questions a reader asks later ("did we change something?") should already be answered here. Link a plain definition of measurement methodology from the report, and see the guide to GEO reporting for clients for presenting the method to people who did not build it.
Lead with the questions you lost
After the method, the first finding should be the list of questions where a competitor was named and you were not, each linked to the answer that produced it. That list is the content brief. It tells a writer which buyer situation to address and shows exactly what the assistant said instead, which a percentage never does.
Keep two neighbouring lists apart. Questions where nobody was named are open ground rather than a loss, often cheaper to win because no incumbent has to be displaced. Questions you already won belong further down; a report that opens with wins gives its reader nothing to do next month.
Two disciplines keep the list honest. Do not attach causes you cannot observe: the data shows that a competitor was named, not why, and an invented reason sends next month's work the wrong way. And call a change real only when it appears in two consecutive runs, because answers vary between runs even when nothing changed.
Presence: each engine on its own, three measures kept apart
Report each engine on its own before showing any combined figure. In our own benchmark one model named 3.5 providers per answer and another 2.1, so an average describes neither. Even two surfaces from one company diverge: across 540,000 query pairs, Ahrefs found Google's AI Mode and AI Overviews cited the same URLs only 13.7% of the time, although their answers reached 86% average semantic similarity. Similar wording, different sources, and a blended number hides exactly that difference.
Within each engine, keep three things apart:
| Measure | What it answers | Why it stays separate |
|---|---|---|
| Mentioned | Was the brand named at all? | Being named in passing is not the same as being suggested. |
| Recommended | Was the brand put forward as an answer to the buyer's question? | This is the outcome buyers act on. |
| Cited | Was one of your pages shown as a source? | Your page can be cited while the answer recommends a competitor. Merging the two flatters the report and hides the real gap. |
Record intent on every question as well. Being named in research questions and absent from purchase questions needs a different fix from the reverse, and one overall percentage cannot tell them apart. A practical layout is one row per engine, the three measures as columns, then the same table for purchase-intent questions only.
Citations and competitors: one ruler for everyone
Count only the citations the answer shows
Only sources marked inside the answer text count as citations. An assistant typically retrieves a dozen or more pages and cites a few, and counting that retrieval pool is the most common way reports overstate reach. It inflated our own citation figures by two to four times before we fixed it. Discard markers that do not resolve to a real URL, and report breadth next to volume: one answer citing twelve of your pages is not twelve times the reach, while the number of distinct questions citing your domain is much harder to inflate.
Show who else is cited, engine by engine
The ranked list of domains cited for your questions tells you where corroboration has to come from, and it needs splitting by engine for the same reason presence does. Profound's analysis of 680 million citations shows how far apart the lists can be: Wikipedia was the most-cited domain in ChatGPT at 7.8% of all citations, while Reddit led both Perplexity, at 6.6%, and Google AI Overviews, at 2.2%.
These are industry-wide figures for a period ending in June 2025, and your category will differ. The point is structural: if the leading source changes by engine, one merged list misdirects the reader for at least one of them. Citation analysis explains how to read your own list.
Measure competitors the way you measure yourself
Share of voice is where reports most often flatter their reader, because any asymmetry in brand detection moves in the reader's favour. An early version of our own measurement showed one brand at 31% share of voice and rank two; measured symmetrically it was 0% and last. The rules that prevent this:
- Count every brand the answer names, not only the ones on a competitor list.
- Resolve spelling variants, legal suffixes and product-line names to one entity before counting, for your brand and theirs alike.
- Show the total number of distinct brands next to the share. Being 1% of 117 brands is a completely different situation from 1% of five.
- Withhold share of voice when the sample is too thin. A percentage from a handful of answers is noise that will swing on the next run.
The method behind these rules is covered in measuring AI share of voice.
What the AI visibility report did not measure
Most reports leave this section out, and that quietly corrupts every section above it. A report that fills a gap with plausible content is worse than a shorter one, because the reader can no longer tell which parts to trust.
| Situation | Correct rendering | Common mistake |
|---|---|---|
| An engine timed out | Blank, with a note | 0%, which turns a flat month into an apparent decline |
| No run in that period | A gap in the series | Interpolation, which invents data |
| A run was slow or partial | Shown, and flagged | Silently dropped from the trend |
| An engine's search crawler is blocked | Reported as an access problem | Reported as a content problem |
| A crawler gets a 200 response with an empty page | Reported as a failed fetch | Counted as reachable |
The third row is not hypothetical: in our own pipeline, measurement runs that took longer than 10 minutes were never snapshotted, so the trend silently dropped them until we found it. The fourth row matters because a zero from an engine whose search agent cannot reach the site has a different fix from a zero caused by thin content. OpenAI, for example, documents OAI-SearchBot as the agent behind ChatGPT's search features in its crawler documentation; if that agent is blocked, no amount of writing will help.
The fifth row is the one most often missed. Most AI crawlers do not execute JavaScript, so a page rendered client-side is an empty shell to them. Test access with the real user agents rather than reading robots.txt, with a browser control group so a site that is simply down is not reported as blocking. The difference between "unmeasured" and "zero" is defined in our glossary entry.
Assembling the report: a side-by-side check and a skeleton
Before a report goes out, check it against this comparison. Everything in the middle column looks fine on a dashboard and misleads anyone who acts on it.
| Element | Weak report | Report you can act on |
|---|---|---|
| Opening | A headline score | Question set, engines, dates and methodology version |
| First finding | What went well | Questions where a competitor was named and you were not |
| Engines | One blended average | Each engine first, combined figure last and labelled |
| Citations | Every page the assistant retrieved | Sources marked in the answer body, with breadth beside volume |
| Competitors | A fixed list, loose matching for your own brand | Every named brand, variants merged, total brand count shown |
| Missing data | Drawn as 0% or interpolated | Left blank or flagged, with a note |
| Change over time | Any movement called a trend | Two consecutive runs on the same methodology version |
| Causes | A reason offered for every loss | Observed facts only, causes left open |
| Numbers | Copied from a dashboard | Recomputed from stored runs |
A report that passes will have roughly this outline:
1. Method: question set (version, exclusions), engines, dates, method version
2. Lost questions, each linked to its answer; open ground listed apart
3. Presence by engine: mentioned / recommended / cited, by intent
4. Citations: answer-body only, breadth and volume, top domains per engine
5. Competitors: same detection for all, total brands, thin samples withheld
6. Not measured: timeouts, gaps, partial runs, blocked or empty fetches
Appendix: numbers recomputed from stored runs
The appendix line matters: a report produced weeks later must still add up, and reading the same stored runs as the dashboard keeps the two from drifting apart. If you want to see these rules applied to a working report rather than a template, the in-app reports page shows how InsightWonder enforces each one.
Sources
- OpenAI, crawler documentation.
- Profound, citation patterns across AI platforms.
- Ahrefs, AI Overview citations and the top 10 results.
- Ahrefs, AI Overviews compared with AI Mode.
- Google Search Central, Search Console generative AI performance reports.
- Pew Research Center, clicks when an AI summary appears.
- Seer Interactive, AI Overview impact on click-through rate.
- Our own measurement incident records, July to September 2026 (Figure 2), all since fixed.