The menu on your website, not in a PDF

The menu on your website is often the most visited page a restaurant has. Guests open it to see what the food is like, whether there is something for everyone in their group, what it costs and whether the dish a friend recommended is still on. For many, it is the page that decides whether they book. Yet on a great many restaurant websites, the menu is a PDF: a copy of the printed menu, uploaded as a file and linked from a button.

PDF menus are understandable. The printed menu already exists, it looks exactly as the designer intended, and uploading it takes a minute. But a PDF is a document designed for paper, not a page designed for a screen. On a phone, it is slow to open, hard to read and awkward to navigate. For search engines, it is harder to understand than a web page. And it is easy to forget, so it drifts out of date while the printed menu changes.

This guide explains why the menu on your website should be a web page rather than a PDF, what a PDF costs on a phone and in search, what to publish instead, how a digital menu connects to the rest of the restaurant website, how it helps restaurant SEO, and how updating the menu becomes easier when the web menu comes from the same source as the rest. It ends with a practical path for moving from PDF to page.

Guests open the menu page with simple questions. What kind of dishes are these? Is there a vegetarian main? What does a starter cost? Is the dessert my friend mentioned still on? Can my child eat something here? They want answers quickly, usually on a phone, often while deciding between several venues.

A good menu page answers those questions at a glance: clear sections, readable dish names and descriptions, prices, and simple marks for dietary needs. It loads quickly, scrolls naturally and lets guests jump to the section they want. Then it makes it easy to book.

A PDF can contain all the same information, but it presents it in a way that makes the guest work harder to find it.

On a phone, a PDF menu usually opens as a full page shrunk to fit a small screen. The guest has to pinch and zoom to read it, then scroll sideways and back to follow each line. Multi-column layouts designed for a large printed card become a puzzle. Large files take time to download on a mobile connection, and some phones open PDFs in a separate viewer, taking the guest away from the website.

Each of these is a small friction, and together they are enough to make some guests give up and look at another venue. Guests rarely complain about a PDF menu; they simply leave.

A menu written as a web page avoids all of it. Text flows to fit the screen, sections can be tapped, and the booking button is always a scroll away.

Search engines can read some PDFs, but a menu written as part of a web page is usually much easier for them to understand. The dish names, descriptions and prices become part of the page's content, connected to the restaurant's name, location and other information. That helps search engines match the venue to searches for particular dishes or types of food.

A PDF is a separate file, often with little context, sometimes made from a scanned image with no readable text at all. A menu that exists only as an image is effectively invisible to search. For restaurant SEO, the menu as text is one of the simplest improvements a venue can make.

Our guide to restaurant SEO covers the other factors that matter.

PDF menus also drift out of date. Updating one means editing the design file, exporting a new PDF and uploading it again, a job that is easy to postpone. Meanwhile, the printed menu changes, prices rise, dishes are added and removed, and the website shows something different.

Guests who order a dish from the website menu and find it is no longer served, or see a price that does not match the bill, lose trust. Our guide to updating the menu in one place, not five covers why every copy of the menu should come from one source.

Instead of a PDF, publish the menu as a web page: text, organised into sections, with dish names, short descriptions, prices and dietary marks. It can still look beautiful, in the venue's fonts and colours, with photographs of key dishes. The difference is that it is built for the screen rather than copied from paper.

Organise it the way guests read: starters, mains, sides, desserts, drinks, or whatever sections suit the venue. Put section links at the top so guests can jump straight to what they want. Keep descriptions short; a phone screen is small.

If you have several menus, such as lunch, dinner, brunch and drinks, put them on one page with clear sections, or on separate pages linked from one menu page.

Descriptions written for a printed menu are not always right for a screen. On a phone, long descriptions push the next dish out of sight, and guests scrolling quickly read only the first few words. Lead with what matters: the main ingredients and how the dish is cooked, in a short line. "Grilled sea bream, fennel, blood orange, brown butter" works better than a paragraph about the fish's journey to the kitchen.

Keep names consistent with the printed menu and the till, so guests who order what they saw online receive exactly that dish. Explain any unfamiliar terms briefly, so guests from elsewhere understand what they are choosing.

Many venues serve different menus at different times: breakfast, lunch, dinner, brunch at weekends, a bar menu in the afternoon. A single PDF often tries to hold them all, or the website shows only the dinner menu and guests assume that is all there is.

Show each menu clearly, with the times it is served. Section links at the top of the menu page, such as "Lunch", "Dinner" and "Weekend brunch", let guests jump to the one they need. If a menu is only available on certain days, say so beside it, so nobody arrives for brunch on a Tuesday.

The drinks list is part of the menu, and guests look at it too: the wine list before a special dinner, the cocktails before a night out, the non-alcoholic options for guests who do not drink. Publish it in the same way as the food menu, as text, organised into clear sections.

A long wine list can be shortened online to the highlights, with a note that the full list is available at the table, or organised by style so guests can scan it easily. Keep prices current, because guests who choose a bottle online expect to find it at that price.

Show prices clearly beside each dish, in the same format as the printed menu. Check how prices must be shown where you trade; in many places, the price shown to consumers must include sales tax or VAT, so the price on the website is the price guests pay.

Avoid surprises. If the venue has a minimum spend for groups or a set price for certain nights, say so on the menu page or the booking page, not only at the table.

Guests planning a group dinner or an event often look for a set menu before they enquire. A clear group or event menu on the website, with prices per guest and what is included, saves the organiser time and makes it easier to choose the venue.

Link it from the menu page and the private dining page, and make the enquiry or booking step obvious. Organisers often share the link with their guests, so a clear, readable page also reaches people who have never visited.

In cities with many visitors, a guest reading the menu may not be reading in their first language. Short, clear descriptions, photographs of key dishes and simple dietary marks help them understand the menu. Our guide to menu design covers how to write descriptions that work for every guest.

A menu page should be one of the fastest pages on the site, because guests open it when they are deciding. Keep it light: text for the menu itself, a handful of optimised photographs, and no autoplaying video or heavy animations. Test it on a phone on a mobile connection and time how long it takes before the first dish is readable.

If the menu is long, consider loading sections as the guest reaches them, or splitting very long menus into separate pages. A fast, simple menu page often persuades more guests than a slow, elaborate one, however beautiful the design.

A menu on your website is a good place to show dietary information: vegetarian, vegan, gluten free, contains nuts. Use a small set of consistent marks, explained once, so guests with dietary needs can see at a glance what suits them.

Allergen information needs care. Show what you can accurately, and make it clear how guests can get full allergen information and that they should tell the team about allergies when they book and at the table. Keep the information correct when recipes change. Our guide to building an allergen matrix that stays correct covers the record behind it.

Photographs can help guests understand dishes, especially unfamiliar ones. Add them for signature and seasonal dishes, rather than every item, so the page stays fast and focused. Keep them honest: a photograph should look like the dish guests will receive.

Optimise every image so it loads quickly on a phone. Large photographs are a common cause of slow menu pages.

A digital menu, a live menu kept in one system and shown on the website, can do more than a static page. It can show dishes that have sold out, update prices the moment they change, filter dishes by dietary needs, and stay in step with the menu guests see at the table through a QR code.

For venues that also use a QR code menu in the dining room, the same digital menu can serve the website. That means one menu, updated once, shown everywhere. Our guide to the QR code menu five years on covers what has worked for venues that use them.

Structured data is a way of labelling information on a web page so search engines can read it reliably. For restaurants, it can describe the venue's name, address, hours, cuisine and menu. The vocabulary for this is published at schema.org, which includes properties for a restaurant's menu and cuisine.

Structured data is not required for a menu to be found, and it is not a shortcut to the top of search results. But it can help search engines understand the page, and it is worth adding if your website platform makes it easy.

The menu page is often where guests decide to book, so make the next step obvious. Put a booking button at the top and bottom of the menu page, and keep it visible as guests scroll on a phone. A guest who has just found a dish they want should be able to book in a few taps.

Link to the menu from the home page, the booking page and your listings, so guests can find it from wherever they start.

Many guests see the menu on the venue's Google Business Profile or social profiles before visiting the website. Link those listings to the menu page on your website, rather than to a PDF, so guests get the same clear, current menu wherever they look.

Our guide to your Google Business Profile covers how to add the menu to the listing.

With the menu as a web page, updating the menu becomes a matter of editing text rather than redesigning and re-exporting a file. Make one person responsible for it, and update it whenever dishes or prices change, ideally from the same source as the printed menu and the till.

Check it monthly against the printed menu. A five-minute comparison catches differences before guests do.

None of this means abandoning the printed menu. A beautifully designed printed menu remains part of the experience at the table, and some guests prefer to read one. The point is that the website should not simply reproduce it as a PDF.

If you want guests to be able to download or print the menu, offer a PDF as an extra, alongside the web page, not instead of it.

Moving from a PDF to a web menu is straightforward:

Most venues can do it in an afternoon.

Here is an illustrative venue that replaced its PDF menu. The details are examples.

In servearound, the digital menu is a live web page rather than a PDF, opened in the guest's browser with nothing to download, with sections, photographs, dietary and allergen filters and dishes marked sold out the moment they run out. It is the same menu guests see at the table through a QR code, read from one library of dishes, so a price changed once is right everywhere.

When a venue publishes it, its menu page can be found by search engines, and it can be linked from your website, your Google listing and your social profiles. See the menus module and Campaigns.

It works, but it is slower and harder to read on a phone, harder for search engines to understand and easier to leave out of date.

Some can, but a menu written as part of a web page is usually much easier for them to understand.

No. Keep it for the table. Just do not use it as the website's menu.

No. Photographs of a few signature and seasonal dishes keep the page fast and focused.

Whenever dishes or prices change, and check it against the printed menu monthly.

Yes, if both come from the same digital menu, which keeps them in step.

Yes. Guests want to know what to expect before they book, and a menu with prices helps them choose with confidence.

Show them if they change predictably, such as a weekly special, and keep them current. Daily specials that change every night are often better left to the table and to social media.

Yes, for most venues. The printed menu is part of the experience at the table; the website menu helps guests decide before they arrive. Both should come from the same source, so a guest who chose a dish online finds it, at the same price, when they sit down.

The menu on your website should be a web page, not a PDF. PDFs are slow and awkward on a phone, harder for search engines to read, and easy to leave out of date. A menu written as text, in clear sections with prices, short descriptions and dietary marks, is faster for guests, better for restaurant SEO and easier to keep current.

Add a few honest photographs, connect the menu to booking with buttons at the top and bottom, link to it from your listings, and consider a digital menu that serves the website and the table from one source. Make updating the menu part of every change, and keep the printed menu for the table.