AEO · Calgary · Restaurants
How local spots get cited when diners ask AI.
The short answer. Diners ask ChatGPT, Perplexity, and Google AI Overviews for restaurant recommendations now. AI engines pick which restaurants to cite based on five signals: clean Restaurant or LocalBusiness JSON-LD, an llms.txt file at the root, real content depth (a story / chef / menu page, not a PDF), named author or chef E-E-A-T, and third-party mentions in Reddit threads and roundups. Most Calgary restaurants ship none of these. The fix is a 4 to 8 hour project that puts you ahead of nearly every competitor in the city.
If you run a restaurant in Calgary, your biggest 2026 marketing risk is not a slow Friday. It is being structurally invisible to the AI engines diners now use to decide where to eat. ChatGPT alone reports more than 800 million weekly active users. Perplexity has crossed 30 million. Google AI Overviews surface above the blue links on roughly half of all relevant search queries in Canada. When a diner types "best Italian in Inglewood" into any of these, the answer they read does not come from your Google Business Profile. It comes from whichever Calgary websites the AI engine could actually parse.
Our recent State of AEO in Calgary 2026 audit found that of 152 Calgary small business websites graded against 14 AI search readiness signals, zero scored Strong. Restaurants were among the worst-performing category. The good news: the structural fixes are well-defined, fast, and durable. This is the playbook.
Before you optimize anything, understand the queries. The dining-related prompts AI engines see most often in Calgary, based on our own usage and on what generates AI Overviews when we test:
Note what is missing from this list: brand-name lookups. Diners who already know your restaurant name will Google it directly. AI engines win the discovery query, the one where the diner has a need but no specific name in mind. Every one of those queries is a chance to be the answer or to be invisible.
From our own AEO audit work and from cross-checking which restaurants ChatGPT and Perplexity actually surface for Calgary queries, these five signals drive the lion's share of citation outcomes for restaurants:
Schema.org markup tells AI engines exactly what your business is in machine-readable form. The restaurant-grade version uses the Restaurant type (a subclass of LocalBusiness) and includes name, address, geo, servesCuisine, priceRange, openingHours, menu, acceptsReservations, telephone, and url. Most Calgary restaurant sites either skip schema entirely or ship a stub from a website builder that only fills out 3 of those fields. Filling all of them is the single highest-leverage technical fix on this list.
An llms.txt file at yourrestaurant.com/llms.txt is a short markdown file that tells AI engines what your site is about and which pages matter. For a restaurant, it should declare neighborhood, cuisine type, hours summary, links to menu / reservations / location / story pages, and a short description. We have a full guide on what llms.txt is and how to structure one. Of 123 audited Calgary small business sites, 76 percent did not have an llms.txt file. This is free real estate.
AI engines reward sites that publish substantive prose about who they are, what they make, and why. A menu PDF is unreadable to most crawlers. A homepage that says only "Italian restaurant in Calgary, view menu" gives the AI nothing to summarize. Restaurants that show up reliably in AI answers have a real About / story page, a chef bio, a description of the cuisine philosophy, and named menu sections with descriptive paragraphs. 500 words minimum across the homepage and About page. More is better up to a point.
Google's E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness) is now mirrored by every major AI engine. The cheapest fix: add a chef bio page with a Person JSON-LD block, link to it from the homepage, and put a <meta name="author"> tag in the HTML head. In our Calgary audit, only 7 percent of small business sites had any named author signal. For a restaurant, putting a real chef and their story on the site is also great brand work, so this is not just a technical fix.
AI engines weight where else your restaurant is mentioned: Reddit threads about Calgary dining, local blog roundups, news features in Avenue Magazine and Calgary Herald, Eater Calgary if you can land it, even Yelp and OpenTable reviews. You cannot fake this overnight, but you can earn it with PR outreach, by pitching local food writers, by showing up in roundups about your neighborhood, and by being genuinely good. The more often your restaurant appears in human-written third-party content, the more confidently AI engines cite you.
If you do nothing else, do these seven things in this order. Each one is well-scoped and finishable in an afternoon.
Allow: rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and anthropic-ai. The default for most CMS templates is to leave this ambiguous, which some AI engines treat as a soft block.Person block linking to it. Ties the restaurant to a real human.From the 152-site Calgary AEO audit, restaurant-specific pass rates were notably weak. Out of the audited Calgary restaurants:
Translation: the technical access is there (almost every Calgary restaurant lets AI crawlers in), but the structural readiness is not. AI engines are showing up at the door and finding the menu is in a PDF and there is no story to summarize. They cite the few restaurants that have done the work.
Imagine two Italian restaurants in Inglewood, both with similar food, similar pricing, similar reviews. Restaurant A has a website with a hero image, a menu PDF, a Google Maps embed, and a reservations link. Restaurant B has the same plus: Restaurant JSON-LD with all 11 fields, an llms.txt declaring "modern Italian in Inglewood, opened 2021, chef Maria Rossi, wood-fire pasta," a chef bio page with Person schema, an HTML menu with paragraph-per-dish descriptions, and a FAQ section that answers "do you take walk-ins" and "is the patio dog-friendly."
When a diner asks Perplexity "best Italian in Inglewood for date night," Perplexity has to summarize a recommendation. Restaurant A is a name with stars. Restaurant B is a story with cuisine philosophy, a chef, a confirmed reservation policy, and a parsed menu. Perplexity cites Restaurant B. The diner books Restaurant B. Same food, same price, same reviews. The cite went to the restaurant whose website was machine-readable.
This is the gap that exists across nearly the entire Calgary restaurant scene right now. Closing it is structural, not creative, and the structural fixes are well-known.
AEO (Answer Engine Optimization) is the practice of structuring a website so AI engines like ChatGPT, Perplexity, Google AI Overviews, and Claude cite it when answering questions. Diners increasingly ask AI for restaurant recommendations instead of searching Google directly. If your restaurant is not structurally readable to AI engines, you are invisible in those answers, even when the diner is two blocks from your front door.
The most common Calgary dining queries we see in AI engines are: best Calgary restaurants for date night, where to eat in Inglewood / Mission / Stephen Avenue, late-night food open now in Calgary, best brunch in Calgary 2026, vegan or vegetarian restaurants Calgary, and best patio Calgary. AI engines answer all of these by reading websites, structured data, and reviews, then synthesizing a recommendation.
AI engines weight five things heavily: structured data on the restaurant website (LocalBusiness or Restaurant JSON-LD with menu, hours, address, cuisine type), the presence of a llms.txt file at the root, content depth (a real About / story page, not just a menu PDF), named author or chef E-E-A-T signals, and how often the restaurant is mentioned in third-party content (Reddit threads, blog roundups, news articles). Reviews matter but not as the primary signal.
llms.txt is a small text file you place at the root of your domain (yourrestaurant.com/llms.txt) that tells AI engines what your site is about and which pages matter. For a restaurant, the file should declare your name, neighborhood, cuisine type, key links (menu, reservations, hours, location), and a short description. It is the highest-leverage AEO signal a restaurant can ship in 2026 and the easiest one to add. Most Calgary restaurants do not have one.
A complete AEO setup for a single-location Calgary restaurant takes 4 to 8 hours of focused work, mostly on copywriting and structured data. The technical pieces (llms.txt, JSON-LD, robots.txt, sitemap.xml) are 30 minutes once the source content exists. The longer pole is writing real About / story / menu / location pages with the depth AI engines reward. Multi-location groups are 12 to 20 hours.
No. SEO and AEO are complementary. Google still drives the largest single share of traffic, and the same structural fixes that improve AEO also help SEO and Google AI Overviews. Think of AEO as a layer on top of solid SEO, not a replacement. The signals overlap heavily: clean schema, fast pages, named authors, real content depth.
If you only do one thing this week, run your restaurant's website through the free Meridian15 AEO Audit. It checks all 14 signals in under 30 seconds and tells you exactly which ones you are missing, no email gate. Compare your score against the 44 percent Calgary average. If you land below 60 percent, the 7-step checklist above will move you to Decent in a single afternoon. From there, named author / E-E-A-T and FAQ schema are the next two compounding wins.
The Calgary restaurants that fix their AEO setup in 2026 will be the ones AI engines cite for the next decade. The window to be early is open. It will not stay open forever.
Where do you stand?
Run the same audit we built for clients. No email gate. Compare your restaurant against the 44% Calgary average.
Run the Audit