What should restaurant website design do for an independent UK restaurant?
Restaurant website design has four jobs: help people book, show them the menu, answer allergy and dietary questions honestly, and confirm the practical details (hours, location, parking, accessibility). Everything else, including the beautiful photography, supports those four.
Most visits happen on a phone, often within an hour or two of the meal, sometimes standing outside. That visitor wants to know three things quickly: is there a table, what does the food cost, and can I eat it. A homepage slideshow that takes five seconds to load and hides the booking button below it loses that person to the restaurant next door.
The second group plans ahead: birthday dinners, anniversaries, work parties, private events. They read more, compare set menus, look at the room and want to talk to someone. They need a different path: private dining pages with capacity, sample menus and a proper enquiry form.
- Book: a button in the header on every page, one tap on mobile.
- Menu: text, prices, dietary tags, updated from one source.
- Allergens: clear signposting and an invitation to talk to staff.
- Practical: hours, map, transport, step-free access, contact.
ResDiary, OpenTable, SevenRooms or your own booking system?
Keep the booking platform you already run unless it clearly costs you more than it earns; the website's job is to put its widget in the right place. Building your own booking system makes sense mainly for restaurants with unusual rules, heavy event traffic or a strong wish to own every diner relationship.
ResDiary, OpenTable and SevenRooms are all established table-management platforms used by UK restaurants. Each has its own pricing model, marketplace exposure and features, so compare their current terms directly. What matters for the website is simple: each offers a way to take bookings from your own site, and the button should open that flow without sending the diner through three pages first.
A booking system of your own gives full control: table rules, deposits for large groups, pre-orders for set menus, reminders by email or WhatsApp and your own diner database. It also means you maintain it. We build these as custom software, and the comparison table below lays out when each route fits.
Stay on a platform when
you value the diners its marketplace sends, your team already knows it, and your booking rules are standard.
Build your own when
your rules are unusual (deposits by party size, set-menu pre-orders, event ticketing), or you want every booking and every guest record held by you.
Where should the booking button go on a restaurant website?
Put the booking button in the top right of the header on every page, keep it visible when the visitor scrolls on mobile, and repeat it at the end of each menu. A diner who decides while reading the dessert list should not have to scroll back to the top.
The button should open the booking flow directly, either in an overlay or on a booking page that loads instantly. Avoid sending people to a separate “contact” page with a phone number and a paragraph of text. If you take walk-ins only, say so clearly in the same place the booking button would be, so people do not search for something that does not exist.
For groups above your online limit, show a short note beside the widget explaining how to book larger tables: a phone number, a WhatsApp link or an enquiry form. Many restaurants lose large, valuable bookings because the widget simply says “no availability” for ten people, and the diner assumes the restaurant is full.
- Header button, sticky on mobile.
- Repeated below every menu and on the private dining page.
- Clear alternative route for large groups.
- Walk-in policy stated plainly if you do not take bookings.
How should a restaurant website show the 14 allergens?
Signpost the 14 regulated allergens clearly on every menu page, mark the allergens in each dish where your kitchen has confirmed them, and invite diners to speak to staff before ordering. The Food Standards Agency's allergen guidance lists the 14: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, peanuts, sesame, soybeans, sulphur dioxide and sulphites, and tree nuts.
For non-prepacked food, the FSA guidance says allergen information can be given in writing, such as on a menu or in an information pack, or verbally with a clearly visible written notice telling customers to ask. It also says written information supported by a conversation works best for consumers. A website is not the legal allergen record for a dine-in meal, but it is where many diners with allergies decide whether to visit at all.
So we build menus with allergen data attached to each dish, filterable by allergen, with a clear note that recipes and suppliers change and that staff should be told about any allergy on arrival. Your kitchen supplies and signs off the allergen data; we never guess from dish names.
Source: the FSA's allergen guidance for food businesses. We build the display; your kitchen and food safety lead are responsible for the allergen information itself.
HTML menus load faster, read better on phones, can be found by Google and AI search, and can carry allergen and dietary tags. PDF and image menus force diners to pinch and zoom, often download slowly, are hard for screen readers and are frequently out of date because nobody wants to redesign the file for a price change.
We store each menu as structured data: sections, dishes, descriptions, prices, dietary tags and allergens. The website shows it as clean text with clear headings. The same data can produce a printable version for the table, so the dining room and the website always agree. When the chef changes a dish, one edit updates everything.
For QR code menus at the table, the code points to the same HTML menu page, sized for phones, with no login and no app download. If you run several menus (lunch, dinner, Sunday, drinks, set menus), each gets its own address, so you can link Google, social media posts and email newsletters directly to the right one.
Google Business Profile menus and reservation links for UK restaurants
Your Google Business Profile is often the first thing a diner sees, so its hours, menu link and booking link must match the website exactly. Google's help pages say you can add links on your profile for customers to make a reservation or place a food order, up to 10 links per category, and choose a preferred link where you have more than one option.
Google also shows links from its partner providers automatically. If your booking platform is one of them, a reservation button may already appear; check it points to the right restaurant and remove anything outdated. Set your own website's booking page or your chosen platform as the preferred link so diners land where you want them.
The menu link should point to your HTML menu page rather than a PDF. Hours need updating for bank holidays, Christmas and any closures, and your team should know who does that. We set up the profile structure, link it properly to the site and can manage the updates as part of monthly care.
- Primary category matching your cuisine or format.
- Menu link pointing to the HTML menu page.
- Reservation link set as preferred, pointing to your booking flow.
- Special hours added before bank holidays and Christmas.
- Fresh photos of dishes and the room, updated each season.
Private dining and events pages that bring in enquiries
A private dining page should answer the organiser's questions before they ask: which rooms, how many guests seated and standing, sample menus with starting prices per head, any minimum spend, available dates, and how to enquire. Organisers compare several venues at once and shortlist the ones that give them enough to decide.
Each room gets photos, capacity, layout options and accessibility details. Sample menus should be real menus you would serve, with dietary options. The enquiry form asks for the event date, number of guests, type of event, budget range and any dietary needs, so your events manager can reply with a proposal rather than five questions.
Events you run yourself, such as tasting evenings, supper clubs or live music, belong on an events page with dates, prices and a booking or ticket link. Past events can stay as a short archive to show what the venue does. Structured data for events helps Google show them in search.
How much does restaurant website design cost in the UK?
With BtechWaleTech, restaurant website design starts at US$150 for up to 100 pages, including menus, allergen signposting, booking integration and private dining. Quotes from other UK providers vary widely; what drives the difference is usually photography, custom booking logic, the number of menus and locations, and whether copy is written for you.
The main add-ons are predictable. Gift voucher sales with card and wallet checkout are a shop build from US$750. A booking system you own, with deposits and table rules, is custom software from US$900. A restaurant group with many venues and menus may need an SEO-scale structure from US$300. AI tools that answer common questions or triage events enquiries start at US$600.
Photography is not something we can provide from India; a local photographer or your own careful phone photos work, and we optimise them for speed. For general UK pricing across site types, see our UK website design cost guide.
Restaurant website design UK diners use on the move: speed and mobile
Restaurant sites must be fast on a phone with weak signal, because many diners check them on the street, on a train or in a car park. That rules out autoplay video headers, heavy sliders and full-screen images that load before anything else.
We build pages so the text, booking button and menu load first, with images compressed and loaded as the diner scrolls. Fonts are limited to what the design really needs. Google's Core Web Vitals in Search Console give us a way to check real-world speed after launch, and we fix any page that falls behind.
Accessibility and speed go together. Clear text menus, good contrast, buttons large enough to tap and sensible headings help people using screen readers or larger text settings, and they help everyone else too. For a deeper check, our website accessibility audit page explains what is tested.
How do restaurants get found on Google in the UK?
Restaurants are found mainly through the Google map pack and searches like “Italian restaurant near me” or “brunch in Leith”. Visibility depends on the Business Profile, distance, reviews and the relevance of your pages, so the website supports the profile rather than replacing it.
On the site, that means pages for each cuisine or format you want to be known for, clear location information, menus in text so Google understands what you serve, and structured data describing the restaurant, opening hours, menu and booking. For a restaurant, a page about your Sunday roast or tasting menu often does more than a generic blog post.
Reviews matter a lot. Ask diners for reviews after their visit with a direct link or QR code, and reply to them. Google's review policy prohibits offering incentives, such as discounts or free items, in return for posting or changing reviews, so do not attach offers. Nobody can guarantee a map pack position; consistent, honest work improves the odds.
Calorie labelling and hygiene ratings on restaurant websites
Larger restaurant businesses in England must show calories on menus, including online menus, and many restaurants choose to show their food hygiene rating on the site. Both need planning in how menus and footers are built.
Government guidance on calorie labelling says the rules came into force from 6 April 2022, apply to businesses in England with 250 or more employees selling non-prepacked food for immediate consumption, and extend to food sold on a website or app, including third-party delivery apps. Most independents fall below that threshold, but a growing group should check. If you are in scope, our menu data includes a calorie field for each dish.
For hygiene ratings, the Food Standards Agency guidance says display at premises is mandatory in Wales and Northern Ireland and voluntary in England, and it encourages businesses to promote their rating on websites and social media. We can add the official rating image supplied through the FSA's resources in the footer or on the find-us page.
How does a UK restaurant work with a web team in India?
Our working day overlaps the UK from late morning, which suits restaurants well: owners and managers can talk between the morning prep and lunch service, or in the quiet mid-afternoon, and changes are ready by the next morning.
Most of the work happens on WhatsApp and a shared folder. You send menus as documents or photos, allergen sheets from your kitchen, logo files, photos and your booking platform details. We send designs and a preview link. Calls are by video when needed. Quotes are in USD, payable in USD or GBP through Wise, bank wire or PayPal; invoices come from India, and nothing is billed before you approve the written quote.
The domain, hosting and code are in your name from day one. We do not visit the restaurant, photograph dishes or print menus. We are honest about that so you can arrange photography locally if needed.
Days one to five
Menus and allergen data collected, booking platform checked, page map agreed, homepage and menu design sent for comments.
Days six to ten
Menus built from data, booking button placed, private dining page and find-us page built, Google profile links planned.
Mistakes to avoid in restaurant website design
The most common mistakes are menus as PDFs, a hidden booking button, hours that disagree with Google and allergen information that is vague or missing. Each one sends diners elsewhere.
Other problems are quieter but costly. Menus that nobody updates, so prices on the site are lower than in the restaurant. Sliders and video that make the site slow on mobile. A contact form for large bookings that goes to an inbox nobody checks. Booking links that open the platform's page for a different branch. Social media feeds embedded on the homepage that slow everything down and show a post from last year.
When hiring a designer, ask how menus are edited, who owns the domain and hosting, how the booking platform is integrated and what happens when your menu changes next season. If the answer involves sending a new PDF to the designer every time, expect the site to fall out of date.
- PDF or image-only menus.
- Booking button below the fold on mobile.
- Opening hours that differ between the site and Google.
- No clear allergen signposting.
- Domain registered by the designer rather than the restaurant.
Restaurant website design UK checklist
Check your current site against this list. If more than three items fail, a rebuild is usually faster than patching.
- Booking button in the header of every page and sticky on mobile.
- Menus in HTML with prices, dietary tags and allergen signposting.
- An invitation to tell staff about allergies before ordering.
- Separate addresses for lunch, dinner, drinks and set menus.
- Opening hours identical on the site and Google Business Profile.
- Profile menu and reservation links pointing to your pages.
- Private dining page with capacity, sample menus and enquiry form.
- Large-group booking route explained beside the widget.
- Find-us page with map, transport, parking and step-free access.
- Calorie field on menus if your business is in scope in England.
- Page loads quickly on mobile in Search Console's Core Web Vitals report.
- Domain and hosting registered to the restaurant.
Worked example: a hypothetical 40-cover bistro in Bath
Say a 40-cover bistro in Bath uses a booking platform, has menus as PDFs, and gets many calls asking about gluten-free options and private hire of its upstairs room. This is a made-up scenario to show how the build would go, not a real client.
The new site keeps the existing booking platform, but moves the button into the header and repeats it under each menu. Menus become HTML, built from a single data file the chef edits, with gluten, milk and nut markers on each dish, a filter for diners with allergies and a clear note to speak to staff. The printed menus come from the same file.
The upstairs room gets a private dining page with seated and standing capacities, two sample menus and an enquiry form asking date, guests and budget. The Google Business Profile is updated with the HTML menu link, the preferred reservation link and special hours for bank holidays.
After launch, the bistro can see booking clicks, menu views and private dining enquiries in its analytics. If gluten-free questions keep arriving by phone, the next step might be a dedicated page on how the kitchen handles gluten, written with the chef.