TL;DR: AI assistants invent plausible but wrong addresses, and independent listings with a thin, inconsistent web footprint are hit hardest. The fix is to publish one unambiguous ground truth using Schema.org Place markup, verified coordinates, and a canonical external identifier, then keep that truth consistent across every platform the business appears on.
Ask ChatGPT for the address of a three-star hotel in Porto and it will probably answer with a street name, a number, and a postal code. The answer will sound confident. For the major chains the answer will usually be correct. For the independent boutique property two streets away, the answer has a meaningful probability of being wrong.
This is not a rare edge case. It is a predictable output of how language models generate text, and it has direct consequences for anyone whose business depends on being found at a specific location.
The Mechanics of a Location Hallucination
A language model does not store a database of addresses. It stores a statistical distribution over tokens. When asked for an address, it predicts a sequence of tokens that looks like an address for that type of venue in that city.
If the training data contained the real address many times, consistently, and across authoritative sources, the prediction converges on the correct string. If the address appeared rarely, inconsistently, or not at all, the model interpolates. It picks a street that sounds right for the neighbourhood, a number that fits the block, a postal code that matches the local pattern.
The output is grammatically valid, geographically plausible, and often completely wrong.
The risk is highest for venues with a sparse or inconsistent web footprint. A vacation rental that exists only on one booking platform gives the model far less to anchor on than a chain hotel listed with the same address across hundreds of sources.
A Worked Example
An illustrative query, with an invented property name and address: "What is the address of Casa do Vale guesthouse in Porto?"
A typical hallucinated answer:
Casa do Vale is located at Rua de Santa Catarina 142, 4000-442 Porto, Portugal.
The correct address in this example:
Casa do Vale, Rua do Vale 38, 4200-512 Porto, Portugal.
Wrong street, wrong postal code, wrong side of the city. The hallucinated answer puts the guest in a shopping district three kilometres from the actual guesthouse. The error is not random. Rua de Santa Catarina is the most famous commercial street in Porto and appears heavily in training data for Porto accommodation queries. The model defaulted to the strongest statistical prior for the city.
Why Structured Data Changes the Outcome
A listing page with a properly formed Schema.org Place or LodgingBusiness JSON-LD block gives the model something it can extract rather than invent.
{
"@context": "https://schema.org",
"@type": "LodgingBusiness",
"name": "Casa do Vale",
"address": {
"@type": "PostalAddress",
"streetAddress": "Rua do Vale 38",
"postalCode": "4200-512",
"addressLocality": "Porto",
"addressCountry": "PT"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 41.1621,
"longitude": -8.5937
},
"identifier": {
"@type": "PropertyValue",
"propertyID": "wikidata",
"value": "Q00000000"
}
}
Three features of this block matter for hallucination reduction:
- Structured fields. The model does not have to parse a sentence. Street, postal code, city, and country are separate keys.
- Coordinates that match the address. A crawler can verify that the latitude and longitude fall within the postal code polygon. Mismatches flag the data as low confidence.
- A stable external identifier. Wikidata or a Google Place ID links the listing to a canonical entity. The model can reconcile the address against an authoritative source rather than relying on training-data frequency.
When these three conditions hold, extraction replaces generation. The probability of a hallucinated answer drops sharply.
The NAP Consistency Layer
Schema on the listing page is necessary but not sufficient. AI systems cross-check the address against other public sources: Google Business Profile, OpenStreetMap, Yelp, Tripadvisor, booking platforms, and the open web. When these disagree, confidence falls and the model becomes more likely to hedge or generate.
This is why Name, Address, Phone (NAP) consistency across platforms is a stronger predictor of citation than any single signal. A listing with perfectly formed schema but a conflicting address on Google Business Profile will still perform poorly. The NAP section of our guide to Google AI Overviews for local businesses covers the mechanics.
What Tends to Fix Hallucination Risk
Four measures move the needle most:
1. Publish verified coordinates alongside the address. A written address is a string. Coordinates are a verifiable fact. MapAtlas Geocoding converts raw addresses into precise latitude and longitude at scale and flags inputs that do not resolve cleanly.
2. Wrap location facts in JSON-LD. The Place, LodgingBusiness, Hotel, Restaurant, and LocalBusiness types all accept address, geo, and identifier fields. Missing fields are where the model starts guessing.
3. Reconcile to a canonical identifier. Link the listing to a Wikidata QID or a Google Place ID. This gives AI systems a primary key to deduplicate against.
4. Enrich with nearby context. Hallucinations are not limited to the address field. Models also invent nearby landmarks, transit stops, and walk times. Verified proximity data, generated by MapAtlas GeoEnrich, anchors these claims too. Location-specific FAQ content, marked up with FAQPage schema as described in our AI Overviews guide, is an effective surface for exposing this data.
The Business Cost of a Hallucinated Address
A wrong address surfaced by an AI assistant does not just embarrass the model. It sends a real guest to the wrong place. The downstream effects compound:
- A cancelled booking, or worse, a no-show.
- A negative review that mentions the wrong location, which then becomes training data for the next model generation.
- Reduced citation confidence for the listing going forward, because the public web now contains contradictory signals.
The asymmetry is important. A hallucinated address hurts the listing even when the listing itself is innocent. The fix is not to correct the model directly, which is not possible, but to make the ground truth unambiguous enough that the model has no reason to generate in the first place.
How to Check Your Own Exposure
The free MapAtlas AEO Checker evaluates a listing against 29 structured signals, including address schema, coordinate presence, NAP consistency, and external identifiers. Listings that pass these checks are materially less likely to be misrepresented in AI answers. Listings that fail are the ones where the model has to guess.
Location hallucinations are not a quirk of any one assistant. They are a predictable consequence of training on an open web where the same business appears with slightly different addresses across dozens of sources. The fix is to publish one ground truth in a format AI systems can extract, and to make that ground truth consistent everywhere else the business is represented.
Related reading:
Frequently Asked Questions
What is an AI address hallucination?
An AI address hallucination is when a large language model returns a specific street address, postal code, or coordinate that looks plausible but does not correspond to the real location of the business, landmark, or property being described. It is not a minor rounding error. The model has synthesized an address that does not exist, belongs to a different venue, or combines a real street with the wrong city. For listings this is particularly damaging because the user may travel to the wrong location before realising the answer was fabricated.
Why do AI assistants hallucinate addresses?
Language models generate text by predicting the most likely next token, not by looking up facts. When an address is underrepresented, inconsistent across the web, or blocked from crawling, the model fills the gap with a statistically plausible string: a street name that sounds right for the city, a postal code pattern that matches the region, a number that feels typical. Without a structured ground-truth source to anchor the answer, the model has no mechanism to distinguish a memorised fact from a generated one.
How often do location hallucinations happen in practice?
There is no single reliable rate. It varies by model, language, query type, and the freshness of the underlying data. The pattern is consistent, though: the less structured, consistent data a venue exposes, the more the model invents. Chain hotels and major landmarks, which appear with the same address across many authoritative sources, tend to be answered correctly. Long-tail listings such as independent vacation rentals, boutique hotels, and small restaurants fare worst, because the model has little verified data to extract and fills the gaps itself.
Does Schema.org structured data reduce hallucinations?
Yes, when the data is verified and consistent across sources. Publishing a Place or LodgingBusiness JSON-LD block with accurate geo coordinates, a validated postal address, and cross-references to authoritative identifiers such as Wikidata or Google Place ID gives the model a ground-truth anchor it can extract and cite. Inconsistent schema, for example coordinates that disagree with the written address, tends to lower confidence rather than raise it.
How do I audit my listings for hallucination risk?
Run the listing URL through the free MapAtlas AEO Checker at mapatlas.eu/ai-seo-checker. The checker evaluates 29 structured signals AI systems use to anchor location facts, including geo coordinates, Place schema, NAP consistency across platforms, and the presence of nearby-context fields. Pages missing these signals score high on hallucination risk because the model has to guess instead of extract.
