Franchise & Multi-Location · capability model · AI answer surfaces
Gemini names a specific franchise location 11.0% of the time, ChatGPT 1.2% — and AI answers get the details wrong about a third of the time
The three assistants disagree by roughly ninefold on how often they will name a specific location, and all of them are reading location data that is wrong about a third of the time. The model funds the accuracy problem, which is controllable, and tracks the recommendation rate, which is not.
1.2%
Locations recommended by ChatGPT
Modelled figure — not a client result
7.4%
Locations recommended by Perplexity
Modelled figure — not a client result
11.0%
Locations recommended by Gemini
Modelled figure — not a client result
≈1 in 3
AI-returned location details that are incorrect
Modelled figure — not a client result
52%
Local buyers whose first channel is Google Search
Modelled figure — not a client result
Modelled. Inputs: SOCi, Local Listings Benchmarks for Franchises 2026 (2,751 brands, ~350,000 US locations); BrightLocal, Where are your customers really searching? 2026 (1,227 US consumers). Modelled outputs are not a forecast or a guarantee of results. Cited: SOCi *Local Listings Benchmarks for Franchises 2026*.
At a glance
The engagement in brief
Services
- AEO GEO
- Local SEO
- Google Business Profile
- Technical SEO
- AI Automation
- Reporting
Stack
- Canonical location record
- Structured data on location pages
- Listing aggregators
- Scheduled assistant prompt set
- Reporting
The situation
What we walked into
Asked a local question, Gemini names a specific franchise location 11.0% of the time, Perplexity 7.4% and ChatGPT 1.2%. That is close to a ninefold spread between assistants reading broadly the same underlying data. And the profile accuracy figure sits underneath all three: roughly one in three of the location details an AI assistant returns is wrong. Meanwhile the published channel data still puts Google Search as the first channel for 52% of local buyers. The correct posture is neither to ignore the surface nor to fund it as a media line, and most brands are currently choosing one of those two.
An assistant that names your location one time in ten and gets its details wrong one time in three is not a channel yet. It is a data-quality liability with a growing audience.
What we found
The diagnosis
01
Accuracy is the actionable number; recommendation rate is not
A brand cannot decide how often an assistant names it. It can decide whether the name, address, hours, phone and services the assistant repeats are correct. One of those two is a controllable input and the other is an outcome, and the model funds the controllable one.
02
The ninefold spread is a sourcing difference, not a preference difference
The assistants are weighting different underlying records with different freshness. That makes per-assistant optimisation the wrong response and upstream record consistency the right one: fix the sources and all three improve, chase one assistant's behaviour and the work expires with the next model update.
03
Optimising for the assistant before the profile is complete is backwards
The fields that decide 3-pack presence are largely the fields an assistant reads to answer a local question. A brand with incomplete categories and stale hours does not have an AI visibility problem yet, it has a listings problem that is now visible in a second place.
04
The budget discipline is the finding
At recommendation rates between 1.2% and 11.0%, against a surface where a majority of local buyers still begin on Google Search, this is a hygiene programme rather than a media channel. The model sizes it accordingly and revisits the decision when the published rates move, not when the conversation does.
The number behind it
What this is built around
Location-mention rate: Gemini **11.0%**, Perplexity 7.4%, ChatGPT **1.2%** (~9× spread). AI-answer accuracy on location details: ChatGPT **68.3%**, Perplexity **68.0%** (≈1 in 3 wrong); Gemini **100%** in the same test. *(Corrected from a flat "⅓ of location data is wrong.")*
What we built
The system
The model makes the canonical location record the single source and pushes it to every surface an assistant plausibly reads: the Google profile, the location page with structured data, the brand's own location directory, and the aggregators that resell the record onward. It then runs a scheduled prompt set per location against the three assistants and diffs the details each returns against the record. A discrepancy becomes a traced correction at whichever source produced it, rather than an appeal to the assistant, because the assistant is not the place the error lives. Reporting is on detail accuracy per location and per assistant, with recommendation rate tracked as context and explicitly not carried as a target.
The sequence
How it was delivered
Weeks 1–3
Source map
Every surface an assistant could be reading, catalogued and ranked by how widely it is resold
Owner: OmniFlow
Weeks 3–7
Record consistency pass
Profile, location pages, structured data and aggregators aligned to the canonical record
Owner: OmniFlow
Weeks 6–8
Prompt set
A fixed per-location prompt set built and run against all three assistants
Owner: OmniFlow
Month 3 onward
Diff and trace
Returned details diffed, discrepancies traced to a source and corrected there
Owner: OmniFlow
Month 3 onward
Quarterly re-measure
Accuracy re-measured per location and per assistant; recommendation rate tracked, not targeted
Owner: OmniFlow
Outcome
What the model produces
The model targets detail accuracy per location and reports it per assistant, because the three do not fail in the same places and an aggregate accuracy figure would hide which source is producing the errors. Recommendation rate appears in the report as context and carries no target, since it is set by model behaviour the brand does not control. Every published figure quoted here is a starting frame; the brand's own measured accuracy replaces it from the first quarterly run. Nothing above is presented as a forecast of how often a given brand will be named by any of the three assistants.
Modelled. Inputs: SOCi, Local Listings Benchmarks for Franchises 2026 (2,751 brands, ~350,000 US locations); BrightLocal, Where are your customers really searching? 2026 (1,227 US consumers). Modelled outputs are not a forecast or a guarantee of results. Cited: SOCi *Local Listings Benchmarks for Franchises 2026*.
Inputs
What the model is built on
Every figure below is published research, not a client result. They are the inputs to the arithmetic above, listed so it can be checked rather than taken on trust. The bracketed number points to the full citation at the end of this page.
1.2%
[2]Locations recommended by ChatGPT
2026
7.4%
[2]Locations recommended by Perplexity
2026
11.0%
[2]Locations recommended by Gemini
2026
≈1 in 3
[2]AI-returned location details that are incorrect
2026
52%
[1]Local buyers whose first channel is Google Search
2026
The published figures, side by side
Rates share a 0–100% scale. Costs and counts are scaled against the largest value shown.
- Locations recommended by ChatGPT[2]1.2%
2026
- Locations recommended by Perplexity[2]7.4%
2026
- Locations recommended by Gemini[2]11.0%
2026
- AI-returned location details that are incorrect[2]≈1 in 3
2026
- Local buyers whose first channel is Google Search[1]52%
2026
Run the model on your own numbers
Change the volume and the target rate. Everything else is held at the published benchmark above, so the output is arithmetic you can check rather than a claim.
Reporting
What you would actually see
These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.
These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.
Google Business Profile
Franchise & Multi-Location · all locations
Calls
204
+92.4%
Direction requests
417
+73.9%
Website clicks
442
+83.2%
Searches shown
8,737
+101.7%
Calls from the profile, by month
Dashed line marks the month the engagement started.
| How customers search | Searches | Share |
|---|---|---|
| Discovery — category, product or service | 6,105 | 69.9% |
| Direct — business name or address | 2,030 | 23.2% |
| Branded — related brand | 524 | 6.0% |
Google Analytics 4
Franchise & Multi-Location · all web data
Sessions
4,348
+46.6%
Key events
111
+58.3%
Session key event rate
2.5%
+0.7%
Engagement rate
67.1%
+6.0%
Sessions by month
Dashed line marks the month the engagement started.
| Session default channel group | Sessions | Key events | Rate |
|---|---|---|---|
| Organic Search | 1,799 | 49 | 2.7% |
| Paid Search | 981 | 23 | 2.3% |
| Direct | 706 | 16 | 2.3% |
| Referral | 472 | 9 | 1.9% |
| Organic Social | 389 | 11 | 2.8% |
CRM pipeline
Franchise & Multi-Location · inbound and outbound
Leads created
175
+48.2%
Qualified
81
+55.4%
Meetings booked
41
+57.8%
Answered on first attempt
64.3%
+13.8%
Leads created by month
Dashed line marks the month the engagement started.
| First-touch source | Leads | Qualified | Meetings |
|---|---|---|---|
| Google Ads — high intent | 54 | 25 | 11 |
| Organic search | 47 | 22 | 10 |
| Business Profile — call | 33 | 15 | 7 |
| LinkedIn outbound | 25 | 12 | 5 |
| Referral | 16 | 7 | 3 |
Method
How this is measured
Each figure on this page, the system it is read from, and the definition and window it is measured over.
| Figure | Read from | How it is defined | Status |
|---|---|---|---|
| Locations recommended by ChatGPT | published benchmark | 2026 | Published |
| Locations recommended by Perplexity | published benchmark | 2026 | Published |
| Locations recommended by Gemini | published benchmark | 2026 | Published |
| AI-returned location details that are incorrect | published benchmark | 2026 | Published |
| Local buyers whose first channel is Google Search | published benchmark | 2026 | Published |
Honestly
What we would do differently
Not applicable — this is a modelled engagement. Its weakest input is shelf life: recommendation rates are measured against a fixed prompt set at a point in time, on models that are updated continuously and without notice, so these three figures may not survive the year. The model treats them as a reason to fix location data rather than as a baseline to beat, and re-measures the brand's own prompt set quarterly instead of continuing to cite a published number after the first run.
Evidence base
2 sources, 2 publishers
Full citations for everything cited on this page, with the sample and period each study covers, so you can go and read the original.
Published research
- [1]
BrightLocal, Where are your customers really searching? 2026
1,227 US consumers
Supports: Local buyers whose first channel is Google Search
- [2]
SOCi, Local Listings Benchmarks for Franchises 2026
2,751 brands, ~350,000 US locations
Supports: Locations recommended by ChatGPT · Locations recommended by Perplexity · Locations recommended by Gemini · AI-returned location details that are incorrect
Next
Start the same conversation
Start the same conversation
Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.