What does AI visibility measure?
Here, AI visibility means observed presence of a brand or its content in a defined sample of AI-generated responses. A useful report states which responses were checked, what counted as presence and how the rate was calculated. It does not treat a single test as a view of every user’s answers.
Keep the observation separate from its interpretation. A brand name, a source link and a recommendation answer different questions. Check whether the response identifies the right company and describes it accurately before assigning meaning to its presence.
Separate being named from being recommended
Use separate flags rather than one weighted “visibility score” whose rules are hidden. The following coding scheme is a suggested measurement approach, not a platform standard.
| Flag | What to record | Boundary |
|---|---|---|
| Brand mention | The response names the intended brand | A matching word may identify another company |
| Owned-site citation | A source link points to a URL on the brand’s own site | A third-party page mentioning the brand is a different source |
| Explicit recommendation | The response expressly suggests the brand for the stated need | A name, list entry or positive adjective alone is insufficient |
One response may satisfy all three flags. They overlap; they are not exclusive categories that must total 100%. Save the wording and URLs so another reviewer can check your coding. A citation records a link, not an endorsement, a visit or a sale.
Define the sample before counting
Write down the questions and why they belong in the sample. Keep questions that already name the brand separate from questions that do not: “Is Cedar Lamp Co suitable for a reading corner?” and “What should I look for in a reading lamp?” set different conditions.
Record the platform and feature, date, language, location or market, available settings, exact question and conversation context. Save the response and visible source URLs. If a condition cannot be observed, mark it unknown. For a repeat comparison, retain the same protocol and disclose changes.
Google says AI Mode and AI Overviews may use different models and techniques, so their responses and links can vary; AI Overviews also do not appear on every search. This is a reason to identify the feature being observed rather than pooling all Google results.
Choose a counting unit. In the example below, one usable response is one observation, even if the same question was asked more than once. A question-level result, such as whether a brand appeared at least once across repeated answers, would use a different denominator.
Keep absence and unavailability apart
Record an observed absence only when you have a usable response and the relevant flag is absent. A failed request, inaccessible result or unsaved answer is an unavailable attempt. Do not code it as “brand absent” merely to fill a cell.
For response-level rates, calculate flagged usable responses ÷ all usable responses × 100. Report the unavailable count alongside that denominator. If no responses are usable, the rate is unavailable, not zero. Apply a consistent usability rule and disclose exclusions; selectively keeping favorable answers would make the sample misleading.
A fictional calculation with overlapping flags
Suppose a fictional Cedar Lamp Co review attempts 12 response observations. Ten are usable and two are unavailable. Of the ten usable responses, four name the brand, three link its own site and one explicitly recommends it. Assume the recommendation also names the brand and links its site. These are invented inputs for arithmetic, not outputs observed from an AI service.
| Observation | Flagged responses | Usable responses | Calculation and result |
|---|---|---|---|
| Brand mention | 4 | 10 | 4 ÷ 10 × 100 = 40% |
| Owned-site citation | 3 | 10 | 3 ÷ 10 × 100 = 30% |
| Explicit recommendation | 1 | 10 | 1 ÷ 10 × 100 = 10% |
The 40% mention rate describes those ten usable observations under that protocol. It is not 40% of customers, searches or the market. The two unavailable attempts remain in the collection log. Adding 40%, 30% and 10% would not produce a meaningful overall visibility rate.
Native impressions and sampled presence are different
Google’s Generative AI performance report for Search includes impressions for AI Overviews and AI Mode, excluding Search Labs experiments. It describes impressions as instances where links to your site were shown in a generative AI feature.
Google aggregates the report’s chart by property: two results from the same site in a feature count as one chart impression. A URL filter changes that aggregation to URL. These platform counting rules are different from the response-level coding example above.
Keep native impressions, sampled brand mentions and your own measured visits or conversions as separate measures. A presence rate alone supplies no evidence that someone clicked, bought or saw the same answer. See AI Overviews for that feature’s reporting and inclusion context.
Make comparisons inspectable
Publish the question list, observation period, counting unit, usable and unavailable counts, coding rules and changed conditions with the result. If you report prominence, define it concretely, such as where the name appeared within the saved response; do not equate position with influence.
Review ambiguous identities and wording before aggregating. Preserve disagreements or uncertain cases rather than forcing every response into a favorable flag. Compare like samples, and explain differences instead of attributing a changed rate automatically to a content update.
Do not turn missing data into a zero
Google notes that its generative AI report may be missing when a site has insufficient impressions or is excluded from the features. It also warns that exported values displayed as “~” or “-” become zeros in the downloaded data. Preserve that unavailable/not-a-number distinction when interpreting an export.
Do not fill missing account data with estimates presented as observations. If no report or response sample is available, describe the measurement plan and leave the result unknown. Avoid universal thresholds for “good visibility” unless the comparison has a stated, relevant basis.
Related measurement and optimization terms
AI citation focuses on linked source references and checking what they support. Generative engine optimization concerns efforts to improve inclusion in generative answers. AI visibility is the observation being reported here; it does not establish that an optimization caused a change.
Sources and measurement scope
Google’s AI features guidance supports the Google-specific variation statement. Its dedicated Generative AI performance report documentation supplies the reporting units and caveats above. The response coding scheme and Cedar Lamp Co calculation are editorial measurement examples, not a universal provider metric or a live account report.