Your restaurant menu is your best SEO asset. Most restaurants hide it in a PDF

Think about how people actually search for somewhere to eat. Not "restaurant". They search "truffle tagliatelle near me", "wood-fired pizza in the city centre", "gluten free pasta", "pre-theatre set menu", "halal steakhouse". These are specific, high-intent searches from people who are deciding right now.

Every one of those phrases is on your menu. And if your menu is a PDF, none of them exist.

Why the PDF is the problem

A PDF is a document, not a web page. Search engines can sometimes extract a little text from one, but they cannot treat each dish as content on a page, cannot associate it with your location, and cannot show it in results the way they show a page. An image menu is worse — it is a picture of words, and to a search engine it is just a picture.

Meanwhile your competitor has a page per menu section, each one loading instantly on a phone, each one a separate opportunity to be the result somebody taps.

What a menu built for search looks like

On the Covent Garden restaurant site we run, the menu is not one page. It is more than thirty. Pizza. Pasta. Risotto. Salads. Desserts. The kids' menu. The pre-theatre set menu, which matters enormously in a theatre district. Each is a real page with real text.

That is the same menu, the same dishes, and completely different visibility.

1. One page per menu section

Dish names, descriptions and prices as actual text. Write descriptions that a person would want to read, not just ingredient lists — this is also where the searchable language lives.

2. Menu schema markup

Structured data tells Google that this is a menu, that these are dishes, and that these are prices. It is how a restaurant becomes eligible for the richer displays in search results rather than a plain blue link.

3. Dietary tags made searchable

Vegan, vegetarian, halal, gluten free, dairy free. These are high-intent searches — somebody filtering for them has already decided to eat out and is choosing where. Very few restaurants optimise for them properly, which makes it unusually easy ground.

4. Photos that do not slow the page down

Food photography is the whole point, and it is also usually why restaurant sites are slow. A photo straight off a phone can be four megabytes. Twenty of those on one page and your site is unusable on mobile data — which is exactly how people browse restaurants. Resize, compress, serve modern formats, and give files real names rather than IMG_4417.

5. Keep the PDF as a download

Some people want the printed version, and that is fine. Offer it as a download. Just stop making it the only version.

The other three things restaurants get wrong

Opening hours that are not maintained

Whether you are open at the moment of a search affects whether you appear at all. Bank holidays, seasonal changes, an early close on Sunday — if the profile does not know, you vanish from the results at your busiest decision-making hour.

A booking link that opens a new tab and loses people

Every extra step costs you covers. If the booking widget is slow, or asks for information before showing availability, people leave. Test it yourself on a phone, on mobile data, at 8pm.

Reviews that stopped in 2023

Recency matters more than volume for restaurants. A place with a steady trickle of recent reviews looks alive; a place with a large pile of old ones looks like it has coasted. Ask on the bill, ask in the follow-up, never incentivise.

Where to start if you only do one thing

Take the three dishes you are best known for. Give each one a real paragraph of text on a real page, with a good photo and the price. Then check whether your opening hours are correct for the next two months.

That is an afternoon of work and it will do more than a month of posting on social media.