How local service brands should track AI search traffic

A multi-location service brand can now see fragments of AI search performance in several places. Google reports AI feature appearances inside normal Search Console performance data and has introduced dedicated Search Generative AI performance reports for a subset of properties. Bing Webmaster Tools has an AI Performance public preview that reports cited pages and grounding query phrases. Google Analytics can show referral sessions after someone clicks. Server logs can show AI crawlers and user-triggered fetchers reaching the site.

None of those reports is the whole truth.

For a 70-location HVAC group, the question is not "how much AI traffic did we get?" The useful question is narrower: which AI answer mentioned which branch, which page or profile supported it, which customer clicked, and whether the lead reached the correct location.

Start with a measurement stack, not one report

AI search measurement needs a stack because each source answers a different question.

• Search visibility tells you whether Google or Bing surfaced the site in AI-powered search experiences.
• Citation and source data tells you which URLs, profiles, directories, or articles supported an answer.
• Referral traffic tells you whether a user clicked from ChatGPT, Perplexity, Gemini, Google, Bing, or another AI surface.
• Booked demand tells you whether the right call, form, booking, or job reached the right branch.
• Crawler and fetcher logs are diagnostics. They tell you whether AI systems could access the public page when they tried.
• Prompt samples are diagnostics too. They show how a market and service answer behaved in a controlled check.

Those signals should live next to the same operating fields: market, location, service line, expected branch, landing page, answer text, source URL, lead path, and owner. How to audit AI search visibility across locations covers the broader audit cadence. This article focuses on the tracking layer behind that cadence.

For a roofing brand, that means the Tampa roof repair answer should not be combined with a Houston roof replacement answer. For a med spa group, a Botox query in Columbus should not be mixed with a laser hair removal query in Scottsdale. The visibility report may be brand-level. The fix is usually location-level.

What Google Search Console can and cannot tell you

Google's AI features guidance says appearances in AI Overviews and AI Mode are included in Search Console's overall Search traffic, inside the Performance report under the Web search type. Google also says AI Mode and AI Overviews may use query fan-out, so the response and supporting links can vary across related searches.

That matters because Search Console is useful, but it is not a branch-level lead ledger. It can show pages, queries, clicks, impressions, countries, devices, and the normal performance dimensions. It does not tell a franchise operator that "the Mesa emergency AC answer cited the Phoenix East branch page, then the buyer called the Gilbert phone number."

Google has also introduced dedicated Search Generative AI performance reports for a subset of properties. The reports separate AI Overview and AI Mode performance views while keeping the normal operator caveat: Search Console can help identify pages, queries, clicks, impressions, and countries, but it still does not prove which branch won a booked local job.

That is useful news for operators, but the practical rule stays the same. Use Search Console to find the page and query family. Then use location-level prompt checks, source checks, analytics, and call tracking to figure out whether the right branch won the answer.

Use Bing's AI Performance data as a citation lens

Bing Webmaster Tools gives a cleaner citation-specific view than most operators had a year ago. Its AI Performance public preview reports AI-driven impressions, total citations, average cited pages per AI answer, cited pages from the site, visibility trends, and grounding query phrases. Microsoft is careful about interpretation: the citation count for a URL reflects how often the page was cited in the selected date range, not page importance, rank, or placement.

For a local service brand, that distinction matters. A high-citation corporate guide can be a content win, while a missing location page can still be a lead problem. If Bing cites the brand's generic "roof repair" page but never cites the Tampa page, the reporting action is not "write more about roofing." The action is to inspect whether the Tampa page has service coverage, local proof, reviews, photos, phone routing, and structured facts that agree.

What query fan-out means in Google AI Mode explains why one local question can turn into several source jobs. Bing's grounding-query and cited-page reports give another way to see that source behavior.

GA4 sees the click, not the answer

Google Analytics is still part of the stack because it measures the session after a click reaches the site. GA4 traffic-source dimensions include source, medium, campaign, and referrer context. That makes it useful for isolating referral sessions from domains such as chatgpt.com, perplexity.ai, claude.ai, gemini.google.com, copilot.microsoft.com, and other AI surfaces when they pass referrer data.

But GA4 should not be treated as the AI visibility report. AI answers can mention a brand without sending a click. A user can read an answer, search the brand name later, call from a Business Profile, or book through a third-party listing. Some referrals may arrive as direct traffic when no referrer information is available. Google also notes that most Google searches happen over HTTPS, which affects keyword visibility.

Use GA4 for what it is good at: sessions, landing pages, events, conversions, path quality, and assisted demand after a user reaches the site. Pair it with Search Console and Bing Webmaster Tools for search visibility, and with server logs for crawler access.

For a restoration roll-up, a useful GA4 segment is not "AI traffic." It is "AI referrals landing on water-damage pages in markets where we can serve after-hours calls." That segment can then be compared with phone calls, form starts, appointment submissions, and booked jobs by branch.

Logs show access, not demand

Crawler and fetcher logs are often misunderstood. They are important because AI systems cannot cite or fetch content they cannot reach. They are weak as demand signals because most bot requests are not customers.

OpenAI separates OAI-SearchBot, GPTBot, and ChatGPT-User. OAI-SearchBot is for surfacing websites in ChatGPT search features. GPTBot is for training-related crawling. ChatGPT-User is tied to user actions and is not used to determine whether content appears in Search. Anthropic separates ClaudeBot, Claude-User, and Claude-SearchBot. Perplexity separates PerplexityBot for surfacing and linking websites in Perplexity search results from Perplexity-User for user-requested fetches.

That separation should shape the report. A blocked OAI-SearchBot, Claude-SearchBot, or PerplexityBot request can explain why a source may be unavailable. A spike in ChatGPT-User or Perplexity-User can suggest user-triggered access. Neither is the same thing as a qualified lead.

For more crawler policy detail, pair this article with Which AI crawlers should local businesses allow?.

Tie every AI signal back to a location

The reporting unit should be the local buying moment. That usually means one query, one market, one service, one expected branch, and one source path.

An HVAC group can track "emergency AC repair in Mesa" against the Phoenix East branch. A garage door franchise can track "garage door spring repair in Plano" against the right franchisee. A med spa group can track "laser hair removal near Short North" against the Columbus studio. A hospitality group can track "best hotel for a family near the airport" against the property page, reviews, and booking path.

Each row should answer: did the AI answer mention the brand, did it name the right location, what source did it cite, did a user click, did the session convert, did the call route correctly, and who owns the next fix?

A useful first row can stay plain: source, Bing AI Performance; query, emergency roof repair in Tampa; expected location, Tampa branch; cited URL, the Tampa roof repair page; referrer session, none this week; bot signal, search crawlers reached the page; conversion path, Tampa phone line; owner, location-page lead; next action, add branch proof and retest.

What is a good AI visibility score for a local business? is useful once the team has those rows. A score is only helpful when it points to the source, location, or service gap behind the number.

Do not over-read small samples

AI search results can vary by user, geography, freshness, model behavior, query wording, and retrieval path. A single prompt test is a snapshot, not a ranking report.

That does not make measurement useless. It means the sample needs repeatability. Use the same query set, same target markets, same engines, same date range, and the same inclusion rules each month. Record whether the answer mentioned the brand, whether the source was owned or third-party, whether the location was correct, and whether the lead path was usable.

The safe language is "appeared in this sample," "was cited in this date range," or "sent referral sessions in this period." Avoid saying an AI engine "trusts" a source unless the methodology actually supports that claim.

First 30 days: build a local AI traffic readout

Start with the locations and services where one more booked job changes the month.

• Pick 10 to 25 priority query and market combinations across high-value services.
• Pull Search Console Web performance data, dedicated Search Generative AI reports when available, Bing AI Performance data, GA4 AI referral sessions, server logs for AI bots, and call or form conversion events.
• Create one row per query, market, expected branch, cited source, landing page, AI referral, conversion path, and owner.
• Mark each row as visibility gap, source gap, tracking gap, routing gap, or conversion gap.
• Review the rows monthly with marketing, ops, listings, and the location owner.

The goal is not to make the report larger. The goal is to make it assignable. If Google sees the page but the AI answer cites a directory, marketing and listings inspect the source gap. If ChatGPT-User reaches the page but no user clicks appear, treat it as access context, not traffic. If AI referrals land on the right page but calls route to the wrong branch, ops owns the fix.

For most multi-location brands, the first useful report fits on one page. It says which local answers are visible, which sources support them, which pages or profiles need work, and which locations should be checked again next month.

Sources

• Google Search Central: AI features and your website. Supports how AI Overviews and AI Mode are included in Search Console performance reporting, how query fan-out can affect supporting links, and why normal Search foundations still apply.
• Google Search Central: Search Generative AI performance reports. Supports the dedicated Search Console AI Overview and AI Mode report scope and the subset-of-properties rollout language.
• Google Search Console Help: Search Generative AI performance report. Supports the current report dimensions, metrics, and property availability caveat.
• Bing Webmaster Blog: AI Performance in Bing Webmaster Tools public preview. Supports citation counts, cited pages, grounding query phrases, trends, and local-business information guidance.
• Google Analytics Help: campaigns and traffic sources. Supports the source, medium, referrer, direct-traffic, and traffic-source reporting concepts used in GA4.
• OpenAI: overview of OpenAI crawlers. Supports the distinction between OAI-SearchBot, GPTBot, and ChatGPT-User.
• Anthropic Help Center: web crawling and site owner controls. Supports the distinction between ClaudeBot, Claude-User, and Claude-SearchBot.
• Perplexity docs: Perplexity crawlers. Supports the distinction between PerplexityBot and Perplexity-User, plus IP verification guidance.
• arXiv: Quantifying Uncertainty in AI Visibility. Supports the measurement caveat that generative search visibility should be treated with explicit uncertainty and repeated samples.

Amadeus Peterson is the CTO & Co-Founder of Cheers, the local search platform for multi-location service businesses.