Restaurant website design that gets the table booked in three taps

Restaurant marketing is local search plus mobile speed plus the booking integration. Lose any of the three and the customer goes to the next result on Google Maps. The version that wins prioritises the menu and the booking over the design portfolio.

The restaurants clients I take on tend to fit one of these three shapes:

• Independent restaurants in central London, regional cities, or competitive food destinations
• Restaurant groups with 3-15 sites needing per-location pages plus a coherent brand layer
• Specialty venues (private dining, supper clubs, pop-ups) with seasonal menus and event-driven traffic

Mobile-first is non-negotiable

Most restaurant searches happen on a phone. The desktop site is the secondary experience. The menu has to load on a 4G phone in under 2 seconds; the booking has to work in three taps. Most restaurant sites fail one or both of those.

OpenTable, Resy, SevenRooms integration

If the restaurant uses a booking platform, and most credible ones do, the integration is the conversion engine. Either embed the booking widget without breaking the rest of the page (most do this badly), or deep-link to the booking platform with proper UTM tracking.

Menu architecture

PDF menus are a search-engine and accessibility disaster. Real HTML menus with proper schema markup (`Menu`, `MenuSection`, `MenuItem`) feed the rich result, work on assistive tech, and load in milliseconds. Most restaurant sites are still on PDF in 2026.

1. A page for every location Address, phone, opening hours by day, directions, the menu for that site and a booking button, with matching Restaurant schema. Dishoom, Hawksmoor and sweetgreen all do this. It is what ranks for '[area] restaurant' and 'near me' searches.
2. Menus in HTML, not only PDF Dishes and prices as real text on the page, marked up with Menu, MenuSection and MenuItem schema. A PDF can sit alongside as a printable copy, the way Rules does. It should never be the only version.
3. Booking one tap from anywhere A booking button in the header and on every location page, linked to the platform you already use (SevenRooms, OpenTable, Resy) with the location passed through. Or the booking form can be built into the page itself.
4. Hours that match reality Opening hours, kitchen hours and holiday closures live in one place in the CMS. They show on the site, in the schema and on the Google Business Profile, so a guest never turns up to a closed kitchen.
5. Allergens and dietary labels Vegan, vegetarian and allergen information sits on the menu itself, not in a separate document. It saves the guest a phone call, and it answers the searches that start with a dietary need.
6. Private dining, events and gift cards Each has its own page with a clear enquiry route. These are some of the highest-value enquiries a restaurant gets, and they are easy to lose in a footer link.

No affiliation with any of these businesses. They are here because each one gets a specific part of the job right, and that part is worth copying.

• Dishoom UK

  Each location page gives the address, opening hours by day, nearest Tube stations and accessibility details, and Restaurant schema sits behind it to match. Separate pages for searches like halal or vegan dining near each site pick up local queries that one location page would miss.

• Hawksmoor UK

  Each restaurant has its own menu pages in plain HTML, marked up with Menu schema and prices, so search engines can read the dishes as well as diners. Location pages separate venue hours from kitchen hours, and booking, private dining and event enquiries are one tap away.

• Rules UK

  The full menu is published as readable HTML with prices and jump links between sections. The PDF is only a printable extra. And each private dining room has its own page, so event enquiries have a clear place to land.

• sweetgreen US

  Each location page carries its own priced menu with calories and allergens, plus hours, phone and a pickup order button, all backed by Restaurant and Menu schema. The locations index lists every store as structured data, which helps each one appear for near-me searches.

• Gramercy Tavern US

  The booking form is built into the page, so a guest picks party size, date and time without leaving the site. Each of the two rooms has its own hours and location page. The menus are HTML with Menu schema, not PDFs.

• Joe's Pizza US

  An Order Now button sits on every page. The locations list gives each shop its address, a tap-to-call number and its own order link. For a takeaway-led business, that short path from search to order is the whole job.

I am the senior on every engagement, with twelve years and more than five thousand sites of practice behind the process. The build runs on Next.js, Astro or headless WordPress depending on who edits the site, and if you are replacing an existing site, the redirects, metadata and schema move across with it so the rankings do too.

Book a 30-minute call. No slide deck, no qualification screen. You describe the restaurants business, the brief, the timeline. I tell you whether I am the right person, and by the end of the call you have a stack pick, a price range, and a realistic delivery window.