How to put your restaurant menu online so guests and search can read it
Publish your menu as text on your own website, one page per menu, with dish names, short descriptions, prices and the dietary labels your kitchen confirms. Link that page from your Business Profile and ordering pages. A photo of a printed menu or a PDF is harder to read on a phone and harder for software to quote accurately.
By DeepRestaurant · Updated · 3 sources
Why the online menu matters
The menu is the page guests check first. In TouchBistro’s 2024 survey of more than 1,500 U.S. diners, 85% said they look at the menu online before choosing a new restaurant. If it’s hard to read, out of date or missing prices, that first look can end the visit.
Photo, PDF or web page
The same menu behaves very differently depending on how it’s posted.
| Photo of the menu | Web page | ||
|---|---|---|---|
| On a phone | Pinch and zoom, glare, small type | Opens as a separate file, often small type | Fits the screen |
| For search and AI | Text is inside an image | A separate document, apart from your page | Real text on your page |
| Updating a price | Shoot a new photo | Edit, export and upload again | Change one field |
| Next step | Nothing to tap | Usually nothing to tap | Order and reserve buttons beside the menu |
What to include
A complete web menu answers the questions guests would otherwise call about:
- Which menu it is and when it’s served: lunch, dinner, brunch, happy hour.
- Sections in the order guests read them.
- Dish names with a short, plain description.
- Prices, or a clear note where prices vary.
- Dietary labels only where the kitchen has confirmed them.
- A note asking guests with allergies to speak with staff.
- The date the menu was last updated.
- Order and reservation buttons next to the menu.
Dietary and allergy labels
Labels such as vegetarian or gluten-free help guests decide, but only if they’re right. Apply them only where your kitchen confirms them, and direct allergy questions to staff rather than to a label. Software that reads your menu will repeat what it says, so accuracy matters twice.
Structured data for menus
Schema.org defines Menu, MenuSection and MenuItem types, and a hasMenu property on restaurants. Marking up your menu pages tells software which text is a dish, which is a description and which is a price. It supports a clear text menu; it doesn’t replace one.
One menu, kept current everywhere
Keep a single source for each menu and point everything else at it: your Business Profile’s menu link, your ordering pages and your social profiles. When a dish or price changes, update that one page first. You can see the difference on a fictional menu in our side-by-side demonstration.
Questions owners ask
Is a PDF menu bad for SEO?
Search engines can read many PDFs, but a PDF sits apart from your page, is awkward on a phone and has no booking or ordering buttons beside it. A web menu does the same job better for guests and for software.
Should prices be on the online menu?
Yes, where you can. Guests use prices to decide, and a menu without them sends people to call or to a third-party listing. If prices vary by location, publish a menu page per location.
Do we need separate pages for lunch and dinner?
If the dishes or prices differ, yes. One page per menu keeps each one readable and lets you link to exactly the menu a guest needs.
Sources
- TouchBistro 2024 American Diner Trends Report (1,500+ U.S. diners), as reported by FSR Magazine · FSR Magazine · 2024-03-26
- Menu, MenuSection and MenuItem types · Schema.org · checked 2026-10-22
- Restaurant (FoodEstablishment) type: hasMenu, servesCuisine, acceptsReservations · Schema.org · checked 2026-10-22