Your PDF menu is sending diners next door

It is 7.10 pm on the waterfront. A couple is comparing two restaurants on one phone, standing up, one bar of signal. The first website opens a PDF menu: the page starts downloading, the text arrives the size of a pinhead, and now they have to pinch, drag and hunt for the fish page. The second shows its dishes, its prices and two photographs straight away. They walk into the second one. The first did not lose on cooking.

Should I put my menu on my website as a PDF?

No. A PDF is a document built for printing, not for a six inch screen: it opens in a separate viewer, often downloads instead, and makes people zoom on every line. Your menu should be an ordinary web page, made of text, that reshapes itself to the width of a phone.

The image version costs even more. A menu exported as a JPG from a design tool is a wall of pixels: neither Google, nor a screen reader, nor an answer engine can read a single dish inside it.

What actually happens on your customer's phone

Three frictions stack up. The file is heavy, so the wait is added on top of the site's own loading time, and more than half of mobile visitors leave past three seconds. The document takes them off your site, so your booking button and your phone number vanish from the screen at the exact moment somebody is hungry. And the back button sometimes drops them on your homepage rather than back on the menu.

None of that happens with a menu page written in text. The booking bar stays pinned to the bottom of the screen for the whole read, and the diner books the table while they are still choosing a dish.

A menu as an image does not exist for Google

This is the part nobody sees, because it is invisible from the inside. Somebody searching for "lobster Grand Case" or "vegetarian restaurant Gustavia" is running a search on words. If your dishes are locked inside an image, your site does not contain those words and cannot answer.

A PDF sits in between: Google can read a text PDF, but it treats it as a standalone document, cut off from your site, with none of your links and none of your booking. You are feeding a file instead of feeding your page.

The menu that AI assistants can quote

For the past two years a share of visitors has stopped typing into Google altogether: they ask ChatGPT or Perplexity where to eat gluten free in Sint Maarten, or which restaurant serves local fish in Gustavia. These machines only see text, and they are not going to open a PDF as a favour to you. A menu in text, with the exact dish names, the allergens and the prices, is simply quotable. The rest is not. The full reasoning is in getting recommended by ChatGPT.

What a good online menu looks like

Not a stack of tabs. Tabs hide half your work behind a click nobody makes while standing in the street. We publish three or four signature dishes in photographs at the top, then the entire menu underneath, readable in one scroll like a paper menu, with a booking bar that stays in view. That is the structure we apply on a restaurant website, and it works as well for a beach bar as for a fine dining room.

And when prices change?

This is the argument that decides most restaurant owners. A PDF menu gets changed by whoever designed it, so it gets changed late, so it ends up lying to your customers about a price or a dish you pulled weeks ago. A text menu is corrected in two minutes, and the price on the website is the price at the table. What a restaurant page on this island needs to contain is set out in the ideal website for a Grand Case restaurant.

What you can measure

We never promise a first page on Google. Three numbers tell you whether your menu is working: time spent on the menu page, bookings opened from that page, and calls that come in with a question about one specific dish, which means people read before they picked up the phone. When those three rise together, your menu is selling.

Our website pricing is public, or get your quote within 24 hours.