How to put your menu online without a PDF
Put the menu on a web page as ordinary text — sections as headings, each dish as a line with its price and description. Do not link to a PDF and do not upload a photograph of the printed menu. A text menu loads instantly on a phone, can be read by search engines and screen readers, and can be changed in a minute.
This one is written for Restaurants.
What actually goes wrong with a PDF menu?
On a phone it either downloads or opens in a separate viewer, and it arrives at page width, which means the text is unreadably small until the person pinches and drags. A search engine cannot reliably read the dishes inside it, so somebody searching for the thing you are known for does not find you. A screen reader usually cannot read it either, which excludes people and, in several countries, is a legal problem. It is typically two to six megabytes, against roughly fifteen kilobytes for the same menu as text. Changing one price means going back to whoever has the source file.
What does a menu-as-text look like?
How do you handle a menu that changes constantly?
Does a text menu help you get found?
Should you keep a PDF at all?
Questions people actually ask
- What about a photograph of the printed menu?
- It has all the problems of a PDF plus one more: it is usually even larger to download. If the image has no alt text, which is normal, the menu is invisible to search engines, screen readers and anyone on a slow connection.
- Can I use a menu widget from a delivery platform?
- You can embed one, but it puts your menu on somebody else’s infrastructure, usually loads slowly, and often carries their branding and their tracking. Your own menu page is faster and it stays yours.
- Do I need to mark up the menu with structured data?
- It is worth doing. Marking up the restaurant, its hours and its menu helps search engines display them correctly. It is not a substitute for the menu being real text — it is an addition to it.