Website design for restaurants

Restaurant sites fail in a specific, predictable way. The menu is a PDF. The reservation button sits below a full-screen video. The phone number is an image. The diner is standing on a street, hungry, and gives up. Fixing that is unglamorous, measurable work.

What we build in

None of it is exciting. All of it is measurable.

The six things a restaurant site needs

• Reservations as the most obvious action on every screen — not tucked under a hero video, and never more than one tap away.
• Menus your team edits in seconds — real text, current prices, seasonal changes published the day they happen. No PDFs, no reprints.
• Fast loads on mobile — where nearly every diner looks. Images budgeted, fonts subset, and content visible before the network settles.
• Private dining, events and press — the higher-value bookings, given pages that read like an invitation rather than a form.
• Multi-venue support for groups — per-venue pages, hours, menus and booking links, plus one place for press and careers.
• Rich results and accurate quoting — Restaurant, Menu and LocalBusiness markup, so search engines and AI assistants describe your hours, location and dishes correctly.

The PDF menu problem, quantified

A PDF menu is the most expensive shortcut in restaurant web design. It is unreadable on a phone, invisible to search engines, impossible for an AI assistant to quote, and it goes stale silently — the prices change and the file does not. Text menus cost slightly more to set up and then cost nothing to keep current.

If the menu is…

Format	Search can read it	AI can quote it	Readable on a phone	Updating a price
A PDF	No	No	Poorly	Re-export and reupload
An image	No	No	Poorly	Re-crop and reupload
Real text	Yes	Yes	Yes	Seconds, by your team

Groups, and why the second venue is easier

A dining group usually starts with one restaurant, then opens a second, and the website becomes a liability — three designs, four menu formats, five sets of opening hours. Building the first site with the group already in mind means the second and third venues become a configuration rather than a rebuild.

What success looks like

Fewer phone calls asking what time you open. Fewer replies to reservation emails. Menus that are current in the evening service rather than the following week. Private-dining enquiries arriving with the date, the party size and the occasion already stated.

Menus change. The site has to keep up

A restaurant menu is never finished. Something runs out, the season turns, a dish stops working, the price of one ingredient moves.

If updating the site means opening a PDF editor, exporting, uploading and hoping the cache clears, the site will be wrong most of the time. Wrong menus are not a small problem: they are the single most common complaint left in restaurant reviews about the website rather than the food.

We build the menu as structured content — courses, dishes, allergens, prices — editable from a phone in a couple of minutes, with the change visible immediately.

Allergens are a legal page, not a footnote

In the UK and across the EU, allergen information has to be available before the order is placed, not on request. A PDF at the bottom of the page is a common attempt at compliance and a poor one: it is unreadable on a phone, often out of date, and impossible to search.

The reliable structure is to attach allergens to each dish in the same place the dish is edited, so the two cannot drift apart. The visitor reading the menu sees the information inline, and the kitchen updates it once.

It is unglamorous work and it is the difference between a site that is compliant and one that merely looks it.

Reservations without the platform tax

Third-party reservation platforms solve a real problem and charge accordingly — per cover, per month, or both — while owning the guest relationship and the data.

For a single-site restaurant taking most bookings by phone anyway, a well-built direct form plus a confirmation email often beats the platform on both cost and guest experience.

Where the platform genuinely earns its fee — high volume, multiple sites, complex table management — we integrate it properly rather than replacing it: same photography, same type, no redirect that makes the guest feel handed off.