GUIDE / AI SEARCH MEASUREMENT

Measure AI search traffic.
Connect visibility to useful enquiries.

Measure AI search in three layers: appearances and citations, recorded website visits, and qualified enquiries. Each answers a different question. Reviewing them together helps you decide which pages deserve further work without treating every AI mention as a visitor or every visitor as a potential customer.

KEY TAKEAWAYS
  • Keep AI visibility, referral visits and qualified enquiries separate; they are different events, not interchangeable results.
  • Use native search reports alongside existing website analytics, recording each report’s scope and date range.
  • Do not add Google generative AI impressions to Web totals: the reporting overlaps.
  • Keep unknown attribution visible and judge changes over comparable periods, with enquiry quality as the commercial check.

1. Define what a useful result means

Before opening a dashboard, define a qualified enquiry for your business. It could mean a genuine request for a service you supply, from a customer you can serve, with enough information to discuss the next step. Keep spam, recruitment requests and unrelated sales pitches outside that count.

Choose a small group of commercially important pages, such as a core service and its supporting guide. Record their preferred URLs, intended audience and purpose. Track both these pages and the whole site so an improvement on one page does not hide a wider decline.

2. Read visibility reports in context

Google’s Generative AI performance report (opens in a new tab) reports impressions in supported Search experiences, including AI Overviews and AI Mode. Review pages, countries, devices and dates. Its data overlaps with Web reporting, so adding these impressions to your existing Web totals would double-count visibility.

An absent report or sparse data does not establish that your website is technically blocked. Check the report’s availability guidance and your property settings. Google’s Search generative AI control (opens in a new tab) includes sites by default; an authorised owner can review whether that setting has been changed.

Bing’s AI Performance announcement (opens in a new tab) describes citations across supported Microsoft and partner experiences. A citation records a reference to content, not a website visit or a sale. Read the report’s coverage before comparing platforms; similarly named metrics may measure different things.

3. Identify the visits you can actually observe

If your site already has suitable analytics, review recorded traffic sources and landing pages. OpenAI’s publisher FAQ (opens in a new tab) says ChatGPT adds utm_source=chatgpt.com to referral URLs. Check how your analytics handles that source rather than relying only on a broad referral-channel total.

Keep each platform’s observed source separate. Record sessions and their landing pages using the same report definition each month. Avoid combining users, sessions and page views into one traffic figure. A person can return several times or visit several pages.

Treat these as recorded referrals, not complete AI influence. People can read an answer and later search your brand, use another device or share a link. Consent choices and measurement settings also affect what is recorded. A direct or unknown visit should remain unassigned unless you have supporting evidence.

4. Keep a repeatable reporting worksheet

Copy this structure into your existing reporting document. Use complete, comparable periods and record the timezone and any filters. Enter “not available” when a measure is missing; do not turn missing data into a zero. Retain the underlying exports so someone else can reproduce the comparison.

Monthly AI search reporting worksheet: record current and previous values for every available measure
MeasureEvidence to recordInterpretation
Google AI impressionsSearch Console export, period, page and filtersVisibility within supported features; overlaps Web totals.
Bing AI citationsAI Performance export, period and cited URLsReferences within report coverage; not visits.
Recorded AI referral sessionsAnalytics source, landing page and periodObserved visits; attribution is incomplete.
Qualified enquiriesDeduplicated enquiry count and qualification ruleCommercial opportunities, not every form submission.
Customer-reported discoveryOptional answer to how the customer found youSupporting evidence; may involve several channels.
Changes and next actionURL, publication date, change made and review ownerContext for investigating movement; not proof of causation.

When counts are small, show the actual numbers before percentage changes. One additional enquiry can create an impressive percentage without demonstrating a reliable trend. If you calculate a referral conversion rate, use qualified enquiries attributable to that same measured visitor group and period, not all enquiries received by the business.

5. Let the evidence choose your next improvement

  • Visibility without recorded visits: review whether the page offers a useful reason to continue reading or evaluate your service.
  • Visits without suitable enquiries: check service fit, geographic availability, mobile usability and the clarity of the next step.
  • Missing visibility on priority pages: inspect indexing, crawl access and content usefulness before publishing more pages.
  • A sudden reporting change: check filters, tracking changes and platform coverage before attributing it to a content edit.

Keep a dated change log and review several comparable periods. Seasonal demand, campaigns and platform changes can move results too. Google’s AI optimisation guidance (opens in a new tab) emphasises useful content and sound technical foundations. Use the evidence to improve those foundations through SEO and AI search and GEO.

Questions people also ask.

Can I add Google AI impressions to my total Web impressions?

No. The Generative AI performance report and Web performance reporting overlap. Present AI impressions as a separate view of supported visibility within search, with matching dates and filters, rather than adding them to Web totals.

Does an AI referral identify the exact question a customer asked?

A recorded source such as chatgpt.com does not by itself identify the original question or answer. Keep that distinction in reports. A customer may voluntarily explain their discovery journey, but do not infer a specific prompt from a landing page alone.

What should I report before website analytics is available?

Report the native search visibility you can access, qualified enquiry counts and any voluntarily reported discovery sources. Label website referral sessions as unavailable. Establish a baseline from real observations instead of estimating missing traffic from citation totals.

PUT IT INTO PRACTICE

Want this done
for your business?

Discuss AI search & GEO