10.0% → 32.5%+22.5 pp
520 of 1,600 sampled answers mention the brandSuppergrove: modeling a rise from 10% to 32.5% AI visibility.

A place for good food and familiar faces.
Follow 40 dining questions across four AI platforms, from local discovery to referral visits and reservation outcomes. A fictional restaurant case study with a complete, traceable demo dataset.
Fictional case study · synthetic demo data
By 王鹏博
- Concept brand
- Suppergrove · Neighborhood kitchen
- Business model
- One location · direct reservations
- Primary outcome
- Confirmed reservations

Suppergrove is a fictional concept brand used here to explore an independent, single-location restaurant with its own website and a third-party reservation provider. Its audience is people choosing somewhere to eat nearby. The proposed work connects the restaurant’s factual information, local discovery surfaces, and booking handoff so each can be reviewed separately.
Fictional brand, synthetic figures. A worked example of how to read a GEO result.
4.0% → 16.0%+12.0 pp
256 answers cite a brand-owned source40 → 124+210%
Example website visits with an identified AI referral source6 → 22+16
Bookings recorded after the reservation-provider handoff.From the baseline to the final period.
A complete worked example for Suppergrove. Follow the same questions, distinguish mentions from citations, and keep business outcomes tied to a separate record.
10.0% → 32.5% AI visibility.
Share of sampled answers mentioning Suppergrove, across four platforms.
Swipe to inspect all five periods.
Source: Answerova illustrative dataset · 40 fixed prompts × 4 platforms × 10 example runs = 1,600 answers per period.
The result varies by platform.
Brand mentions as a share of sampled answers on each platform. Same questions, same sample size.
Scale: 0–50%. Each platform has 400 example answers per period. Platform totals reconcile with the overall trend.
| Period | Answers | Brand mentions | Visibility | Cited answers | AI visits | Confirmed reservations |
|---|---|---|---|---|---|---|
| M0 | 1,600 | 160 | 10.0% | 64 | 40 | 6 |
| M1 | 1,600 | 224 | 14.0% | 96 | 58 | 9 |
| M2 | 1,600 | 320 | 20.0% | 144 | 76 | 13 |
| M3 | 1,600 | 416 | 26.0% | 208 | 98 | 17 |
| M4 | 1,600 | 520 | 32.5% | 256 | 124 | 22 |
What the customer is really asking
Start with a real buying task, not a prompt that already names the brand. These are example questions to refine before collecting a baseline.
“Where can I book a neighborhood restaurant for a small group dinner?”
Where should we eat near our hotel tonight?
Which neighborhood restaurants take small-group reservations?
Where can we find a menu with clearly explained dietary options?
Which restaurants have a direct booking link?
- 01Dining question
- 02Local fit
- 03Menu & availability
- 04Confirmed reservation
A proposed path from discovery to an outcome. Each step would need its own observable evidence.
Read the starting point.
The M0 example starts with 160 brand mentions in 1,600 sampled answers: 10.0% visibility. Only 64 answers cite a brand-owned source. The website records 40 example AI referral visits and six reservation outcomes. The scenario focuses on a readable menu, consistent local details, and a direct reservation handoff.
The work behind the example.
Three connected layers, adapted to this business model.
The local foundation
Publish a readable menu, a consistent name and address, current opening hours, and a prominent reservation link. Reconcile the website with the restaurant’s owned local profiles. Use Restaurant structured data only for information that is accurate and visible.
The dining context
Build useful explanations around actual dining decisions: location, group size, accessibility, menu, and occasions. Confirm each detail with the restaurant. Earn accurate mentions from relevant local publishers; never invent reviews or suggest a dietary guarantee the kitchen cannot support.
The measurement layer
Save dated answers to a fixed set of non-branded dining questions. Record which restaurants and sources appear. Separately track reservation clicks and completed bookings when the booking provider supports a lawful, reliable handoff. Ask guests how they found the restaurant as an additional source.
How the work would unfold
Agree the scope and responsibilities first. This is a proposed sequence, not a completed project timeline or a promise of results by a particular date.
| Stage | Proposed work | Reviewable output |
|---|---|---|
| Baseline | Check profiles, menu, dining prompts, and the mobile booking flow. | A dated local-discovery and booking baseline. |
| Build | Align business details and publish useful menu and occasion information. | Approved facts, readable pages, and consistent profiles. |
| Release | Verify live pages, local links, and the reservation-provider handoff. | A tested path from the website to booking. |
| Review | Repeat the agreed prompt sample and reconcile reservation events. | Separate answer observations, visits, and confirmed bookings. |
Connect discovery to the business.
From an AI referral to confirmed reservations.
Discovery, visits and business outcomes are separate measures.
AI answer visibility
160 → 520 brand mentionsAI referral visits
40 → 124 visitsConfirmed reservations
6 → 22 outcomesIllustrative outcome-to-visit ratio: 17.7%. Answer visibility is a sampled observation; it is not the denominator for website conversion.
Confirmed bookings
Use reservation-provider records, with duplicates and cancellations handled consistently.
Seated covers
Reconcile with the restaurant’s own records before discussing attendance or revenue.
The useful business question is whether more suitable diners reach a booking that becomes a visit. A mention in an AI answer is an upstream observation. A reservation click is an intent signal. A confirmed booking is a provider event. A seated party, cancellation, or no-show is a separate restaurant outcome.
The source and definition behind each number.
A fixed, non-branded question set
The example uses 40 buyer questions across GPT, Gemini, Claude, and Muse. Ten example runs per platform create 1,600 answers in every period. The same denominators are used from M0 through M4.
Visibility and citations use different counts
AI visibility is answers mentioning the brand divided by all sampled answers. The cited-source rate is answers citing a brand-owned page divided by the same sample. A mention and a citation are counted separately.
Visits and business outcomes have their own source
AI referral visits represent example website analytics records. Confirmed reservations represent a separate synthetic business-event series. Bookings recorded after the reservation-provider handoff. These figures are not inferred from AI answer counts.
A reproducible demo, ready for real evidence
Every number is synthetic and every chart uses the downloadable dataset. These figures demonstrate a reporting structure, not an actual engagement. Real publication would use dated answer exports, analytics records, and reconciled business events.
Replace the synthetic dataset with a dated question set, saved answers and source URLs, verified website changes, and reconciled analytics and business records. Keep the same definitions and disclose any gaps.
Questions about this approach
Are these actual Suppergrove client results?
No. Suppergrove is a fictional concept brand. The figures are synthetic demo data and the imagery is AI-generated. This page shows how a sourced case study could present the relationship between visibility, visits, and business outcomes.
Can GEO replace a restaurant’s local profiles?
No. Accurate local profiles, a readable website, useful menu information, and a functional booking flow work together. The appropriate mix depends on the restaurant and its actual discovery sources.
What if the booking platform does not expose completions?
Measure the events you can verify, such as outbound reservation clicks. Review provider reports separately and describe the attribution gap instead of counting every click as a booking.
What should the restaurant provide first?
Its website, owned profile links, approved menu and business details, booking-provider information, and the dining occasions it wants to serve. Credentials are not needed in the inquiry form.
What would this look like for your brand?
Share your website, your business model, and the customer questions you want to understand. We’ll discuss the evidence and the right scope.
