Local AEO: how to get recommended by AI assistants when buyers add 'near me'
Local AEO is dominated by Google's Knowledge Graph and Business Profile — Gemini wins this category by a mile. The playbook for restaurants, services, and brick-and-mortar businesses.
"Best Italian restaurant near me" used to mean opening Google Maps, scanning ten pins, and reading the first three sets of reviews. By mid-2026 that same query is just as often spoken to Gemini in the car, typed into ChatGPT on a phone, or buried inside the AI Overviews block on a regular Google SERP. The shape of the answer changed with it. The map shows ten pins. The AI returns one or two recommendations with a confident sentence about why.
For a local business, that's a different game. Missing from the AI's one-sentence answer means lost foot traffic, lost reservations, lost calls — and you don't see it happen, because the user never lands on a search results page. A dentist in Brooklyn Heights with strong AEO captures the early-funnel "best dentist near me" query that historically belonged to Yelp's first page. A dentist without it watches that pipeline quietly evaporate.
The playbook for getting recommended by AI assistants for local queries overlaps with generic AEO in places, and diverges sharply in others. This post is what's actually different.
How AI engines treat local differently
Three architectural facts shape every local-AEO decision. Get these wrong and the rest of the work doesn't matter.
Gemini is structurally dominant in local. It taps Google Business Profile, Google Maps, and the Knowledge Graph in ways no other engine does. When you ask Gemini "best ramen in Austin," it's effectively running a local pack lookup augmented by reviews and your Knowledge Panel — then writing a sentence over the top. The other engines lag here significantly. In our scans, Gemini cites the actual top-3 GBP-ranked businesses for a local query roughly 4-5x more often than ChatGPT does for the same prompt.1
ChatGPT and Perplexity lean on aggregators. For local queries they're training-data heavy and retrieval thin. Without first-party access to Google's local index, they fall back on Yelp, Tripadvisor, OpenTable, Healthgrades, and city-specific "best of" lists. A salon in Miami that doesn't show up on the local Yelp roundup or in a Miami New Times "best of South Beach" article is largely invisible to ChatGPT, no matter how clean its on-site SEO is.
Voice and typed queries route differently. "Hey Gemini, find me the closest plumber" routes through Google Assistant infrastructure and returns one result, usually the highest-rated GBP within a few miles. "Best emergency plumber in Phoenix" typed into Gemini's text box returns 3-5 listed options with reasoning. The first is winner-take-all. The second leaves room for second and third place. Most local businesses optimize only for the second and miss the first.
The implication: you can't approach a Gemini citation strategy the way you approach a Perplexity one. The signals overlap maybe 30%. The rest is its own discipline.
The 5 signals that matter for local AEO
Across hundreds of local-business scans, five signals consistently move citation rates on local prompts. Ranked roughly by leverage:
1. A fully completed Google Business Profile
This is the most underused signal in local AEO. Most GBPs are 40-60% complete — the basics filled in, the long tail empty. Categories, hours, photos, attributes, services, products, posts, Q&A — every one of those fields is a retrieval input for Gemini. A dental practice that lists 8 services with descriptions (cleanings, whitening, Invisalign, emergency, pediatric, cosmetic, implants, periodontics) earns citations for queries Gemini wouldn't even consider for a practice that only listed "general dentistry." Photos updated this month outscore photos from 2022. Posts in the last 30 days signal an active business; an empty Posts tab signals a dead one.
2. NAP consistency across 10+ aggregators
Name, Address, Phone. Same exact form on every platform — Yelp, Tripadvisor, Facebook, Apple Maps, Bing Places, Foursquare, Nextdoor, Yellow Pages, Better Business Bureau, BBB. If your GBP says "Suite 200" and your Yelp says "Ste 200" and your Facebook says no suite at all, the engines treat these as three signals of unclear authority instead of one signal of three-way confirmation. ChatGPT and Claude specifically cross-reference NAP across aggregators when they're not sure which "Joe's Pizza" the user means. Inconsistency creates entity ambiguity, and ambiguity loses citations.
3. Real customer reviews on Google + niche platforms
Volume and freshness, not just average rating. A restaurant in Brooklyn with 200 Google reviews averaging 4.6 stars, with 30 of them in the last 90 days, gets cited more often than a restaurant with 800 reviews averaging 4.8 stars where the most recent is from 2024. AI engines down-weight aggregate ratings from stale review pools. The niche platforms matter too — OpenTable for restaurants, Healthgrades and Zocdoc for medical, Avvo for legal, MindBody for fitness studios, The Knot for wedding vendors. ChatGPT specifically over-weights these category-specific review sites when answering category queries.
4. LocalBusiness JSON-LD schema
Generic Organization schema is not enough for local. You need LocalBusiness (or one of its more specific subtypes — Restaurant, Dentist, DaySpa, Plumber, HealthAndBeautyBusiness, etc.) with geo.latitude, geo.longitude, full openingHoursSpecification, priceRange, paymentAccepted, currenciesAccepted, and areaServed. Most local sites have either no schema or a stripped-down Organization block. The complete version is parsed by every retrieval pipeline and is the single highest-leverage on-domain change you can make.
5. Geo-modified content
A dental practice page that mentions "Brooklyn Heights dental services" and "dentist near Atlantic Avenue" beats one that says "professional dentistry" — full stop, no contest. The retrieval pass for any local query includes the place name as a hard filter. If your H1, your meta description, and your opening paragraph don't mention the neighborhood or city, you're invisible to that query before the re-ranker even sees you. This sounds obvious. It's the most common single failure we see on local sites, including local sites with otherwise excellent SEO.
The 6 tactics that move local AEO citations
Ranked by leverage per hour invested. Most teams work the bottom of this list and skip the top.
Tactic 1 — Complete every Google Business Profile field
Forty-five minutes of work, six months of payoff. Open your GBP dashboard, audit every empty field, fill it. Especially: Services (with descriptions, not just names), Attributes (wheelchair accessible, free Wi-Fi, accepts credit cards, kid-friendly, outdoor seating — these are direct retrieval inputs), Q&A (seed it yourself with the 10 questions you get most often, answer them with full sentences), and Products (yes, even for services businesses — listing "Teeth Whitening — $350" creates a structured price signal). Use our Google Business Profile audit to find the gaps you're missing.
Tactic 2 — Build proper LocalBusiness JSON-LD
The full schema, on every location page. If you have three locations, three pages, three blocks of schema with different geo coordinates and addresses. Use our schema generator — pick LocalBusiness or the closest subtype, fill in the geo, opening hours, and payment fields, paste the result into your <head>. We've seen plumber sites in Phoenix double their Gemini citation rate in three weeks from this single change. The signal isn't subtle.
Tactic 3 — Solicit 30-50 recent reviews
Aim for steady accumulation, not a single sprint. A gym in Chicago that adds 4-6 Google reviews a month from members is a stronger signal than one that buys 50 reviews in a weekend. The drip pattern is what AI engines look for — it correlates with active operation. Bake a review request into your post-purchase flow: confirmation email, receipt, follow-up text after a treatment or class. Don't ask for five stars. Ask for honest feedback. The 4.6 average outperforms the 5.0 average in citation tests because 5.0 looks fake.
Tactic 4 — Get a mention in hyperlocal media
This is the leverage point most local businesses ignore because it feels old-school. It isn't. A neighborhood blog, a city tourism site, a "best of" roundup from a local magazine, a feature in a community newsletter — these dominate Yelp for many ChatGPT and Perplexity citations on local queries. The engines treat a Brooklyn Paper feature on a Brooklyn restaurant as a categorically higher trust signal than a corporate "as seen in" press release. The motion: identify the 5-10 hyperlocal publications in your area, pitch a story tied to something real (a community event you sponsor, a new menu item with provenance, a local hiring milestone), or contribute to a roundup someone else is writing.
Tactic 5 — Match voice and typed query variants
The phrasing differs. "Dentist near me" (voice, looking for closest match), "best dentist in Brooklyn" (typed, looking for ranked options), "emergency dentist open Sunday in Brooklyn Heights" (typed, looking for filtered match). Each is a different retrieval shape. Your homepage H1 should target one. Your FAQ should hit the others. A page with "Best dentist in Brooklyn Heights — open weekends, emergency appointments" in the H1 + meta + first paragraph captures both the typed and voice variants for the same query.
Tactic 6 — Verify per-engine, especially Gemini
Run your domain through our AI visibility checker and look at the Gemini column separately from the rest. For local queries, Gemini is the channel that matters most by volume, and your win-rate there is the leading indicator of foot traffic. If your generic AEO score is 50% but your Gemini score on local prompts is 15%, the score is hiding a problem. Segment, don't average.
What NOT to do — the local-specific traps
Three patterns burn time and damage local-AEO standing faster than anything else:
-
Buying Google reviews. Google's filter has gotten ruthlessly good at detecting clusters — same IP range, same review timing, same phrasing patterns. When the filter catches you, rankings collapse and the AI engines follow within days. We've seen brand citation rates drop 60% in two weeks after a botched review-buying campaign. Claude and Gemini cross-reference Google's filter signals — once Google flags you, multiple engines down-weight you.
-
Treating your GBP as set-and-forget. A dentist in Austin filled out their GBP completely in 2023, then never touched it again. Their citation rate on "best dentist in Austin" dropped 30% over 18 months as the engines watched their Posts tab go cold, their Photos tab stay frozen, their Q&A unanswered. Recency matters. Aim for a Post a week, a few photos a month, and Q&A responses within 48 hours.
-
Ignoring Gemini because "ChatGPT matters more." For local queries this is exactly backward. Gemini volume on local intent dominates the other engines by 5-10x on most categories. Optimizing for ChatGPT first is the right move for SaaS. For a Phoenix plumber, it's malpractice.
How to verify your work
The closed-loop check has four steps:
- Query each engine for "best [your category] in [your neighborhood]" — Gemini, ChatGPT, Perplexity at minimum
- Screenshot the AI Overviews citation cards on Google for the same query, weekly
- Run our AI visibility checker on your domain with a prompt set tuned to local intent
- Segment Gemini's results from the rest — they should diverge, and the gap is your most important number
A monthly cadence is too slow for an active local-AEO program. Weekly works. If you're making changes — completing GBP fields, adding schema, soliciting reviews — daily scans during the change window let you attribute deltas to specific tactics.
The full AEO tools catalog covers the other instrumentation you'll want once you have a baseline — schema generation, citation source radar, query generation. Your starting set for local is the GBP audit, the schema generator, and the AI visibility checker. Add the rest after.
If you're auditing a site cold and want a fast first pass, our AEO audit tool walks the on-page signals (schema, geo modifiers, internal linking) end to end and flags the biggest gaps before you commit to a full program.
TL;DR
Local AEO is Gemini's category. Complete your Google Business Profile down to the last attribute. Ship proper LocalBusiness JSON-LD on every location page with full geo and opening hours. Build a steady drip of real recent reviews on Google plus the niche platform for your category. Get covered by a hyperlocal publication. Mention your neighborhood explicitly in H1s and meta. Then measure Gemini separately from the other engines, because the gap between your generic AEO score and your Gemini local score is the number that predicts foot traffic.
The boring infrastructure work — GBP fields, schema, NAP consistency, reviews — outperforms anything fancy. AI engines reward local businesses that look obviously real. The job is to look obviously real, in every place the engines look.
Related reading
- AEO for ecommerce — when product and place overlap, like a bike shop with online sales
- AEO for SaaS — the polar opposite playbook, no place, all subscription
- AEO for B2B — long sales cycles, comparison-heavy, different signal mix
- How to get cited by Gemini — Gemini is THE local engine, full playbook
- How to win back traffic lost to Google AI Overviews — AI Overviews now dominates many local SERPs
- Perplexity citations playbook — the patterns that lift you on the aggregator-driven engines
Footnotes
-
Internal FixAEO scan data across 2,000+ local-intent prompts spanning restaurants, dentists, plumbers, gyms, and salons in 12 US metros, Q1-Q2 2026. Methodology and prompt-set design notes available on request. ↩
Want to see how your brand scores?
FixAEO runs all the checks in this post automatically — free, no signup.
Run a free scan