How to measure visits and mentions from AI assistants

What can be measured from AI assistants and what cannot

There are two things to count. Visits are the sessions on your site that began when someone clicked a link in an assistant’s answer. They arrive with a referrer, and Google Analytics records them the same way it records a click from Facebook or from Google. Mentions are the times an assistant named your business in an answer, whether or not the customer clicked. A customer who reads that Bear River Land Company handles ranch listings in Cache Valley and then calls the number in the answer never touches your site, and no analytics tool sees it.

Visits are the easier of the two. Google Analytics reports AI Assistant as its own channel in the acquisition reports, and the source column shows chatgpt.com, perplexity.ai, copilot.microsoft.com and gemini.google.com by name. Bing Webmaster Tools and Search Console do not separate AI traffic from ordinary search, and Google does not report AI Overview clicks separately from other Google clicks.

Mentions have no report anywhere. No assistant publishes how often it named you. The only measurement is the one you make yourself, by asking the same questions each month and writing down the answers, which is the log described under what GEO is, used throughout this guide and run beside the answer box check each month. Calls and forms that begin with an assistant can be caught partly by asking every caller how they found you, and the lead tracking page covers the setup.

What unmeasured AI traffic looks like for a land brokerage

Bear River Land Company is a ranch and land brokerage in Logan, Utah, with three agents, about 40 active listings across Cache Valley and southeast Idaho, and a typical listing around 160 acres. The owner has heard buyers mention that they found the firm through ChatGPT, and has no idea whether that is two people or two hundred.

The Google Analytics property was set up by the web designer in 2023 and nobody has opened it since. The default channel report lumps every referral together, and the owner has never looked at the source column. A buyer from Salt Lake asks Perplexity which brokers in Cache Valley specialize in irrigated farm ground, reads an answer that names Bear River Land Company, and calls the office directly from the number in the answer. The receptionist writes down the source as phone call. A second buyer clicks through to the listings page, spends nine minutes, and fills out the contact form. The form does not ask how they found the firm.

The owner is spending time each month on the work in this guide and has no number, up or down, to judge it by. Both buyers were real, and both are invisible in the records.

A worked example: a Logan brokerage's first three months of AI measurement

The owner opened Google Analytics, went to Reports, then Acquisition, then Traffic acquisition, and changed the primary dimension to Session source. The AI sources were already there, unnoticed. The same report was then pulled for three months, and a mention log of ten prompts across four assistants was started alongside it.

The mention log was run on the first of each month, the same ten prompts in ChatGPT, Gemini, Copilot and Perplexity, forty runs.

The contact form gained one question, how did you hear about us, with AI assistant as a choice, and the receptionist began asking every caller. In August, 7 of 31 new inquiries said an assistant. That is the number that matters to a brokerage, and it only exists because someone asked.

For scale, the RV park site near Yellowstone that Hazer works on recorded 299 visits from AI assistants in August 2026 in Google Analytics, and zero in August 2025. A brokerage with 40 listings will not see numbers like a park with hundreds of nightly bookings, and the direction of the line is what to watch, not the size of it.

How to check your own AI assistant traffic

1. Open Google Analytics and go to Reports, then Acquisition, then Traffic acquisition. Look for a row in the channel column labeled AI Assistant. If it is there, click it to see the sources.
2. If the row is not there, change the primary dimension to Session source and type chatgpt in the search box, then perplexity, copilot and gemini. Older properties without the AI Assistant channel still record the sources.
3. Set the date range to compare this month with the same month last year. Write down both totals.
4. Add a column for your key event, whether that is a form, a call click or a booking, so you can see what the AI sessions did rather than only how many there were.
5. Start the mention log. Write ten prompts, run them in all four assistants on the first of the month, and record for each run whether you were named, in what position, and whether any fact was wrong. A spreadsheet with four columns is enough.
6. Add AI assistant such as ChatGPT as a choice on the how-did-you-hear question on your contact form, and ask it on the phone. Compare that count with the Analytics count each month. The gap between them is the mentions that never became a click.

What we do about measuring GEO

You will get a monthly report with the visits from each assistant pulled from your Google Analytics, compared with the same month a year earlier, and the key events those visits produced. Beside it you will see the mention log for your ten prompts, with the count of runs where you were named, named first and named with a wrong fact, so the trend is visible in one table. Where a wrong fact shows up, its source is traced and corrected before the next run. The report and the log start with the audit, which is where the work starts.

Questions people ask about GEO: how to measure visits and mentions from AI assistants