Why a PDF menu quietly costs your restaurant bookings

It is half past nine on a Tuesday and someone is on the sofa planning Friday night. They have three restaurants open in tabs on their phone and they are doing the thing everyone does: reading the menus. Whichever menu is easiest to read has just gained an advantage that has nothing to do with the food.

If your menu is a PDF, this is the moment it costs you. Not with a complaint. Just with a quiet switch to the next tab.

What a PDF menu is like on a phone

A PDF is a print format. It exists to make an A4 page look identical everywhere, which is exactly what makes it wrong for a screen the size of a playing card.

First it has to load, and menus exported straight from design software are often heavy files that crawl on mobile data. Then it opens, sometimes in a separate viewer that takes the visitor out of your website altogether. What appears is a full sheet of A4 shrunk to fit, with type far too small to read. So begins the ritual: pinch, zoom, drag left, drag right, lose your place, zoom back out and start again.

Some people push through it. Plenty do not, and the ones who give up never tell you. They simply book the place whose menu they could actually read.

What search engines and AI assistants make of it

Search engines can read the text in some PDFs, but a menu locked inside one is still second best. A PDF ranks as a standalone file, so someone searching for a dish can land in a bare document viewer with no booking button, no opening hours and no way back to your site. And if the menu was scanned or saved as an image, which is common, there is no text in it at all. To a machine, it is a photograph.

The same goes for AI assistants. When someone asks ChatGPT or a similar tool where to get a good vegetarian Sunday roast nearby, those tools work from web pages they can parse. A menu written as real text on a real page hands them your dishes, your prices and your descriptions. A menu trapped in a PDF gives them very little, and a photographed one gives them nothing. Your food never enters the conversation.

Phone-only booking has the same problem

Now suppose the menu wins them over, and the only way to book is to ring. It is half nine at night. You are closed, or you are mid service with nobody free to answer. So they have to remember to call tomorrow, during hours when they are busy at work themselves.

Every extra step loses a share of the people willing to take it. Some will ring. Others drift to the restaurant where booking took thirty seconds on the phone they were already holding. Phone-only booking does not feel like a leak from inside the building, because the phone still rings. You just never hear from the people it turned away.

What actually changes when you fix it

A menu built as a proper page on your website loads in a moment, reads comfortably one handed and never needs zooming. When a dish changes or a price moves, you update a line rather than re-exporting a document, so the menu online is the menu on the table. Search engines and AI assistants can read every word. And the whole thing lives inside your site, one tap from the booking button and your opening hours. This is how we build every one of our websites for restaurants and cafés.

The booking route does not need to be elaborate either. A proper booking system is ideal, but even a short form that says "request a table and we will confirm by text" works while you are asleep. The point is simple: a decision made at half nine on a Tuesday can become a booking at half nine on a Tuesday, instead of a phone call that may never happen.

Keep the PDF for print

None of this means throwing the PDF away. It is still the right format for the printed menu on the counter and the laminated one by the door. It is just the wrong thing to hand to someone on a phone. Your website is not a filing cabinet; it is your front of house for people who have not walked in yet.