The Evidence Standard Every AI Visibility Report Should Meet

What Should an AI Visibility Report Prove Before You Act on It?

An AI visibility report should prove what was measured, how it was measured, and what the result can and cannot support. Most reports show a score or a share. Few show the evidence underneath, and without that evidence a number cannot tell you whether to change your content, your budget, or your agency.

AI visibility is several outcomes, not one. An AI answer can name your brand, recommend it for a need, cite a page on your site as a source, send a visitor, or influence a purchase. Each of those needs different evidence. Treating them as interchangeable is how a report sends a strategy in the wrong direction.

This article proposes a standard for that evidence. We call it the AI Visibility Evidence Standard, version 1. It is our proposal, not an established industry standard. We apply it to a real Radar report of our own site, and we publish where our own product falls short of it.

A note on evidence. Every Radar figure below comes from production records for pixelmojo.io, read on 25 September 2026. Platform statements are dated and linked to the platform's own documentation or to the research itself.

Why Do AI Visibility Numbers Need an Evidence Standard Now?

Because in 2026 the ways to measure AI visibility multiplied, and they do not measure the same thing. Platforms now publish their own AI reports, research shows that the channel you query changes the answer, and the evidence for popular optimization tactics is thinner than the marketing around it.

Platforms now publish their own AI numbers, and they differ

Google Search Console has a generative AI performance report covering AI Overviews and AI Mode. As of September 2026, its help page lists impressions by page, country, device, and date, excludes Search Labs experiments, and does not list clicks or click-through rate.

Bing's AI Performance report counts citations across Microsoft Copilot, Bing, and select partner experiences. Its Citation Share metric, added on 16 June 2026, is your site's citations as a share of all citations shown for the same grounding query. Bing describes it as an observational metric, not a ranking system or a competitive scoreboard.

A Google impression and a Bing citation are different events, measured on different surfaces. A report that adds them together, or draws them on one trend line, is mixing units.

The channel you query changes the answer

A September 2026 preprint by Uberti-Bona Marin and colleagues evaluated 1,536 responses to product queries from ChatGPT (app and API), Gemini (app and API), and Google AI Overviews. The domains shown through each API overlapped on average only 12.0 percent (ChatGPT) and 14.8 percent (Gemini) with those shown in the matching consumer app. The ChatGPT and Gemini apps shared only 5.4 percent of domains for the same query, and the products they recommended often changed across repeated requests.

The study covers product-recommendation queries, so the exact gap will differ by topic. For product-recommendation queries in that audit, an API answer was not a stand-in for what a customer saw in the app. Many monitoring tools, Radar included, query provider APIs because apps cannot be sampled reliably at scale. That is a defensible choice, as long as the report says so.

A citation is not a mention

In a June 2026 Semrush study of 3,981 domain appearances, 61.7 percent were citations where the brand was never named, 13.2 percent were both a citation and a mention, and 25.1 percent were mentions with no citation. The denominator is every recorded appearance.

A site can supply the evidence for an answer while a competitor gets the recommendation. A report that counts citations as brand visibility, or mentions as endorsement, will overstate what happened.

Optimization claims outrun the evidence

A July 2026 critical survey of 45 studies on generative engine optimization reached a blunt conclusion:

“No reviewed technique shows a stable, longitudinal, cross-platform causal effect on organic discoverability or downstream behavior.”

Olivier Martinez, A Critical Survey of Generative Engine Optimization (2023-2026), arXiv 2607.14035

Google's own optimization guide, last updated 10 July 2026, says Google Search ignores llms.txt and similar AI text files, needs no special schema for its AI features, and requires a page to be indexed and eligible for a snippet. If the tactics are uncertain, measurement is how a business learns what works for it. That raises the bar for the reports themselves.

What Is the AI Visibility Evidence Standard?

The AI Visibility Evidence Standard is a list of eight disclosures that let a reader judge whether an AI visibility result is meaningful, comparable, and actionable. It is Pixelmojo's proposed standard, version 1, published in September 2026. It does not prescribe a score. It prescribes what any score must show.

The difference is easiest to see on one real result, reported two ways. Both columns below describe the same audit, which the next section walks through.

How Does a Real Report Measure Up? Our Own Site, Annotated

The clearest way to test a standard is on a real report. Below is Radar's Citation Check for pixelmojo.io, run on 25 September 2026 at 01:11 UTC, annotated against the eight requirements from the saved record behind the report. The report a customer sees shows less than that record; the self-assessment later in this article lists exactly what. We chose our own site because we can publish every detail.

The audit asked four prompts in the category "AI visibility audit platforms": one branded ("What is Pixelmojo and what do they specialize in?"), two unbranded category prompts ("What are the best AI visibility audit platforms companies?" and "Compare the top AI visibility audit platforms options. What are the pros and cons of each?"), and one reputation prompt ("What do people say about Pixelmojo? Is it a good company?"). The prompts come from templates with the category inserted, which is why one reads awkwardly. A report should show them exactly as sent.

Requirement 1, channel: disclosed, but not in the report itself

Radar's methodology page names the provider APIs and the exact models and states that consumer apps may differ. The report a customer sees shows the engine names, not the model or web search setting for each result. We took both from the saved record. That is a gap under requirement 1.

Web search changes how to read the citation column. Two engines had it on and two had it off. Radar never credits a citation to an engine queried without web search, even if its answer text contains a URL, because that URL was not retrieved as a source for the answer. Their empty citation cells are empty by rule, not by merit.

Requirements 2 and 5, prompts and denominators: the headline hides the split

The report's consistency line reads "Brand mentioned by 3/4 active providers." That is true, and on its own it misleads. All three mentions came from prompts that contained our name. In the two unbranded category prompts, the ones a buyer types before knowing who we are, the four scored engines named us 0 times in 8 answers.

Radar reports that line too ("Mentioned in 0/8 competitive queries"), and it is the line that should lead. A report that pools branded and unbranded prompts is measuring recognition and calling it visibility.

Requirement 4, definitions: a mention is not a correct answer

Here is one prompt from the saved record, answered by two engines in the same audit.

Perplexity's seven captured sources: https://www.pixelmojo.io/press, https://www.pixelmojo.io/about, https://www.pixelmojo.io/, https://www.pixelmojo.io/llms.txt, https://www.pixelmojo.io/blogs/knowledge-graph-llm-visibility-real-data, https://www.pixelmojo.io/blogs/why-we-blocked-ai-training-bots-and-citations-went-up, and https://www.pixelmojo.io/terms-of-service.

Both answers count as a mention, and both were classified primary and neutral. Only one describes the business correctly. The ChatGPT API, without web search, described a digital marketing agency, which is not what Pixelmojo is, from knowledge it dated to October 2023. A report that counts mentions without checking what was said would record that as a win. Radar checks accuracy in a separate Hallucination Check, which is why requirement 4 asks a report to define its terms: a mention says the name appeared, not that the answer was right.

The saved excerpt is also short, about 200 characters around the first mention rather than the whole answer, which limits what anyone can inspect afterwards.

Requirement 6, sources: citations are uneven by engine

Perplexity linked seven of our pages for the branded prompt, including /llms.txt and /terms-of-service, which says something about what it retrieved. Gemini's grounded sources were stored as the domain name only, six entries reading "pixelmojo.io", so the report cannot show which page Gemini used. Under requirement 6 that is a partial disclosure, and we count it as a gap.

Since 25 September 2026, Radar credits a citation only when the link's host is the audited domain or a real subdomain of it, never because the domain appears somewhere in the URL. The same release made the dashboard report new mentions and new linked citations as separate observations.

Requirements 5 and 7, a zero with its denominator

The same audit's share-of-voice check did not find us at all. Its summary reads: "Pixelmojo was not detected in the responses we collected from 4 usable providers (4 attempted) for "AI visibility audit platforms" queries: 20 usable responses in total. 85 other brands were found."

That is how a zero should read. Not "invisible to AI", but absent from 20 specific responses, with a count of what appeared instead.

That zero answers the shortlist question for one category on one date: asked about AI visibility audit platforms, did the engines name Pixelmojo? Scout puts the question in 18 seconds.

Read the transcript

When buyers ask AI who to choose, does your business make the shortlist? Huh? Let's take a closer look.

Requirement 3, uncertainty: a range where judgment is involved

Two checks in the same audit need judgment rather than a rule. For those, Radar asks two different models five times each, claude-sonnet-4-6 and gemini-2.5-flash, and stores the range instead of a single number. On this run the ranges were 52 to 75 and 19 to 39, and both were flagged borderline because the models disagreed. Those judged results sit beside the score; they are not added into it.

“The most useful line in our own report was the one that made us look worst: zero mentions in eight unbranded answers. A standard is worth having only if it puts that line first.”

Lloyd Pilapil, Pixelmojo

What Happens When Method Labels Do Not Track Method Changes?

You lose the ability to say why a score moved. We learned this on our own site: across five full audits in 22 hours, our overall Radar score read 75, 69, 74, 72, and 74, and we cannot cleanly attribute the changes.

The audits ran between 03:00 UTC on 24 September and 01:13 UTC on 25 September 2026. The five checks that read only our site returned the same score every time: Crawl Check 98, AI Readiness 100, llms.txt 100, Robots.txt 82, and Schema 95. The checks that ask AI models moved. The Hallucination Check read 100, 40, 100, 80, and 100. The Answer Engine check read 74, 69, 68, 73, and 74. The Citation Check read 51, 45, 46, 44, and 45.

That looks like model variability, and some of it may be. But the same day, two changes to the Hallucination Check itself were merged, at 06:09 and 09:08 UTC, each within minutes of an audit. We also published content changes to the site. The model answers, our site, and our grader all changed inside one window. Each saved score does carry a method label, but it read the same value in all five audits and through every earlier rubric change, so it cannot separate those three causes.

Radar does keep a public scoring changelog, and its three entries date to July and August 2026. The two Hallucination Check changes of 24 September are not in it. That is a gap in our own practice, and it is the gap requirement 7 is written to close.

A weekly stability check makes the cause findable

From 17 August to 21 September 2026, Radar re-scored a fixed set of 12 public domains each week with its deterministic readiness check and compared each result with an expected range. Of those 72 results, 70 stayed in range. We traced the two exceptions, both in the week of 14 September: one came from a change in our own robots.txt parser, the other from a change on the site itself. Neither came from the models, and because that check has no model input, neither could have.

That is requirement 7 in practice: a known method, a known baseline, and a record of what changed. It is also the part of Radar's own history we most wanted to get right before asking anyone else to meet the standard.

Where Does Radar Meet the Standard, and Where Does It Fall Short?

We judged each requirement by one question: does the report a customer sees disclose it? A limit the report states counts as disclosure. Evidence that is saved but not shown does not. On that test, Radar's report fully discloses denominators today, and every other requirement is partly shown, partly saved behind the report, or not captured yet. We publish the gaps because a standard its author does not apply to itself is marketing.

Our methodology page already notes that part of Radar's scoring is under review. We are not announcing dates here. The point of the table is that you can check it against any future release, the same way you can check any provider's.

How Can You Apply the Standard to the Report You Already Get?

Ask your provider eight questions, one per requirement, and judge the report by how many it can answer from what it already shows.

1. Channel. Did you query the provider APIs or the consumer apps, which models, and with web search on or off?
2. Prompt set. Which exact prompts ran, and which of them contained our brand name?
3. Observations. When did each run happen, how many responses came back usable, and how many times did each prompt run?
4. Definitions. What counts as a mention, a citation, and a recommendation in this report?
5. Denominators. What is each percentage out of?
6. Sources. Which URLs were cited, and which of them are ours?
7. Comparability. Did the method change since the last report, is that change logged with a date, were past results recomputed, and is each zero a real zero or a missing measurement?
8. Outcomes. Which numbers are exposure, which are visits or revenue, and which come from Google's or Bing's own reports?

A report that answers all eight from what it already shows is much closer to decision-grade. A report that answers three is the start of a conversation. If you are choosing a provider rather than auditing one, our guide to hiring a GEO agency covers the commercial side. For why AI answers vary at all, see No Brand Controls Its AI Recommendations, and for tracking setup, our guide to tracking AI citations.

Lloyd and Scout put the zero from our own share-of-voice check through that process in 90 seconds: check the questions, read the answers, compare the questions with what customers actually ask, then make a useful change and check again.

Read the transcript

Lloyd, AI didn't mention us. What do we fix? First, let's check what that zero means. In Radar's share-of-voice check, Pixelmojo wasn't detected in twenty usable answers from four providers. About what? AI visibility audit platforms. So we're invisible? We were missing from this sample. It doesn't tell us why, or what every buyer sees. Then where do we start? Check the questions. Read the answers. See which businesses appeared, and what evidence is available. And check whether those questions match what our customers actually ask. Exactly. That helps us choose what to investigate before changing the site. Find the gap. Make a useful change. Then check again? Yes. And record what changed. You can put that away. Good. I hadn't plugged it in yet.

“In addition to the technical requirements for Search, a site must be included in Search generative AI features in Search Console to be eligible for display in generative AI features on Google Search.”

Google Search Central, AI optimization guide, updated 10 July 2026

That sentence is a useful test of any report. Some eligibility and reporting conditions are visible only inside a platform's own tools. A report that claims to measure them from the outside should say which ones it cannot see.

How Can Other Providers Adopt the Standard?

Any provider can use the AI Visibility Evidence Standard, v1, without asking. Cite it as "Pixelmojo AI Visibility Evidence Standard, v1 (September 2026)" and publish your own table of where you meet each requirement.

We expect it to change. Version 1 does not yet say how many repetitions are enough, how to sample consumer apps reliably, or how to measure recommendations rather than mentions. Those are open questions, and we would rather answer them in public with the rest of the field than set them alone. Critiques and counterexamples are welcome at founders@pixelmojo.io.

How Does Radar Help?

Radar's Citation Tracker runs across four scored engines. Its report shows each prompt, each engine's mention result with a linked-citation marker when the answer also names the brand, and the counts behind every rate. An answer that links the site without naming the brand is counted in the URL citation score but not shown at answer level. The saved record behind it holds more than the report shows today, including the model, timestamp, answer excerpt, and captured cited URLs for each result; those differences are gaps in the table above. For how the scores themselves are built, see A Score You Can Defend.

The Standard Is the Point

AI visibility will keep changing faster than any one tactic. What will separate useful work from noise is whether the numbers behind it can be checked. The AI Visibility Evidence Standard, v1, is our proposal for what that checking requires: the channel, the prompts, the observations, the definitions, the denominators, the sources, the method, and the outcomes, each stated plainly.

We have graded our own product against it and published the result. We invite every provider, agency, and in-house team to do the same.

Want to see your own report measured this way?

• Run the Citation Tracker - Every prompt and engine, with counts beside every rate
• Read the Radar methodology - What Radar measures and how
• Contact Us - Talk through your current AI visibility reporting