Back to Blog

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.

What Diners Actually Ask AI Engines

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:

• Neighborhood + cuisine. "Best ramen in Calgary," "where to eat in Inglewood," "Italian restaurants near Stephen Avenue."
• Occasion-driven. "Best date night restaurants Calgary 2026," "where to take a client for dinner downtown Calgary," "anniversary dinner Calgary."
• Constraint-driven. "Vegan restaurants Calgary," "gluten-free brunch Calgary," "Calgary restaurants open late," "kid-friendly restaurants Calgary."
• Comparison-driven. "Is X restaurant or Y restaurant better for date night," "Model Milk vs Bridgette Bar."
• Decision-stage. "What should I order at <restaurant>," "is <restaurant> good for groups."

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.

Five Parts of a Strong Restaurant Foundation

These are practical parts of a crawlable, verifiable restaurant site. Retrieval and source-selection systems change, and none of the five guarantees a citation.

1. Restaurant or LocalBusiness JSON-LD with depth

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.

2. llms.txt at the site root

An llms.txt file is an optional Markdown summary at yourrestaurant.com/llms.txt. Compatible tools may use it to discover selected public pages, but support is incomplete and Google does not use it. Read the full llms.txt reference before deciding whether to publish one.

3. Real content depth, not a menu PDF

Crawlable prose about the restaurant, chef, cuisine, and menu gives retrieval systems more factual material than a menu PDF or one-line homepage. There is no universal word-count floor. Write enough to answer real diner questions without padding the page.

4. Named author or chef E-E-A-T

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.

5. Third-party mentions

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.

The 7-Step AEO Checklist for Calgary Restaurants

If you do nothing else, do these seven things in this order. Each one is well-scoped and finishable in an afternoon.

1. Add Restaurant JSON-LD with all 11 fields (name, address, geo, servesCuisine, priceRange, openingHours, menu URL, acceptsReservations, telephone, url, image). Validate at search.google.com/test/rich-results before shipping.
2. Consider an optional llms.txt file. Publish one only if a short, maintained summary of your public pages is useful. It does not guarantee citations.
3. Check retrieval access in robots.txt. Confirm that OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, and PerplexityBot are not blocked. Decide training crawler access separately.
4. Write a real About or story page. Explain who you are, why the restaurant exists, the cuisine philosophy, and the chef's background. There is no universal word-count floor.
5. Add a chef bio with Person schema. Include a real photo, relevant experience, and an accurate JSON-LD Person block. Write enough to establish who the chef is without padding the page.
6. Publish your menu as crawlable HTML, not a PDF. If your menu is a PDF, AI engines treat it as opaque. Put it in actual page markup with section headings, item names, and a one-line description per item. PDFs can stay as a download link, but the canonical menu must be HTML.
7. Add FAQ schema only to a real visible FAQ section. Cover the questions diners actually ask: parking, reservations, dietary accommodations, group sizing, dress code, and average meal duration. The visible answers and JSON-LD must match exactly. FAQ parity is an optional 2-point audit check, not a ranking or citation lever.

What Calgary Restaurants Are Missing Today

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.

A Worked Example: Two Calgary Restaurants, Same Cuisine

Imagine two Italian restaurants in Inglewood with similar food, pricing, and reviews. Restaurant A has a hero image, a menu PDF, a map, and a reservations link. Restaurant B adds accurate Restaurant JSON-LD, a chef bio, a crawlable HTML menu, and a visible FAQ section with matching schema. It may also publish an optional llms.txt summary. The stronger site gives retrieval systems more public facts to verify, but no single addition guarantees a citation.

When a diner asks Perplexity for the best Italian restaurant in Inglewood for date night, Restaurant B offers more verifiable source material: a cuisine description, named chef, reservation policy, and crawlable menu. That can improve retrieval, but the source-selection result still depends on the engine and the wider evidence available.

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.

Frequently Asked Questions

What is AEO and why do Calgary restaurants need it?

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.

What dining queries are people asking AI engines?

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.

How do AI engines decide which Calgary restaurants to recommend?

AI systems use changing retrieval and source-selection methods. A restaurant can make its public information easier to verify with crawlable menu and location pages, accurate Restaurant JSON-LD, named chef or author details, and consistent third-party mentions. llms.txt is optional. FAQPage schema can describe visible questions and answers, but it is not a ranking or citation lever.

What is llms.txt and why does my restaurant need one?

llms.txt is an optional Markdown discovery file at yourrestaurant.com/llms.txt. It can summarize important public pages for compatible tools. Support is incomplete, Google does not use it, and the file does not replace a sitemap, control crawler access, or guarantee citations.

How long does an AEO setup take for a restaurant?

A complete setup for a single-location restaurant usually involves focused copywriting and structured-data work. Make the story, menu, and location pages crawlable, add accurate JSON-LD, and check retrieval access. llms.txt is optional. Scope depends on the current site, not a universal hour or word count.

Will AEO replace SEO for my restaurant?

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.

Where to Start

From there, improve named chef or author information and add FAQPage schema only where visible questions and answers already exist. Those changes make the page easier to interpret, but they do not guarantee rankings or citations.

Restaurants that improve crawlability, structured data, authorship, and source quality give retrieval systems better material to work with. That still does not guarantee citations, so track a stable set of Calgary dining prompts over time. AI answers are one channel, not the whole plan, so pair this with the rest of your Calgary restaurant marketing.

Related: Restaurant website design, the menu is the website.