The menu is usually the most important content on a restaurant website. Treat it like a product interface: quick to scan, accurate, and useful under pressure.
Use HTML as the primary menu
Put menu sections, dish names, descriptions, prices, and notes in actual page text. A downloadable PDF may remain as a secondary option for printing, but it should not be the only path. HTML adapts to phone screens, supports screen readers, and is easier for search and AI systems to interpret.
Design for the six-second scan
Most visitors look for three things immediately: the style of food, the likely price, and whether their party can eat there. Use familiar section headings, consistent price placement, short descriptions, and generous spacing. Avoid carousels for menu sections.
Keep dietary language precise
Use clear labels such as vegetarian or vegan only when the kitchen can support the claim. Explain whether “gluten-friendly” differs from a gluten-free preparation environment. Always direct allergy questions to staff; a symbol is not a food-safety guarantee.
Separate service periods when they truly differ
If brunch, lunch, dinner, bar, and happy-hour menus have different hours or offerings, give each a clear section or URL. State when each menu is served. Do not make diners infer that the dinner menu is available at noon.
Make updates boring and reliable
Choose one source of truth and assign an owner. Date seasonal or special menus when useful. Remove unavailable items rather than stacking disclaimers. After every update, check the menu link from the home page, Google Business Profile, and reservation service.
Add structured menu information carefully
Schema.org supports Menu, MenuSection, MenuItem, Offer, price, price currency, and dietary suitability. Structured data should mirror the visible menu. Do not mark up items or prices that a customer cannot see on the page.
Menu page checklist
- Loads without a download
- Readable at 375 pixels wide
- Logical heading order and section names
- Dish descriptions are concise and specific
- Prices use one consistent format
- Service hours are visible
- Dietary labels include appropriate caveats
- Reservation and ordering actions are nearby but not intrusive
- PDF, if offered, is secondary and accessible
- Structured data matches the rendered menu
For the available vocabulary, review the official Schema.org Menu type and its MenuSection and MenuItem properties.