Key takeaways
- Two things cause different brands for the "same" prompt: random sampling noise, and real geographic differences in which sources the AI retrieves. You have to separate them before drawing conclusions.
- A single run tells you almost nothing. Measure mention rate across many runs and many prompts, per city.
- Location can change the fan-out searches the AI runs, the sources it reads, and the local brands it names. A monitor pinned to one place does not represent another.
- Often the problem is coverage, not measurement: you are absent from the sources that market's answers draw on.
- Build a per-city prompt set, run it repeatedly, and compare mention rate, position and cited sources side by side.
The symptom: same words, different brands
You type "best accounting software for small businesses" into ChatGPT. A colleague in another country types the same thing. You get a list with your brand in it. She doesn't. Or a local restaurant group shows up in answers for Rotterdam but disappears in Utrecht, 40 kilometres away.
The first reaction is usually "the AI is broken" or "someone is gaming it." Neither is true. Several mechanisms stack on top of each other, and some are noise while others are real signal about where your brand is weak.
A Reddit thread in r/AskMarketing put it well: when the same prompt returns completely different brands in a different country, it is a different set of companies, so it is less a measurement problem and more a coverage one. You are absent from the sources that market's answers lean on. That framing is the most useful one in this guide, but it only works once you have ruled out noise.
Layer 1: randomness that has nothing to do with location
Before blaming geography, accept that the same prompt from the same place already produces different answers.
Language models generate text one token at a time by sampling from a probability distribution. They do not look up a fixed answer. An OpenAI community thread on exactly this question makes the point bluntly: the variation is a design choice, not a bug. A model that always picked the single most likely word would sound repetitive, so sampling is built in.

A few sources of variation stack up here:
- Sampling and temperature. Even at low temperature the effect does not fully vanish. One 2025 study cited by Promptly found small models answered a repeated multiple-choice question consistently only 50 to 80% of the time.
- Model updates. The version answering today may not be the one that answered last month.
- Conversation context. Earlier turns and small wording changes shift the output.
- Infrastructure quirks. Different servers and batching can round numbers differently and flip close calls.
For brand visibility this means one thing: a single test prompt is not an indicator of anything. Rank4AI makes the same point and measures mention frequency as a percentage across multiple runs. A brand appearing in 7 of 10 responses is in a different position from one appearing in 3 of 10, even though both "appear."

This matters for city comparisons because noise can look exactly like geography. If you ran the prompt once in London and once in Leeds and got different brands, you may have learned nothing.
Layer 2: why answers are crowded to begin with
Answers cite a lot of sources. In Promptwatch Data's analysis of unique domains per ChatGPT response (Sep 28 to Oct 4, 2026, responses with at least one citation), 47.6% of responses cited 10 or more domains and 66.1% cited at least 8. Only 6% cited 3 or fewer. For organic prompts, 52.5% cited 10 or more.
That is my inference rather than something the report states, but it follows: when an answer pulls from 10-plus sources, small shifts in which regional or local sources get retrieved can change which brands make the final list. There is no single "top result" to defend. There is a pool of sources, and which ones land in the pool depends on the search the model ran.
Layer 3: real geographic effects
Now the actual location effects. I should be upfront: I did not find primary-source data quantifying how much ChatGPT, AI Overviews or Perplexity vary by city, and no platform documents exactly how it uses location (IP address, device settings or account details). So treat what follows as mechanisms that are plausible and observable, not measured percentages.
The prompt itself contains a place
The obvious one. "Best dentist in Austin" and "best dentist in Denver" are different questions with different correct answers. If you thought of them as "the same prompt," that is not a bug.
The retrieval queries change
ChatGPT does not search for your prompt verbatim. It splits it into several web searches, known as query fan-outs. Promptwatch Data's ChatGPT query fan-out report found an average of 2.15 searches per response in early December 2025 and about 1.84 by early March, with average query length falling from about 117 characters to the high 80s. The takeaway from that report: content has to match the generated queries, not the user's prompt.
If the generated queries include a city name or a "near me" term, the retrieved pages change with them. That is an inference, but it explains a lot. Your brand may be well covered for the query "accounting software" and thinly covered for "accounting software Manchester." There is also a newer shift: ChatGPT started using the site: operator at scale on August 8, 2026, jumping from about 0.4% to about 17% of fan-out queries overnight. Retrieval behaviour changes under you, which is another reason to keep measuring rather than trust a one-off check.
Different markets, different companies
In many industries the competitive set is simply different per country or city. A regional bank, a local franchise, a country-specific marketplace. The AI is reflecting a real difference in who exists and who gets written about locally.
Source mix differs by sector
Promptwatch Data shows source mixes are heavily industry-dependent. For travel prompts, Skyscanner, Going and Tripadvisor lead ChatGPT citations, with booking and search sites earning more than half. For automotive in August 2026, marketplaces like Autotrader and Cars.com outrank every car brand. If the marketplaces and directories that dominate your category are strong in one city and thin in another, your brand's presence will follow.
Weak local signals
A Neil Patel post claims Google puts multi-location brands in the top three about 36% of the time while ChatGPT recommends them 1.2% of the time. I could not find the underlying study, so treat that as unverified. But the direction is believable: multi-location brands often have strong brand-level pages and weak per-location content, which is exactly what a city-flavoured query would need.
Noise or geography? A quick diagnostic
| Symptom | Likely cause | What to check |
|---|---|---|
| Different brands on two runs from the same city | Sampling noise | Run the prompt 10 or more times and compute mention rate |
| Your brand appears 6 of 10 in City A and 1 of 10 in City B | Real geographic gap | Compare cited sources for each city |
| Different brands because the prompt names a different place | Different question | Normalize the prompt template and swap only the city |
| Brand appears in one language market but not another | Coverage in local-language sources | Check which domains get cited in each language |
| Results shifted overnight for everyone | Model or retrieval change | Look at trend lines across all locations, not one |
How to measure it properly
Step 1: write a prompt template with the city as the only variable
Take a handful of commercial prompts your buyers actually use. Then build versions per city: "best [category] in [city]", "[category] near me", and a version with no location. Keep wording otherwise identical. Senso.ai, a vendor blog so treat it as opinion, suggests 10 to 20 real user questions per city or region, and at least three location-aware prompt sets (for example US, EU and APAC, or city-based if that is how you sell). That is a reasonable starting size.
Step 2: run each prompt many times
Ten runs is a floor. Count the share of responses that mention your brand, not whether it showed up once. Report it as a percentage per city.
Step 3: set the location properly
This is where manual testing breaks down. Typing prompts from your own laptop tests your location only. Senso.ai also warns against assuming a local rank tracker will work for AI results, and I agree: a Google local pack tracker does not tell you what ChatGPT says for a user in a given place. You need tooling that can run the prompt as if asked from that location, in the right country and language.
Step 4: record more than a yes or no
Capture these per city:
- Mention rate across runs
- Position in the answer (first named or fifth)
- Sentiment and the claims made about you
- Which domains were cited
- Which competitors appeared
Promptwatch Data's own advice in the unique-domains report applies: measure across many prompts because a single prompt tells you little, track your position and how ChatGPT describes you, and earn mentions on third-party listicles, reviews and forums.
Step 5: compare cited sources, not just brands
The brand list tells you what happened. The citation list tells you why. If City A's answers cite three local directories and a regional news site that mention you, and City B's answers cite different ones that don't, you have found the gap. The fix is getting covered there, not rewriting your homepage.
Tools that can track by location
I could not find a reliable pricing or feature comparison of geo-tracking tools, so check each vendor's current docs before buying. What I can say is which ones are built for this kind of work.
Promptwatch lets you create monitors by country, language, state and city, and on Business and higher plans pin a monitor to exact coordinates so ChatGPT, Google AI Overviews and Google AI Mode answer as if asked from that spot. Monitors run daily, or every 12, 6 or 1 hours on higher plans, which helps with the noise problem since you get many runs per week. Prices and plan limits are on promptwatch.com/pricing. Its citation reports then show which sources sit behind each city's answers.

Other tools in the category worth a look for multi-market tracking:
Peec AI is built around multi-language tracking.
Profound covers enterprise monitoring across several AI engines.

Otterly.AI is a lower-cost monitor if your needs are basic.
For local-listing health, which feeds many of the directories AI answers cite, tools like BrightLocal and Yext are relevant:

| Tool | Location-aware tracking | Good fit |
|---|---|---|
| Promptwatch | Country, language, state, city, exact coordinates (Business and up) | Teams that want to measure and then fix gaps |
| Peec AI | Multi-language | Multi-country monitoring |
| Profound | Multi-engine monitoring | Enterprise brands |
| Otterly.AI | Basic monitoring | Small budgets |
| BrightLocal | Local listings and rankings, not AI answers | Fixing the listings AI sources from |
If you are shopping around, the GEO software directory lists more options.
What to do once you find the gap
Say your brand shows up in 60% of runs for City A and 10% for City B. The playbook:
- List the domains cited in City A's answers that mention you, and the domains cited in City B's answers that do not.
- Find local listicles, directories, review sites and forums in City B that name your competitors but not you.
- Build real local content: location pages with local facts, staff, case studies and addresses, not templated copy with the city name swapped.
- Earn mentions on those third-party pages. This is the part that moves the needle most, since answers draw on many sources.
- Re-run the same prompt set after a few weeks and compare mention rate against your baseline.
Also check that AI crawlers can read your location pages at all. If your city pages are blocked or render poorly, no amount of content helps. Crawler logs make this visible; Promptwatch's AI crawler logs show which bots hit which pages and where they fail.
If you would rather hand this off, an agency that does GEO work can run the measurement and the outreach. 1001 SEO Media does this kind of AI search and local visibility work.
Common mistakes
- Testing once and drawing conclusions. One run per city is a coin flip.
- Testing from your own location and assuming it generalizes.
- Changing wording between cities, so you are comparing different questions.
- Treating the brand list as the whole story and ignoring citations.
- Using a Google rank tracker as a proxy for AI answers.
- Chasing one answer instead of the trend. Models and retrieval change, so keep a baseline and watch the trend line.
Bottom line
Different brands in different cities come from two sources: sampling noise you can average out, and coverage gaps you can fix. Run a fixed prompt template per city, repeat it enough times to get a mention rate, and compare the sources behind each answer. For more on how AI answers get built, browse Promptwatch Data. To try location-specific monitoring yourself, start with the free AI visibility report or the 7-day trial.


