AI Search Visibility by Country, State, and City with Personas and Languages

Assistants do not have a map pack. They still answer as if the user were in a place, in a language, with a job. We track that in Promptwatch with country, state, city, personas, and language. We do not sell it as local pack rankings.

For Google Business Profile, reviews, and location pages, we still run the local SEO playbook. That work feeds the public facts models repeat. This post is the assistant log.

Where geo tracking actually sits

Country-level tracking is on all paid plans. State and city are on Professional and above (and on the agency plans). Essential at $95/mo is enough to start a national program. Professional is $245/mo when a second locale or a city split matters. Business is $579/mo. Kick-off is $199/mo with unlimited projects and prompts, 10 seats, and state/city included. Explore is free: 10 ChatGPT prompts, one country conversation at most. G2: 4.7/5.

AI Overviews can be tracked for a region. AI Mode is available across supported countries. We still split Overviews from ChatGPT on the slide. Search Console generative reports stay in the Google appendix.

Languages we actually see on accounts include English, Dutch, German, French, Portuguese, Japanese, and others the product lists (Thai, Vietnamese, Chinese simplified and traditional, and more). Per-generation language on Content Agents is a separate switch when we draft. We do not mix NL and EN prompts in one average.

Personas are how we prompt like the buyer: practice manager versus patient, IT versus finance. Same prompt stem, different persona, different answer. That is not a city. Do not stack city and persona on day one or the response budget disappears.

Paid engines: ChatGPT, Gemini, Claude, Perplexity, Grok, Llama, DeepSeek, Mistral, Copilot, AI Overviews, AI Mode. Daily refresh. No instant alerts. No $29 Promptwatch plan.

What we will not call local GEO

A map-pack rank. A BrightLocal or GeoRanker AI SKU we have not verified. A doorway page for every city the model might mention. If we cannot write something true about that city, we do not target it. The playbook already says that.

Otterly at $29 with Gemini as an add-on and lag is a poor multi-city log. Peec at $95 is a mention tracker. Profound Starter at $99 annual is ChatGPT only. Fine if the client already bought it. Insufficient if they asked for Gemini in German in two states.

Visitor analytics can show location of the people who clicked. That is not the same as the simulated city on the prompt. We keep those columns apart.

How this changes the prompt list

We freeze a national list first. Then we duplicate the five revenue prompts into the one city or language that sales already loses. We do not duplicate all 50. Query fan-outs in the second locale often name a local publisher we are absent from. That is a citation ticket, not a new location template.

Webflow and Framer can take a reviewed location page. WordPress publish is still coming soon. Autopublish stays off. Invented neighborhoods stay out.

FAQ

Is city tracking a replacement for GBP?

No. GBP is still the local homepage for Google. City-level Promptwatch checks are how we see whether ChatGPT or Gemini names you when the user is treated as local. Do the playbook. Then measure the assistant.

Can we do city tracking on Essential?

Country only on Essential. Move to Professional, Business, or Kick-off for state and city. We will not pretend otherwise to win a SOW.

How we run it

1. Ship the local playbook items that are actually broken (GBP, NAP, real location copy).
2. Load a national prompt list in Promptwatch. Baseline two weeks.
3. Add one city or one language, plus one persona if the buyer types differently.
4. Read mention vs citation per locale. Do not average them.
5. hello@1001seomedia.com if you want the geo split on the retainer. Tell us the countries you sell in. Do not ask for map-pack positions from this tool.