How to set up city-level AI visibility tracking for a local business: a step-by-step guide for 2026

Key takeaways

• City-level AI visibility tracking means testing location-anchored prompts ("best plumber in Tulsa") repeatedly across AI platforms, not a single branded check.
• ChatGPT typically cites only around 5 sources per web search answer, roughly half what AI Overviews and Perplexity cite, which makes local "best X near me" questions genuinely contested rather than winnable outright.
• NAP consistency, schema markup, and a linked website on your Google Business Profile all materially change whether ChatGPT recommends you. Businesses with a website on their Maps listing get recommended 12.3% of the time vs 3.2% without one.
• Most local businesses make the same mistake: testing one rigid phrase per city instead of the conversational variants real customers actually type, or trying to track everything everywhere and drowning in noise.
• Tools like Promptwatch and BrightLocal's Local AI Visibility Tracker can automate this, but a 10-20 prompt manual baseline is a legitimate place to start if you're not ready to pay for software yet.

Why city-level tracking is different from regular AI visibility tracking

Most AI visibility advice assumes you're a single brand competing nationally. A plumber in Tulsa doesn't care if ChatGPT recommends them in Seattle. They care whether a homeowner in their own service area, typing "emergency plumber near me" into ChatGPT at 11pm, ever sees their name.

That's a different measurement problem. You're not tracking one visibility score, you're tracking a grid of scores, one per city or service area, each with its own competitors, its own local directories, and its own answer. A business with five locations needs five separate pictures, not one blended average that hides where you're actually losing.

And the stakes are real. According to Whitespark's study covered by Search Engine Land, Google AI Overviews now appear on 68% of local searches overall, and on 97% of hybrid-intent queries like "average cost of dental implants in Phoenix." Being ranked in the top 10 organically only gives you about a 25% chance of showing up in that AI Overview. Local pack rank and AI visibility are two separate games you have to track separately.

Step 1: Build a prompt set from how customers actually talk, not keywords

The single biggest mistake in local AI tracking is testing a handful of rigid, SEO-style phrases per city and calling it done. Senso.ai's research on this is blunt: teams that plug in "AI visibility tool Chicago" once and see a mention treat that as success while missing every conversational variant a real customer types.

Start with language, not keywords. Pull from three sources:

• Your sales and support team's actual phrasing of problems customers describe ("my water heater is leaking, who do I call")
• Comparison and objection language you lose deals to ("is [competitor] better than you for emergency calls")
• Keyword research converted into question form using an LLM, as Profound's prompt design guide recommends: take "24 hour locksmith Denver" and turn it into "who's open right now for a locksmith in Denver"

For each city or service area, you want a mix of branded, unbranded/category, comparison, and "near me" style prompts. Promptwatch's own citation data shows why the mix matters: non-branded, organic-style prompts are the most crowded, with 52.5% of ChatGPT responses citing 10 or more domains. Once someone already knows your brand name, though, citation counts narrow sharply, only 21.3% of branded prompts pull in that many domains, and your own site plus a handful of third-party pages carry outsized weight. That means your branded prompts and your unbranded prompts need separate strategies, not one combined list.

Senso.ai also flags the opposite failure: trying to brute-force 300 keywords across 50 cities. The result is a report nobody can read and a team that still can't answer "where do we actually show up." Pick 10-20 well-chosen prompts per priority city. BrightLocal's own tracker caps at 20 prompts per location for this exact reason, quality over volume.

Step 2: Pick your priority cities and platforms before you pick a tool

Don't track every location you've ever served. Rank your cities by revenue or growth priority and start with the top three to five. Omnia's monitoring framework recommends the same discipline for platforms: establish a baseline in your primary market first, then expand.

On platform choice, don't spread evenly across eight AI engines on day one. Track where your customers actually are. For most local service businesses that means Google AI Overviews, Google AI Mode, and ChatGPT first. Add Perplexity or Gemini only if you have evidence your audience uses them. Omnia's guide puts it well: two or three engines tracked properly tell you more than eight tracked without context.

It's worth knowing the citation math differs by engine too. Promptwatch's data on sources per response shows ChatGPT typically cites around 5 sources per web search answer, while AI Overviews and Perplexity cite roughly double that, about 10 each. Fewer slots means ChatGPT is the harder, more contested engine to win in; AI Overviews and Perplexity are comparatively more forgiving entry points for a mid-authority local site.

Step 3: Verify how a tool actually generates its "city-level" data

This is the step most business owners skip, and it's the one that determines whether your numbers mean anything.

Some vendors simulate a city by injecting a location string directly into the prompt text rather than running the query through infrastructure actually located in that region. Peec AI has publicly stated it avoids this and instead runs from dedicated infrastructure across 80+ countries. Whether that criticism applies to other named platforms isn't something I'd take at face value from a competitor's marketing page, but it's exactly the right question to put to any vendor before you trust a city-level score: is this a real location-anchored query, or a prompt with a city name bolted on?

Ask directly: how many runs happen per prompt per city, which engines are queried through a real browser or regional endpoint versus an API, and can you see the raw AI answer behind the score. If a vendor can't answer those three questions clearly, be skeptical of the dashboard.

Step 4: Set your baseline manually before you automate

You don't need software to get your first data point. Omnia's guide lays out the manual method clearly: open an incognito browser (or a VPN set to the target city), ask each of your prompts on each platform, and log the results in a spreadsheet. Record whether your brand was mentioned, where it ranked in the answer, what was cited, and the sentiment.

This works fine for 10-20 prompts across a handful of cities. It gets unmanageable past that, and it also runs into a deeper problem: AI answers aren't stable. Searchable's research found that across nearly 3,000 runs of the same prompt, the odds of two runs returning the same brands in the same order were about 1 in 1,000. A single screenshot proves nothing. You need repeated sampling over time to see a real pattern, which is exactly where manual tracking breaks down and automated tools earn their cost.

Step 5: Automate with a tool built for location-level tracking

Once your manual baseline confirms the prompt set is worth tracking regularly, move to a tool that reruns it on a schedule and benchmarks you against named local competitors.

For a single-location business, BrightLocal's tracker is purpose-built and easy to justify. For multi-location brands that also want to see why they're (or aren't) showing up, things like crawler activity and which pages are actually getting cited, a broader platform like Promptwatch is worth the step up, since it pairs the prompt tracking with the diagnostic and content-production layer most pure trackers skip.

Promptwatch

AI search visibility and optimization platform

View more

If you're an agency managing this for multiple local clients, it's worth browsing the wider category before committing. The GEO software directory at bestgeosoftware.com lists dedicated platforms side by side, and ai-rank-tools.com is useful specifically for comparing rank-tracking mechanics across vendors.

Step 6: Fix what's actually broken, not just what's visible

Tracking tells you where you're invisible. It doesn't fix it. TruLata's 2026 guide on getting cited by ChatGPT lists four prerequisites that come up again and again in local AI citation research:

1. LocalBusiness schema markup (use the specific subtype, Plumber, HVACBusiness, Electrician, not generic LocalBusiness) with accurate NAP, hours, and services
2. Consistent NAP across Google Business Profile, Bing Places, Yelp, and relevant directories, matched character for character
3. A visible, active review profile
4. Crawlable HTML with OAI-SearchBot (and other AI crawlers) explicitly allowed in robots.txt

The NAP consistency point matters more than it sounds. If your phone number differs even slightly across your website and your Google Business Profile, that contradiction lowers the AI model's confidence in the data, and a competitor with cleaner listings gets the citation instead.

The data backs this up at scale. According to research covering nearly 140,000 Google Maps listings across 79 US cities, ChatGPT recommends 12.3% of local businesses with a website linked on their Maps listing, versus just 3.2% without one, a nearly 4x gap. Gemini is even harsher: 3% versus 0.3%, better than 10x. If you serve multiple trades, note that the gap varies by category; chiropractors showed the widest gap (8.8x) in that study.

On content, ChatGPT Search draws local citations from business websites (58% of the time), third-party mentions (27%), and directories (15%), per Bigeye Agency's research. That means your own site copy still carries the most weight, but it's not the only lever. Don't neglect service-area pages; just make sure each city page has genuinely unique content, not a template with the city name swapped in, which is a pattern AI models and humans both notice.

Step 7: Re-run on a fixed schedule and watch for drift

Senso.ai's research flags a pattern worth taking seriously: visibility isn't static. A single model update can shift which sources a platform prefers overnight, sometimes a drop from 80% citation share to 40% in a day. Teams that stop testing after one good result get blindsided weeks later.

Weekly reruns on a fixed prompt set is the standard most guides converge on, including Omnia's and Searchable's. Daily is overkill unless you're actively shipping content and want to see what moved. Monthly is too slow to catch drift before it costs you visibility for weeks. When you do need to change your prompt list, treat it as starting a new baseline rather than patching the old one. Comparisons only mean something when the inputs hold still.

Common mistakes to avoid

• Testing one rigid phrase per city instead of the conversational variants customers actually use
• Tracking only branded prompts and missing the category and "near me" queries where most local discovery happens
• Treating a single good screenshot as proof you're covered, when AI answers vary significantly between runs
• Trusting a vendor's "city-level" claim without asking whether it's a real regional query or a prompt with a city name injected
• Building templated city pages that are identical except for a swapped place name
• Letting NAP details drift out of sync across your website, Google Business Profile, and directories

Where to go from here

If you're not ready to pay for tooling, start manual: pick three to five priority cities, write 10-15 conversational prompts per location mixing branded, category, and "near me" phrasing, and log results weekly in a spreadsheet for a month. That alone will tell you more than most businesses in your category currently know about their own AI visibility.

Once the manual process proves the prompt set is worth tracking continuously, move to software that automates the reruns and adds competitor benchmarking. If your goal is understanding the full picture, why you're cited, where the citations come from, and what traffic they actually drive, rather than just a visibility score, a platform like Promptwatch is built for that end-to-end view rather than monitoring alone. For a broader look at local-specific and general-purpose options side by side, the directories at bestgeosoftware.com and surferstack.com are a reasonable next stop before you commit to a subscription.