Menu Pages Google and AI Can Actually Read

**Publish your menu as real text on a web page, not as a PDF, an image, or a design file. A menu that can't be read as text is invisible to search engines and to AI assistants — which means when someone asks whether you have gluten-free options or what a dish costs, nothing can answer.**

This is the most common and most consequential website mistake restaurants make. It's also among the easiest to fix.

Why Is a PDF or Image Menu a Problem?

**Search engines can't index it usefully.** A menu as an image contains no text a crawler can read. A PDF is somewhat better but is treated as a separate document, ranks poorly, and provides a bad mobile experience.

**AI assistants can't quote it.** When someone asks an assistant "does [restaurant] have vegetarian options" or "what's on the menu at [restaurant]," the system retrieves text from web pages. If your menu is a picture, there's no text to retrieve. It either says it doesn't know, or — worse — pulls outdated information from a third-party site.

**Customers hate it on phones.** A PDF opens in a separate viewer, requires pinch-zooming, and is one of the more reliable ways to lose someone deciding where to eat. Most people looking up a menu are on a phone, often standing outside.

**Screen readers can't read it.** An accessibility problem as well as a search one.

What Should a Menu Page Look Like?

**Real HTML text on a page on your own domain.** Not embedded, not linked out, not an image.

**One page, or a page per menu.** If you have distinct lunch, dinner, brunch, and drinks menus, separate pages work well — each can rank for its own searches, and "brunch [neighborhood]" is a search worth having a page for.

**Proper heading structure.** Section names — Starters, Mains, Desserts — as real headings, not bolded paragraph text.

**Each item with a name, a description, and a price.** The description is where the search value lives. "Grilled cheese" ranks for nothing. "Grilled cheese — aged white cheddar and gruyère on sourdough from [bakery], with tomato soup" contains ingredients, technique, and a local supplier reference, all of which are things people search and ask about.

**Dietary information marked clearly.** Vegetarian, vegan, gluten-free. These are among the highest-intent searches in the category and among the most common questions asked of AI assistants about restaurants.

**Current prices.** If prices change often, that's an argument for making the page easy to edit, not for omitting them. Menus without prices are a known frustration and people leave.

Does This Really Affect AI Answers?

Directly, and it's easy to test.

Ask ChatGPT or Perplexity what's on the menu at your restaurant, whether you have gluten-free options, and what a main course costs. Then ask where it got the information.

If your menu is an image or PDF, one of three things happens: the assistant says it doesn't have that information, it pulls from a delivery platform or review site with an outdated version of your menu, or it guesses from your restaurant's category.

All three are bad. The third is the worst, because a confident wrong answer sends someone to you expecting something you don't serve.

A menu published as readable text on your own site is the authoritative source, and it's the one these systems will prefer when it exists.

What Structured Data Should You Add?

Schema markup helps machines understand what they're reading.

**Restaurant schema** on your main pages, including your address, phone, hours, price range, and cuisine type.

**Menu schema** — Schema.org supports Menu, MenuSection, and MenuItem types, letting you mark up sections and individual items with names, descriptions, and prices.

**FAQPage schema** for your common questions — reservations, parking, dietary options, private events.

This isn't a substitute for readable text; it's a layer on top of it. Text first, markup second.

What About Delivery Platform Menus?

Delivery platforms usually have your menu, often with prices marked up and items missing.

Two problems. First, if that's the only readable version of your menu online, it becomes the source AI assistants and search engines use — with the wrong prices. Second, you don't control when it's updated.

Your own site should hold the authoritative menu. Delivery platforms are a sales channel, not your menu of record.

What Else Belongs on the Menu Page?

Since it's likely one of your most-visited pages, it should do more than list food.

- **Hours**, or a clear link to them

- **Reservation or ordering action**, prominent

- **Address and a map link**

- **A note on parking**, which in most Seattle neighborhoods is a real question

- **Whether you take walk-ins**

- **Allergen note** and how to ask about substitutions

- **Last updated date**, which signals to both readers and machines that the page is current

How Do You Keep It Current?

The reason restaurants use PDFs is usually that the designer made the menu in a design tool and the PDF is what exists. That's a workflow problem, not a technical one.

**Make the web menu the working version.** Update the page when the menu changes, and generate the printed version from that, rather than the reverse.

**Choose a platform you can edit yourself.** If updating a price requires emailing a developer, the menu will go stale. Any modern website platform makes this a two-minute job.

**Put a date on it.** "Menu updated [date]" builds trust and signals freshness.

**Seasonal menus are content.** Every change is a reason for a post, a Google Business Profile update, and a fresh signal that the site is maintained.

Key Takeaways

- A PDF or image menu is invisible to search engines and AI assistants, and frustrating on a phone.

- Item descriptions carry the search value — ingredients, technique, and local suppliers are what people search and ask about.

- Mark dietary options clearly; they're among the highest-intent restaurant searches.

- Make the web menu the working version and generate the print version from it, not the other way round.

Frequently Asked Questions

Should a restaurant menu be a PDF on the website?

No. PDFs can't be indexed usefully, provide a poor mobile experience, and can't be read by AI assistants answering questions about your menu. Publish the menu as real text on a web page and generate any printed version from that.

### Why doesn't ChatGPT know what's on my restaurant's menu?

Most likely because your menu is published as an image or PDF, which contains no text for the system to retrieve. It will then either say it doesn't know or pull an outdated version from a delivery platform or review site. Publishing the menu as readable text on your own site fixes this.

Should restaurant menus show prices online?

Yes. Menus without prices are a well-documented source of customer frustration and cause people to leave for a competitor whose prices are visible. If prices change often, that's a reason to make the page easy to edit, not a reason to omit them.

What schema markup should a restaurant use?

Restaurant schema on the main pages with address, phone, hours, price range, and cuisine, Menu, MenuSection, and MenuItem schema on the menu page, and FAQPage schema for common questions about reservations, parking, and dietary options. Markup supplements readable text rather than replacing it.

Is Your Menu Invisible?

Watt Consulting rebuilds restaurant menu pages as readable, marked-up text — and will test what AI says about yours first. Start your project.