Restaurant Website Design UK: The Complete 2026 Guide to Bookings, Direct Orders, and Local Search

Every order through Deliveroo costs you up to 35% in commission. Every phone booking is customer data you never captured. Your website should be fixing both.

There is a specific, quietly expensive problem sitting inside most independent UK restaurant businesses: they have spent years building a genuinely loyal local following, and they are giving away a significant share of the margin on that loyalty to third-party platforms. Every order placed through Deliveroo, Just Eat, or Uber Eats costs the restaurant between roughly 14% and 35% in commission. Every table booked by phone call, rather than through an owned booking system, is a customer whose email address, dining preferences, and repeat-visit pattern the restaurant will never capture and never be able to market to directly.

A properly built restaurant website - fast, with a genuine HTML menu that Google can actually read (not a PDF or an image), direct commission-free ordering, and integrated table booking - addresses both problems simultaneously. We build websites for hospitality businesses at WebWise Digital. This guide covers what a genuinely effective restaurant website needs in the UK in 2026.

77% - of customers check a restaurant's website before dining, according to Toast research

80-90% - the conversion rate drop restaurants see on mobile when the website is not properly mobile-optimised

14-35% - the commission third-party ordering platforms take on every single order - money that stays with the restaurant when ordering happens through its own site

1. The PDF Menu Problem: Losing Both Mobile Diners and Google

The single most common, most damaging mistake on UK restaurant websites is the PDF menu. It seems like a convenient shortcut - upload the same file used for print, done. In practice it fails on two fronts simultaneously.

On mobile, a PDF menu requires pinching, zooming, and scrolling sideways to read - exactly the friction that causes a hungry, impatient visitor to give up and choose the restaurant two doors down instead. And for Google, a PDF or image-based menu provides essentially no readable content: it cannot tell searchers or search engines what specific dishes are offered, what a specific cuisine search should surface, or what dietary options are available. A diner searching "vegan Sunday roast Leeds" or "gluten free pizza near me" will never find a restaurant whose menu exists only as an unreadable image.

WATCH: The fix that also improves rankings

An HTML menu page - real, readable text with dish names, descriptions, prices, and dietary tags, formatted cleanly for mobile - should be the primary version of the menu, with a PDF offered only as a secondary download for anyone who genuinely wants it. This single change does two things simultaneously: it removes the biggest mobile conversion barrier on the site, and it gives Google the specific dish-level content needed to rank for cuisine, dish, and dietary-specific searches that a PDF menu can never capture.

2. The Direct Ordering Case: Keeping the Commission

Third-party delivery platforms serve a genuine discovery purpose - a new customer who has never heard of a restaurant may find it browsing Deliveroo. But once that customer has ordered once and liked the food, every subsequent order routed through the same platform is pure, avoidable commission loss. Research indicates that a majority of consumers actually prefer to order directly through a restaurant's own website rather than a third-party app when given the option and made aware of it - the barrier is usually that the restaurant never built that direct option, or buried it somewhere the customer never found.

OPPORTUNITY: The commission maths that justifies the website investment on its own

A restaurant doing 3,000 pounds a month in delivery orders through third-party platforms at a 25% average commission is paying 750 pounds a month, 9,000 pounds a year, in commission alone. A direct ordering system built into the website - typically integrated through a payment processor like Stripe, with no ongoing per-order platform fee - shifts that margin back to the restaurant. Even a partial shift of existing repeat customers from third-party ordering to direct ordering pays for a properly built website many times over within the first year.

3. Booking Systems: Removing Friction Between Interested and Booked

A diner deciding to book a table at 11pm on a Tuesday, after browsing several restaurant websites, will not book anywhere that requires a phone call during business hours. Live, 24/7 online booking - integrated with a platform like ResDiary (a strong option for UK independents), OpenTable, or a simpler standalone system depending on the restaurant's size - removes this friction entirely. The booking widget should show real available time slots, confirm instantly, and send automatic confirmation and reminder messages to reduce no-shows.

The specific requirement, covered throughout our CRO guide, is that booking must be reachable within two or three taps from any page on the site - not buried behind multiple menu clicks. A visitor who has decided to book should never have to search for how to do it.

4. Photography: The Element That Decides Before the Food Does

Restaurant decisions are made visually before they are made on any other criteria. Strong food and interior photography is not a nice-to-have design element - it is close to the entire decision-making input for a diner who has never eaten at the restaurant before. Photos should be genuine, current, and specific: the actual dishes served, not generic stock food photography, and the actual dining room, not an aspirational image that does not match reality.

On Google Business Profile specifically, listings with photos receive meaningfully more direction requests than those without - one widely cited figure puts the increase at 42%. Photos should be updated monthly, not left static for years, to keep the profile looking active and current.

5. Local SEO and Google Business Profile for Restaurants

For most independent restaurants, the Google Business Profile functions as the effective homepage - a diner sees the map pin, reviews, hours, photos, and booking link before they ever reach the actual website. This makes GBP optimisation, covered in full in our GBP guide, the single highest-leverage free action available. The ordering link on GBP specifically should point to the restaurant's own direct ordering system, not a third-party delivery app - directing that traffic to a commission-charging platform when a commission-free alternative exists is giving away margin unnecessarily.

Reviews carry exceptional weight for restaurant decisions specifically, more than almost any other local business category - a diner choosing between two similarly positioned restaurants will very often defer to whichever has the stronger, more recent review profile. The review response and generation discipline covered in our negative reviews guide and reviews service applies directly.

Multi-location restaurants

A restaurant group with multiple branches needs a genuinely unique page per location - not a templated copy with the address swapped. Each location page should have its own specific opening hours, its own local content, and ideally its own GBP profile, linked clearly from a central locations page. Duplicated, near-identical location pages are a well-documented pattern that suppresses ranking for all of them simultaneously.

6. Schema Markup for Restaurants

Restaurant schema markup should reflect facts that are already visibly true on the page - cuisine type, price range, opening hours, accepted payment methods, and menu items with prices - rather than being used to claim anything the page itself does not support. Properly implemented Restaurant and Menu schema, covered in general depth in our schema markup guide, gives Google the structured data needed to surface rich results (star ratings, price range, opening status) directly in search results, and gives AI-powered search systems the structured basis to recommend the restaurant confidently for specific cuisine or dish queries.

7. Technical Performance: The 80-90% Mobile Drop-Off

The mobile performance statistic for restaurants is genuinely stark: restaurants without a properly mobile-optimised website see conversion rates drop by 80 to 90% on mobile compared to desktop. Given that the overwhelming majority of restaurant search happens on a phone - someone deciding where to eat tonight, right now, on the way home - this single technical failure eliminates the majority of the site's commercial potential before a single dish photo is even seen.

We build every restaurant site in Next.js, deployed on Cloudflare's CDN, validated against Core Web Vitals before launch - the same technical foundation covered in depth in our Core Web Vitals guide and mobile conversion guide. Image-heavy restaurant sites are particularly vulnerable to slow load times if not built correctly - modern image formats and proper lazy-loading are essential, not optional.

8. Email: The Retention Channel Most Restaurants Never Build

A diner who books a table directly, rather than through a third-party platform, has given the restaurant their email address - a marketing asset a Deliveroo order never provides. The email automation system covered in our email marketing guide applies directly to hospitality: a birthday or anniversary reminder, a seasonal menu launch announcement, a re-engagement email to a customer who has not booked in three months. This is one of the clearest, most concrete arguments for direct booking over third-party platforms - every direct booking builds a marketing asset the restaurant will own indefinitely.

9. What WebWise Builds for UK Restaurants

A five-page starter site from 950 covers homepage, menu (genuine HTML, not PDF), about, contact, and booking page - hand-coded in Next.js, mobile-first, Core Web Vitals green, with Restaurant and Menu schema and GBP connection. The Lead Generator tier at 1,500 adds direct commission-free ordering integration and full booking system setup. The Full Local SEO tier at 2,500 adds multi-location pages where applicable, citation building, and three months of ranking work.

The starting point is a 15-minute call at webwise.digital/contact - or see full pricing at webwise.digital/#pricing.

Conclusion: The Website That Keeps the Margin You Are Currently Giving Away

The case for a properly built restaurant website is not primarily about aesthetics or brand storytelling, though those matter too. It is about two specific, quantifiable leaks in most independent restaurants' current setup: commission paid unnecessarily to third-party ordering platforms, and customer data never captured because bookings happen by phone rather than through an owned system. A website that fixes both - readable HTML menu, direct commission-free ordering, seamless booking, and the mobile performance to make all of it usable - pays for itself in the margin it recovers within months.

Further reading: our local SEO guide for the broader citation and map pack system, and our mobile conversion guide for the technical detail behind the mobile performance figures cited throughout this guide.