The phone rings in every town you serve.
Why is our PDF menu costing us customers?
Because nobody can search it. Google can't read a PDF properly, phones make people pinch and zoom, and AI assistants can't quote a dish from it. A real menu page, one line per dish, is the single biggest change most restaurants can make to be found for what they actually serve.
A PDF menu feels like the reasonable choice: the designer made it, it matches the printed one, you upload it and you’re done. Then nothing happens, and you never find out why.
What the PDF is doing to you
Google can’t rank it for dishes. Someone searches “gluten free brunch Leslieville”. Your menu has three gluten-free brunch dishes. The competitor with a real menu page shows up; your PDF doesn’t, because search engines treat it as a document, not a page about your restaurant.
Phones hate it. It opens in a viewer, it’s the wrong size, people pinch and zoom and give up. Most of your menu views are on a phone, often from the street outside.
AI assistants skip it. “Where can I get a good vegan burger near King West?” is answered from menus the assistant can read. A PDF isn’t one of them.
It goes stale. Updating it means the designer, a new export, a re-upload. So the autumn menu stays up until February.
What to do instead
A real menu page: every dish a line of text with its description and price, grouped as you’d print it, filterable for the things people filter by (vegetarian, gluten free, kids). Marked up so Google and AI engines know each line is a menu item. Edited by your team in two minutes when a dish changes. The printed menu can still be generated from it, so there’s one source of truth.
What changes
You start appearing for dishes and dietary searches, not only your name. Phone visitors stay. And when someone asks an AI where to eat, your menu is one it can quote.