Local GEO: How Geography Is Again an AI Visibility Lever
A tradesperson in Lyon types “best plumber near me” into ChatGPT. Local SEO does not disappear with LLMs, but its mechanics change: geography becomes a semantic filter before it is a proximity filter.
A tradesperson in Lyon types "best plumber near me" into ChatGPT. An expat looks up "where to eat vegan in the 11th arrondissement" on Perplexity. A B2B buyer asks Gemini which CRM integrator based in Lille can show up within 48 hours. Three queries, one thing in common: they expect an answer anchored in a precise territory.
Local SEO has existed for fifteen years. Google Business Profile, customer reviews, consistent NAP citations, city pages. None of that know-how disappears with LLMs. But the mechanics change. A classic search engine crosses your geolocated position with an index of nearby results. An LLM has to understand the local context from text, rephrase the query, and choose sources to cite. Geography becomes a semantic filter before it is a proximity filter.
Why localization is surfacing again with LLMs
Generative engines handle a local query by breaking it down. "Best plumber near me" becomes a series of sub-queries: what type of service is being asked for, what geographic area "near me" covers, which criteria define "best" (reviews, availability, prices, specialty). This fan-out decomposition favors businesses whose content answers each of those sub-questions directly, rather than those that only have an address listing.
ChatGPT, Perplexity and Gemini do not all have the same geographic precision. Perplexity leans heavily on fresh web sources and readily cites local directories, regional press articles, neighborhood forums. ChatGPT, when it turns on web search, prefers pages that clearly state their catchment area in the text, not only in the metadata. Gemini, connected to the Google ecosystem, still draws on Business Profile and reviews, but rewrites the answer in its own words, which dilutes the direct link to your listing.
The result: a local business well ranked on Google Maps can stay invisible in a ChatGPT answer if its site never explicitly says "we serve Villeurbanne, Vénissieux and Caluire" in text an AI can read.
How LLMs reconstruct local context
An LLM does not know where you are, unless the application tells it. It therefore works with the explicit geographic signals contained in the query and the sources. Three kinds of signals matter.
The first is textual mentions of area. A page that lists "Paris, Boulogne-Billancourt, Neuilly-sur-Seine" in full, in a normal sentence, is more likely to be associated with those cities than a page that only puts a postcode in the footer.
The second is third-party sources that confirm local presence. A regional press article, a professional directory listing, a dated and localized Google review, a mention on a forum such as Reddit or a local Facebook group. LLMs weigh consistency across several independent sources more than a single site declaring itself the local expert.
The third is structured data. LocalBusiness schema is still read by generative engines that crawl raw HTML, provided the page is not entirely client-side JavaScript. An address, opening hours, a service area declared in JSON-LD give the AI a clean signal, with no ambiguity of interpretation.
What actually makes the difference
Many local businesses think one page per city is enough. That is a mistake that already cost dearly in classic SEO, and costs even more in GEO. A "plumber in Villeurbanne" page that copies the "plumber in Vénissieux" content and only changes the city name adds no new information. An LLM comparing several sources detects that duplication and prefers a source that describes a real local foothold: an active local phone number, a named customer testimonial, a recent job told with verifiable details.
Content that works answers precise local questions. Not "our plumbing services" but "how much does unblocking a drain cost in Lyon in 2026" or "what is the average plumber response time in the 6th arrondissement". That level of granularity matches what LLM fan-out queries are trying to fill.
Local press and specialist directories play a disproportionate role. An article in Le Progrès that mentions your company often weighs more, in an LLM's eyes, than a page on your own site optimized for the keyword. The reason is simple: an independent third-party source is seen as more reliable than a self-declaration. Businesses that invest in local press relations and partnerships with sector directories are, without realizing it, building local GEO capital.
Here is how the two disciplines overlap and diverge:
| Lever | Local SEO | Local GEO |
|---|---|---|
| Google Business Profile | Direct ranking signal in Maps | Secondary signal, reused by Gemini especially |
| Customer reviews | Influences ranking and click-through | Social proof cited in the generated answer |
| Duplicated city pages | Tolerated if slightly differentiated | Penalizing, detected as hollow content |
| Local press and directories | Useful for link building | Third-party source the LLM cites for credibility |
| LocalBusiness structured data | Optional, helps rich snippets | Key signal if the site is readable without JavaScript |
| Real geographic proximity | Direct ranking factor (IP, GPS) | Absent unless the app passes the user's location to the AI |
Pitfalls to avoid
The first pitfall is believing the Google Business Profile is still enough to cover everything. It remains essential for Maps and for Gemini, but it is not read the same way by ChatGPT or Perplexity, which lean more on the open web.
The second pitfall is over-optimization by city. Generating fifty automatic pages for fifty neighboring towns produces content that LLMs identify as programmatic spam. Ten pages that tell a precise local reality beat fifty hollow ones.
The third pitfall is forgetting that freshness matters. A three-year-old review, a 2021 article, an address that changed without an update: LLMs that prefer recent sources drop these signals in favor of more up-to-date competitors, even modest ones.
The last pitfall is treating local GEO as a one-off project. Visibility in generative answers is built over time, by accumulating consistent mentions across the web: a clean site, press, directories, reviews, local social networks. A single audit is not enough. You need monitoring that checks, query after query, how each LLM renders your local presence.
Vurto monitors exactly what ChatGPT, Gemini, Perplexity and Claude answer about your business, city by city, and flags the areas where your local presence stays invisible to AIs.