Measure AI visibility without confusing it with traffic.

Keep four evidence layers separate ↗

An agent can retrieve a page without sending a person to it. A cited page can receive no click. A visit can arrive without a recognizable referrer. Design the reporting system around these different observations instead of combining them into one agentic-traffic number.

Choose the outcome before choosing the KPI ↗

For source recognition, track supported platform AI impressions and captured answers that visibly identify the publication or author. Treat visits as a downstream outcome. An appearance does not by itself establish attention, recall, endorsement, or an inquiry.

For site acquisition, track collected referral sessions and meaningful actions. For a callable tool, track independent successful use and repeat use. Choose the primary measure that matches the intended result and keep the other observations alongside it.

Use the measurements each platform actually provides ↗

Bing Webmaster Tools documents an AI Performance report with citation-related information for supported Microsoft and partner experiences. Interpret that as citation evidence for those covered surfaces, not a census of every assistant. A cited-page count is not a referral count.

Search Console’s generative AI Search report now provides dedicated AI-impression visibility. Those impressions remain part of overall Web performance. Use the report to find pages worth improving, then examine collected visits separately. It does not make every organic session attributable to an AI feature.

GA4’s native AI Assistant channel measures sessions classified from supported assistant sources. Read session source/medium and preserve classification gaps. The linked GA4 walkthrough provides a worked review; citations and crawler requests remain separate measurements.

Source: Bing: Introducing AI Performance in Webmaster Tools; Google Search: AI features and your website; Google Analytics: Default channel group; Google Search Central: Generative AI performance reports

Build a fixed question panel ↗

Write questions that a potential client or hiring leader might ask before encountering your name. Mix definitions, decisions, comparisons, and implementation requests. A portfolio-focused panel might include how to calculate contribution return, how to prepare product data for agents, and how to supervise an automated commerce release.

Record the exact prompt, surface, visible model if provided, date, locale, and whether browsing was enabled. Save the answer and its source links. Keep the wording stable within a baseline period; otherwise a changed prompt and a changed site become confounded.

Repeat observations and keep all results, including missing citations. Answers can vary between runs. A manually selected favorable screenshot is not a trend. A custom API application with its own search and prompt is a different surface from the consumer assistant and should be reported separately.

A baseline before a growth claim ↗

This library launches with a measurement plan, not an invented citation baseline. Its technical checks establish that the pages and exports can be fetched. Search inclusion, citations, referral volume, and commercial outcomes require subsequent observations.

For the first observation window, record which prompts cite the site, which exact pages appear, and whether the answer represents those pages accurately. Where analytics is available, separately record referral sessions, engaged reading, calculator use, and qualified contacts. Do not label uncaptured values as zero.

Use a consistent review interval and disclose the sample size. If ten prompts are each checked twice, the denominator is twenty observations. It is not twenty independent users or an estimate of market share. Compare like surfaces and like questions before interpreting a change.

Diagnose the failure before adding more content ↗

If the page cannot be fetched, inspect crawling and delivery. If it can be fetched but is not indexed, inspect indexability, canonicalization, and whether the page offers distinct value. If it is indexed but rarely cited in the panel, inspect the relevance and completeness of the answer and compare the actual sources selected.

If citations occur without visits, the answer may have resolved the task inside the assistant. For a source-recognition objective, evaluate the relevance, visible attribution, and persistence of those appearances. If visits are also a goal, offer useful material beyond the answer: a calculator, a downloadable contract, or a complete worked example.

If visits occur without inquiries, inspect audience fit and the connection to your work. A page that attracts only unrelated developer troubleshooting may produce impressive activity with little commercial value.

A compact monthly evidence memo ↗

Report the fixed-panel citation observations, the pages cited, answer accuracy issues, known AI referrals, and qualified outcomes in separate rows. Add the content published or substantively revised during the same period and note other changes that could affect the result.

Finish with one decision: refresh an existing answer, build a missing resource, fix access, or improve the path from reading to relevant work. The purpose of measurement is to choose the next investment, not to make an emerging channel look more certain than it is.

Cite this guide

George Kelly. Measure AI visibility without confusing it with traffic. iamgeorgekelly. Updated September 22, 2026. https://www.iamgeorgekelly.com/field-guide/ai-visibility-measurement

Keep the source notes and example labels with an excerpt. For a provider requirement, follow the original documentation in Sources & scope.

Choose your next task ↗ · Browse the source directory ↗