The menu is the most visited page of any restaurant website, usually by a wide margin. According to a survey of 1,101 adults by the US agency MGH (2019), 77 percent of guests look at a restaurant’s website before they dine or order – and 68 percent have skipped a restaurant at least once because of its website. People searching for a place to eat want to know what it costs and whether everyone at the table will find something, before they book. Yet many websites treat the menu as an afterthought: a scanned PDF, three years old, readable on a phone only by zooming and swiping. A good online menu is not a design problem. It is craft, with a handful of clear rules.

Rule one: no PDF

The PDF is convenient for the owner and an imposition on the guest. On a phone, they have to download the document, zoom in, and swipe sideways across the page. Many give up first. In the MGH survey mentioned above (2019), 30 percent of respondents named a hard-to-read menu as a reason to stay away from a restaurant – level with a website that looks outdated. On top of that, Google can read PDF content but weights it lower than regular page content. Someone searching for “schnitzel Vienna 7th district” is more likely to find the restaurant whose menu exists as a proper web page.

So the menu belongs on the website as an HTML page: text that adapts to the screen width, with jump links to starters, mains, desserts, and drinks. It sounds mundane, but it is the single biggest lever. If you change only one thing about your website today, change this.

Why guests stay away after seeing a restaurant’s website

Website hard to navigate33%

Menu hard to read30%

Website looks outdated30%

Source: MGH survey of 1,101 US adults, 2019

The order: guide the eye

Nobody reads an online menu front to back. Guests scan. So the top of the page belongs to whatever your restaurant is known for: the goulash, the seafood platter, the handmade pasta. If your signature dish first appears at position fourteen under “Mains”, you are hiding your best salesperson.

Within the categories, the classic sequence works: starters, soups, mains, desserts, drinks. But group generously. Twelve mains in one block wear the reader out; three groups like “From the grill”, “From the pan”, and “Vegetarian” make the same menu easy to scan. And a clearly visible vegetarian or vegan group is not ideology, it is service: in almost every larger group, one person decides based on exactly that.

Prices: show them, and make them readable

Some restaurants leave prices off the website, worried about scaring guests away. The opposite happens: whoever finds no prices assumes high ones and books elsewhere. A menu without prices fails to answer the guest’s most important question.

For layout, we advise against the dotted leader line that drags the eye across the page from dish to number. Better to place the price quietly right next to the dish. The consultants’ favourite tip of dropping the euro sign is yours to take or leave; what matters more is that the prices are correct. A guest who read €16.90 online and pays €19.50 at the table does not come back, and that is exactly why keeping the online menu current is not optional polish.

Descriptions: ingredients, not adjectives

A good description is one or two lines and names what is on the plate: “Rump steak with fried potatoes and crispy onions” says everything. “An unforgettable taste experience from our kitchen” says nothing. Provenance is welcome when it is true and means something: the beef from the Waldviertel, the alpine cheese from the Bregenzerwald. Once every second dish is “homemade”, nobody believes it by the third one.

For the classics: do not explain what everyone knows. A Wiener schnitzel needs no description, at most a note whether it is veal or pork, and that belongs in the name.

Allergens: required, but keep them quiet

In Austria, the 14 main allergens must be declared, usually via letter codes from A for gluten to R for molluscs. Online you have better options than on paper: the codes can sit small and grey after each dish, with a legend at the bottom of the page, without disfiguring the menu.

What matters is that they stay in sync. If the kitchen changes a recipe and the sauce suddenly contains cream, the code for milk has to appear online too. That is a strong argument for a system where the kitchen or service team can edit the menu themselves instead of emailing an agency.

Photos: few, but real ones

Food photos cut both ways. According to the MGH survey (2019), 45 percent of guests specifically look for photos of the dishes on restaurant websites. So good photos sell, but bad ones repel, and most phone photos taken under artificial light are bad ones. Our honest recommendation: better no pictures in the menu than dark, yellow-tinted ones. If you use photos, use a few, professionally shot, of the dishes you actually want to sell. Stock photos are off limits; the guest notices at the table at the latest, and then the trust is gone.

Current beats perfect

The most beautiful menu is worthless if it is out of date. Seasonal changes, new prices, the dish that no longer exists: all of it has to be editable online in minutes, or it simply will not happen. In practice, this is precisely where PDF menus and agency websites with ticket systems fail most often.

With GuestMaker, the digital menu is part of the package: you change dishes, prices, and allergens yourself in the dashboard, and the change is live immediately. Even on a Sunday evening, when you remember the autumn menu starts tomorrow.