Your PDF menu is costing you covers
The menu is the single most looked at thing on a restaurant website, and putting it in a PDF makes it unreadable to phones, search engines and AI assistants at the same time.
Why is a PDF menu bad for a restaurant website?
It forces a download, opens in a separate viewer, requires pinching and zooming on a phone, and is poorly indexed by search engines. An AI assistant asked what you serve usually cannot read it at all.
Most people looking at your menu are standing outside somewhere deciding where to eat, on a phone, with one hand. Every extra tap loses some of them.
There is also a practical cost inside the restaurant: a PDF is usually updated by whoever has the original file, so prices drift out of date because changing them is somebody else's job.
What should a restaurant menu be instead?
A normal web page with the dishes as text, grouped by course, with prices. Structured data behind it so search engines and assistants can read the items and prices directly.
Keep the PDF as a printable extra if you want one. The page is what people and machines read; the PDF is for whoever wants to print it.
Will an AI assistant recommend my restaurant?
Only if it can read what you serve, where you are and when you are open. That means text on a page rather than an image or a PDF, and consistent details across your website and listings.
The quickest check is to ask an assistant what your restaurant serves and see what comes back. Whatever it says is roughly what a growing share of prospective customers are being told.
Also asked
- What about menus that change daily?
- Publish the fixed structure and mark the changing sections clearly, with a note about how often they change. A daily menu that is a week old does more harm than a page saying the specials change daily and listing the last confirmed set.
If this is your trade
Restaurants and hospitality →