Field guide: the menu as a phone sees it, on 180 restaurant websites

See the full reportDownload the PDF

Take any independent restaurant's website, open it on your phone and tap Menu. You land on one of five things: a page of dishes you can read and scroll, a PDF, a photo of the printed menu, an ordering app, or nothing at all. Only the first one is a menu to everybody who asks for it.

The State of Independent Restaurant Websites 2026 read 180 independent restaurant, café and bar websites the way a diner does. On the question every diner asks first after "are you open", the count is plain: only 49% put the menu up as real text a phone can read. 51% serve a PDF, a photo, an app page, or no menu we could find.

This guide walks the counter with you: what the scan counted, what each kind of menu looks like from the phone and from a search engine, and how to check a prospect's site before you call.

What did the scan count as a menu?#

We fetched each home page as a server sends it, followed the link marked Menu (or Food, Dinner, Eats, Tap list and the like), and read what came back. A menu passes when the page carries at least eight short lines that read as dishes or drinks, or five dishes with five prices. If the menu page didn't have them, we tried one menu it links to, then the home page.

Anything else fails, and the evidence records which kind of fail it was: a PDF link, a page that is mostly images, a link out to an ordering or delivery app, or no menu at all.

Two limits to keep straight. The scan reads the page the server delivers, so a menu that only appears after scripts run counts as missing; a search engine on a slow pass and an older phone on a weak signal meet the same gap. And it says nothing about the food. It reads what a site shows, never how good the cooking is.

The five menus you'll meet#

Text on a page. Dishes as words in the page itself. It reflows to the width of the phone, the type size follows the reader's settings, a screen reader reads it top to bottom, and a search engine can index every dish. Someone searching for a dish near them can land on this page.

A PDF. It opens in a viewer or downloads, at the size it was laid out for paper. The diner pinches and drags around a two-column page. Search engines can read some PDFs, but the file sits outside the site's pages, often with an old file name. Screen readers depend on how the file was exported.

A photo of the menu. A picture of words. Nothing in it can be selected, searched, translated or read aloud unless someone wrote it out in the alt text. WCAG 1.4.5 asks for text, not images of text, for exactly this reason.

An app page. The menu lives on an ordering or delivery service. It may read fine there, but it sits on someone else's site, so the restaurant's own page has no menu of its own.

Nothing. No menu link we could follow, or a menu page with too little on it to read as one. To a diner, that is a closed kitchen.

Why the menu decides the next two answers#

A text menu isn't the only fix, but it is the one the rest of the menu work stands on.

Prices. Only 34% of the sites show prices beside dishes. Our rule reads prices from a text menu, five or more next to dishes, so a PDF with prices on it doesn't count here. That is deliberate: a diner checking what dinner will cost on a phone wants it on the page, and so does a search engine.

Allergens and diets. 29% of the sites mark allergens or vegetarian, vegan and gluten-free dishes. That is the least-answered of the eight diner questions in the study, and the one the report leads with. The marks have to be readable to count, which means text: a GF in a PDF or a photo can't be searched, filtered or read aloud.

And one technical check rides along. Only 16% of the sites carry restaurant, café or bar structured data, the markup that tells search engines the address, the hours and where the menu is. A menu page with a stable address is the thing that markup points to.

Which kinds of place are furthest behind?#

The four groups in the study, on the three menu questions:

Casual and family places lead on all three. Chef-driven rooms put their menu up as text more often than not, but mark diets on only 23%, which is the gap to raise with a tasting-menu kitchen that handles requests every night. Cafés and bars trail on the menu itself, and on prices with it: fewer than three in ten show prices beside dishes.

What does a phone-ready menu look like?#

Short sections, one dish to a line, a description and a price beside it, and a legend near the top that a diner meets before the first course. The legend is the cheapest win on the page. Here is one an agency can hand over as written:

Then one line under the menu title, so the owner has a reason to keep it current:

The PDF can stay, as that download. It just stops being the menu.

How do you check a prospect's menu in two minutes?#

1. On your phone, tap Menu. Note which of the five you get.
2. Try to select a dish name. If you can't, it isn't text.
3. Look for a price and a GF or V. Both should sit beside the dish, on the page.
4. Search the restaurant's name with one signature dish. If only a PDF or an app page comes up, the site's own pages aren't carrying the menu.

Write down what you found in the owner's words: "Your menu is a photo." That sentence does more work in the first conversation than any score.

For the conversation itself, our audit recording script turns these checks into a five-minute screen video for the owner. Prices are the conversation that follows the menu, and auto shops have the same gap; our talk track for repair shops shows how to ask an owner for numbers they already give at the counter. The full numbers, by kind of place, are in the report.

Go to the findingsGet the data