Morphos / Journal
Your menu should not be a PDF
It is the most common shortcut in restaurant web design, and the most expensive one over a year.
A PDF menu looks like a saving. It is a file the restaurant already has, and uploading it takes a minute. What it costs is less visible: every diner who cannot read it, every search engine that cannot index it, and every AI assistant that cannot quote it when somebody asks what you serve.
The same menu, four formats
| Format | Search can read it | AI can quote it | Phone readable | Changing a price |
|---|---|---|---|---|
| A PDF | No | No | Poorly — pinch and drag | Re-export, re-upload, hope |
| A photo of the menu | No | No | Poorly | Reshoot |
| Text inside an image | No | No | Poorly | Re-edit the image |
| Real text on the page | Yes | Yes | Yes | Seconds, by the team |
The doorway test
Open your site on a phone, standing up, one thumb, in poor light. Can you find tonight's menu and read it without zooming? If not, a meaningful share of your potential diners have already gone elsewhere — and they will not tell you, because they simply will not arrive.
What replacing it involves
Not a redesign. The menu becomes a structured block on the existing page: sections, dishes, prices, dietary notes. The team edits it in place. Structurally it is a morning's work, and it is the single highest-return change available to most restaurant websites.
One thing to get right
Use real headings and lists, not styled paragraphs. A menu that looks like text but is built from `
What to put in the menu's place
Replacing a PDF is the easy half. The harder question is what the page should do that the PDF could not.
Three things, in order of value. It should be searchable — somebody looking for a specific dish or a vegetarian option should find it on the page rather than scrolling an image. It should carry allergens inline, attached to the dish rather than in a footnote. And it should be structured so that a search engine understands the restaurant serves that food, at that price, in that place.
None of that requires a booking platform or a page builder. It requires the menu to be data rather than a document, which is a decision made once during the build.