TL;DR: AI assistants are replacing Google for the "where should we eat tonight" search, and most restaurants are invisible to them. Fixing that is less technical than you think and most of your competitors haven't started. Here's what to do this quarter.
People used to type "best ramen near me" into Google and scan a list of ten blue links. Now they open ChatGPT or Perplexity and ask: "What's a great ramen spot in the East Village that takes reservations Saturday night for four, not too loud, under $60 a head?" The AI answers in two sentences and links to three sources. If your restaurant isn't one of those sources, you don't exist for that customer.
This isn't a trend worth watching. It's already happening at scale. The behavior shifted faster than the industry noticed, and the people who'll benefit most are the ones who move now, before the playbook becomes table stakes.
AI search is more responsive to deliberate effort than Google ever was. Google took years to reward good content. AI assistants pull from a much smaller source pool, and that pool is still being filled. You can get into it. This article is about how.
SEO is about ranking pages. AEO is about getting cited inside an answer.
With SEO, winning meant appearing on page one of Google's results list. With AEO, winning means being one of the three to five sources that an AI assistant quotes when someone asks a real question. The traffic model is completely different. A customer who clicks one of five links in a Perplexity answer is already filtered; they're already halfway to booking. That's a different quality of visitor than someone scrolling page two of search results.
The mechanics have changed too. Keyword density is functionally dead for this purpose. What AI assistants reward is structured, factual, citable content. They're looking for sources they can pull a clear answer from. If your website answers the question directly, in plain language, in the first hundred words of a page, you have a real shot at the citation. If your website is a mood board with a PDF menu and no text, you're invisible.
The traffic split between traditional search and AI-assisted search is shifting every quarter. Operators who are still optimizing for 2019 Google are doing real work for diminishing returns.
The process is roughly: retrieve, rank, synthesize. The AI identifies the most relevant and credible sources and assembles an answer. Most responses cite somewhere between three and eight source URLs.
The sources that tend to win are not mysterious. Reddit threads carry significant weight. City subreddits, dining subreddits, neighborhood discussions. Trusted industry publications come next: Eater, Time Out, Infatuation, local food blogs with real editorial standards. Then your own structured content, your Google Business Profile, and platforms like Yelp and TripAdvisor.
Across patterns I see in test queries, a few things predict citations reliably: a clear, factual answer in the first hundred words of a page; content structured with headers and questions; and a site that's linked to from other places the AI already trusts.
You can write the most perfectly structured FAQ and still not get cited if nothing credible links to your site. A mention from Eater or Resy's editorial pages does more work than fifty links from random directories.
Every field. Real photos that show the actual space. Current hours that you update when they change. A real link to your menu, not a PDF. Your neighborhood listed in the description. The category set correctly.
Google Business Profile data gets pulled into AI answers constantly. If yours is incomplete or outdated, you're handing citations to whoever around the corner has theirs finished. This takes an afternoon and it's free.
AI systems cannot read PDFs reliably. If your menu is a PDF buried behind a link, it doesn't exist for citation purposes. Put your menu on an actual webpage with real text. List dishes, descriptions, dietary tags, and price ranges.
This also helps your regular SEO. A page with fifty searchable food items and real descriptive text outperforms a PDF link in every context.
Not "about us" copy. Not marketing language. The specific questions guests ask before they book: parking situation, dietary accommodations, reservation policy, accessibility, whether you're good for kids, whether there's a noise issue, what the price range actually is.
Each question gets a clean heading and a two-to-three sentence factual answer. I'll go deeper on the question list below, but the format matters here. Questions as headings, answers as plain prose. That structure is exactly what retrieval systems look for.
Eater, Time Out, Resy's editorial side, the Infatuation, neighborhood food blogs with real readerships. One "best of" mention from any of these drives more AEO value than a hundred keyword-stuffed blog posts on your own site. The citation weight is in a different category. If you've never pitched a local food writer, now is the time.
When you ask guests to leave a review, give them a light prompt. Remind them to mention what they ordered, the occasion, the neighborhood. "Loved the tasting menu at your West Village location for our anniversary" is a more citable review than "great food great service."
That specific language gets indexed. When someone asks an AI for "anniversary dinner in the West Village," the answer can pull directly from review text like that.
Schema.org has markup types for Restaurant, Menu, FAQ, and OpeningHours. When you add this to your site, you're giving AI systems a machine-readable summary of your key facts. It's not required to get cited, but it removes ambiguity. If you're on a modern CMS like Squarespace, Wix, or WordPress, there are plugins that handle most of this without touching code.
Reddit is one of the most-cited sources in ChatGPT answers and Google AI Overviews right now. When someone asks an AI assistant where to eat in Bushwick, there's a real chance the answer references a thread from r/FoodNYC or r/AskNYC from eight months ago.
This does not mean astroturfing. Fake accounts, paid upvotes, planted promotional comments: the algorithm and the humans reading both spot it fast. Don't.
What it does mean: when real guests and real staff are already on those platforms, genuine participation has value. If someone posts asking about natural wine bars in the East Village and your sommelier actually knows the answer, they can respond. Linking to your site once in a long substantive thread is reasonable. A comment that exists only to promote is obvious to everyone.
You want your restaurant mentioned where people are asking real questions and getting real answers. That happens when the people connected to your place are genuinely useful on the internet.
These are the question categories your FAQ page should cover. Each one gets its own heading and a short factual answer. Not marketing copy. Factual.
Hours, location, transit. Current hours, exact address, nearby parking, subway lines.
Accessibility. Step-free entrance, accessible restroom, wheelchair seating at tables or the bar.
Reservations. How far in advance, walk-in wait times, deposit or credit card hold policy.
Groups and private events. Largest party at a regular table, private dining room availability, the process to book it.
Atmosphere. Noise level, lighting, romantic vs. casual, dress code.
Dietary accommodations. Vegetarian, vegan, gluten-free options; severe allergy policy.
Price range. Typical dinner for two with drinks, prix fixe availability, most affordable entry point.
Tipping and payment. Cash accepted, gratuity policy for large parties, service charge.
Special occasions. Outside cake policy, birthday or anniversary acknowledgment, advance notice required.
Kids. Family-friendly, children's menu, high chairs.
Each of these as a clear heading with a two-to-three sentence factual answer. That page will do more AEO work than almost anything else on your site.
Open ChatGPT, Perplexity, and Google AI Overviews. Ask the questions your customers actually ask. Not "best NYC restaurant." Something specific: "Where should I take my parents for a quiet dinner in the West Village, under $80 a person, on a Saturday?" Or: "Good place for a bachelorette group dinner in the Meatpacking District that won't rush us."
Are you cited? In the first answer, or only after a follow-up? When you're named, what context gets attached?
Do this once a month. Not daily. Movement is slow but directional. What you're looking for is a trend over three to six months, not a week-over-week score.
If a competitor keeps showing up in answers you should be winning, look at what they're doing: their FAQ structure, their Google Business Profile, what publications have linked to them. You can learn a lot from who's already in the answer.
Stuffing your About page with neighborhood keywords. Paying for backlinks from generic directories that exist only to sell links. Five-hundred-word blog posts about "What Is Pizza" because someone said Google likes fresh content. Hiding your phone number to push online ordering. Treating Yelp as your only review platform.
None of this moves the needle for AI-assisted search, and most of it was diminishing returns in traditional search anyway. What these systems reward is what real guests reward: clear, honest, specific information about your place.
If you already have basic SEO in place, you can start seeing citation improvements in thirty to sixty days after implementing structured content and FAQ pages. For newer sites starting from scratch, three to six months is a more realistic window. The fundamentals compound over time.
A developer is helpful but not required. Most modern site builders include plugins or built-in tools that add schema markup without writing code. Squarespace, WordPress with Yoast or RankMath, and Wix all have accessible options. The Restaurant and FAQ schema types are well-documented and the implementations are relatively straightforward.
Steps one through three in the list above are owner-operator territory. You do not need outside help to finish your Google Business Profile, convert your menu to HTML, or write an FAQ page. Steps four through six, particularly earned media and structured data implementation, benefit from someone who works in this space regularly. The return is higher there.
Yes. AI systems synthesize whatever's out there, including critical reviews. Hiding or ignoring bad reviews doesn't protect you. Responding to them thoughtfully, publicly, does. Address the concern directly in your reply. That response text gets indexed too, and a well-handled negative review reads differently than an ignored one.
Same playbook. Voice assistants pull from the same structured content sources. Clear FAQ formatting, complete business profile data, and specific factual language on your site all feed voice results the same way they feed text-based AI answers. You don't need a separate strategy.
Step 1: Spend thirty minutes finishing your Google Business Profile this week. Every empty field is an opportunity you're leaving on the table.
Step 2: Open ChatGPT and ask three real customer questions about your category in your neighborhood. See who shows up in the answers. Take notes.
Step 3: If you want help building this for your restaurant or bar, this is part of what my consulting work covers. You can find more at https://jlittrell.com, including ASM Command.
More playbooks like this go out in The Ops Wire newsletter at https://theopswire.substack.com.
Jason Littrell spent 10 years behind the bar in NYC (including Death & Co) and served as USBG NYC president. He now runs his hospitality consulting firm entirely on AI. He hosts the Hospitality Strategy Lab podcast and writes The Ops Wire newsletter.
Jason