Most of your future guests will meet your restaurant for the first time on a phone, standing on a pavement or sitting on a sofa, deciding where to eat within the next hour or the next week. Your website has one job in that moment: answer three questions fast — what is the food, where are you, and how do I get a table.
Everything else is decoration. This guide covers what independent UK restaurants actually need from a website in 2026, what you can safely skip, and the mistakes that quietly cost covers every week.
What diners actually do before they book
The typical journey is short and almost entirely mobile. Someone searches “Italian restaurant Cheltenham” or “Sunday lunch near Burford”, scans the map results, checks photographs and reviews on Google Business Profile, then taps through to the website for three things: the menu, the opening hours and a way to book.
Two consequences follow. First, if your site is slow or awkward on a phone, you lose people before they see a single dish. Second, your website and your Google Business Profile are one system in the guest's mind — a mismatch between them (different hours, an old menu, a dead booking link) reads as a restaurant that does not sweat the details.
The five pages every restaurant website needs
Independent restaurants do not need thirty pages. They need five good ones:
1. Home. One strong photograph of the food or the room, a sentence that says what you serve and where you are, opening hours, and an unmissable booking button. If a visitor cannot work out your cuisine, location and next step within five seconds, the page is failing.
2. Menu. The most visited page on almost every restaurant site, and the most frequently botched — see the next section.
3. Book a table. A reservations page that feels like part of your site, with a visible phone number for people who prefer to call.
4. Find us. Full address, an embedded map, parking and transport notes, opening hours and a tap-to-call phone number. This page does heavy lifting for “near me” searches and for guests already on their way.
5. Private dining, events or gift vouchers. These are your highest-margin enquiries. A dedicated page with real detail — capacities, sample menus, an enquiry route — converts far better than a line buried on the contact page.
Everything else — the story, the gallery, the newsletter — is optional and should never delay or clutter the five above.
Stop uploading PDF menus
The PDF menu is the single most common restaurant website mistake, and it is understandable: the print designer already made one, and uploading it takes two minutes. But a PDF fails in almost every way that matters.
Google cannot reliably read it, so your dishes — the exact phrases people search, like “Bibury trout” or “Sunday roast Oxfordshire” — never enter the index. On a phone it forces pinch-and-zoom gymnastics. It cannot be updated quickly when a dish changes. It is inaccessible to screen readers. And it carries no structured data.
An HTML menu fixes all of this: every dish name becomes searchable text, updates take minutes, prices stay current, and you can mark the page up with proper menu and Restaurant schema — name, address, cuisine, price range, reservation support — so Google can show rich, accurate information straight from search. Our complete guide to schema markup for restaurants walks through the markup, and the accessible menus guide covers the implementation side.
One more thing: include prices. Diners treat a menu without prices as either expensive or evasive, and many simply book elsewhere.
Reservations: the hand-off that loses covers
Most independents use a third-party reservations platform, which is sensible. The mistake is treating the hand-off as someone else's problem. A jarring redirect to a generic page that looks nothing like your restaurant costs real bookings, particularly on mobile.
What good looks like:
- the booking widget or page inherits your branding as far as the platform allows;
- availability, party size and special requests are easy to complete with one thumb;
- a phone number stays visible for guests who would rather call;
- confirmation is immediate and unambiguous;
- you can actually measure how many people start versus finish the booking.
Test the full journey on your own phone once a month, the way a guest experiences it. Our post on why restaurant websites lose reservations maps the common failure points in detail.
Google Business Profile and your website work as a pair
For most independent restaurants, the Business Profile is seen by more potential guests than the homepage. Treat it as a second website:
- keep opening hours synchronised everywhere, especially bank holidays, Christmas and January closures;
- link the menu and reservations buttons to the right pages, not the homepage;
- add real photographs regularly — dishes, the room, the team;
- respond to reviews, good and bad, like a professional;
- use the same name, address and phone number format on the profile and the website.
The website's role is to validate whatever the profile promised. If the profile says “cosy Cotswold pub with rooms” and the site looks like a nightclub flyer, the guest trusts neither. Reviews feed the same loop — our guide to Google reviews and local rankings explains how much they matter.
Photography: show the food you actually serve
Diners book with their eyes, and they have a finely tuned radar for stock photography. A generic plated salmon that has never been near your kitchen does two kinds of damage: it fails to persuade anyone, and it sets an expectation your kitchen then has to fight.
You do not need a huge shoot. Half a day with a photographer who understands food — budget £300 to £600 in most of the UK — produces enough dishes, room shots and team photographs to carry the website and the Business Profile for a year. Shoot the dishes people actually order, in the room they will sit in, in daylight where possible. Then refresh the set when the menu changes seasons. A phone camera is genuinely fine for the everyday social updates in between; it is the hero images on the homepage and menu that earn their professional fee.
Two practical rules on the website itself: compress every image before upload, and resist the forty-photo gallery. Six excellent photographs outperform sixty average ones, on load time as much as on appetite appeal.
Speed: hungry people are impatient
Restaurant sites are unusually prone to slowness: enormous uncompressed food photography, three embedded maps, a reservations widget, an events plugin and a cookie banner all fighting for a phone on 4G.
The priorities are boring and effective: compress and properly size every photograph, lazy-load anything below the fold, embed one map rather than three, and audit the third-party scripts once a quarter. Google's Core Web Vitals thresholds are a sensible target, and they correlate directly with whether a mobile visitor stays long enough to book. The detail is in our Core Web Vitals guide for restaurant websites.
The common mistakes checklist
Run your current site against this list:
- menu only available as a PDF;
- no prices on the menu;
- opening hours that differ between the website and Google Business Profile;
- no Restaurant or menu schema markup;
- a booking link buried in a footer or hidden behind a hamburger menu;
- no tap-to-call phone number on mobile;
- autoplaying video or music;
- stock photographs of food you do not serve;
- a gallery of forty uncompressed images;
- no allergen or dietary information anywhere;
- a menu from two seasons ago still live.
Three or more ticks and the site is actively costing you covers.
What it should cost
A focused, five-page custom site for an independent restaurant — HTML menu with schema, reservations integration, proper photography direction, fast on mobile — typically sits between £3,000 and £6,000 in the UK in 2026, plus modest monthly hosting and maintenance. Template builds can be done for less, with the usual ceilings. Beware any quote that does not mention the menu, mobile performance or the reservations journey: those are the three places the money is actually made.
The bottom line
A restaurant website is a booking tool with a menu attached, not a digital brochure. Five strong pages, an HTML menu Google can read, a reservations journey that works one-handed, a Business Profile kept in step, and a site that loads quickly on a phone — that is the whole job.
If your current site ticks the wrong boxes on the checklist above, run it through our website grader, look at our hospitality work, or book a restaurant website review. We will tell you plainly what is worth fixing and what is fine as it is.
