This is a practical walkthrough: what a restaurant website actually has to do, the three ways to get one built in the UK, a step-by-step build order, the mistakes that quietly cost restaurants money, and what it all costs.
What a restaurant website actually has to do
Most restaurant sites fail at the basics, not the aesthetics. Before fonts and photography, your site has five jobs:
- Show the menu — as a page, not a PDF. More than half your visitors are on a phone, deciding where to eat right now. A PDF menu forces them to pinch-zoom a document designed for print; many give up. Search engines can't read dishes out of a PDF either, so “best katsu near me” will never find you. Your menu should be real text on a real page, updated the moment a dish or price changes.
- Answer the three questions: are you open, where are you, can I book. Hours, address with a map link, and a booking route belong within one scroll of the top — on mobile.
- Take the booking (or the order) itself. Every booking that happens on your own site instead of a portal is a guest whose details you keep and a fee you don't pay. (More on commission below.)
- Look like your room. The website is the first impression for a guest who's never walked in. A generic template with someone else's stock photos sells a restaurant that isn't yours.
- Be found. Google reads your site's text, structure and speed. Local search (“Thai restaurant Bristol”) is where restaurant demand lives, and your site is what Google ranks.
Your three options in the UK
An agency or freelancer
You'll get custom design and someone else does the work. The trade-offs: cost is quoted upfront and again whenever you want changes; the timeline is weeks, not hours; and after handover, editing the menu usually means emailing someone and waiting. For a restaurant whose menu changes weekly, that last one matters more than it sounds.
A generic website builder
The big drag-and-drop names. Cheaper, and you own the process — but you're assembling a restaurant site out of generic parts. The menu is a text box you format yourself. Bookings and ordering are third-party plugins with their own fees. Expect to spend evenings on design decisions a restaurant-specific tool has already made.
A restaurant-specific builder
Tools built only for restaurants start from finished restaurant sites, not blank pages: the menu is structured data (with dietary tags and spice marks), booking is built in, and the design decisions were made by someone who has looked at a thousand restaurant websites. This is the category TableSpark is in, so weigh our view accordingly — but the category logic holds whoever you pick.
The commission trap
However you build the site, be careful how bookings and orders run through it. Most reservation platforms charge per seated cover, or a monthly fee plus per-booking charges. Most ordering and delivery platforms take a percentage of every order. Two things follow:
Your costs rise exactly when you succeed. A full Saturday costs more than a quiet Tuesday. And the platform owns your guest — their email, their booking history, their marketing consent live on the platform's list, not yours.
The alternative is direct: bookings and orders on your own domain, delivered to your own inbox, at a flat cost. That's how TableSpark works — 0% commission, explained here — but whatever you choose, ask the per-cover and per-order question before you sign.
Building it, step by step
Gather the raw material (one evening)
Your current menu with prices; 20–30 photos (dishes, the room, the front); opening hours; address and phone; your story in three sentences. Phone photos in good daylight beat no photos — you can upgrade later.
Start from a finished site, not a blank page
Pick a template whose mood matches your room — not the one with the prettiest stock food, because your photos will replace it anyway. Browse by style, or by cuisine if that's easier: 50 finished restaurant templates, grouped from Italian to Thai to fine dining.
Put the menu in properly
Dish names, descriptions, prices, dietary marks — as structured menu data, not pasted text. This is the highest-value hour of the whole build: it's what guests came for and what Google indexes. (On TableSpark you can photograph your paper menu and let the AI draft the whole site from it — how that works.)
Wire up bookings
A form guests can use in under a minute: date, time, party size, contact. Test it yourself on your phone. Make sure you know where the booking lands (email? a dashboard? both?) and that someone checks it before service.
Connect your domain
yourrestaurant.co.uk looks right on a menu card and collects the search value of every mention. Builders connect a domain you already own via a DNS record; buying one costs a few pounds a year.
Publish, then do the ten-minute SEO pass
Before you share the link: every page has a sensible title (“Menu — Your Restaurant, Bristol”, not “Home”); your address and hours appear as text; photos have descriptions. Then claim your Google Business Profile and point it at the new site — for a restaurant, this free listing is as important as the website itself.
Keep it alive
An out-of-date menu or wrong bank-holiday hours quietly burns trust. Whatever you build with, editing must be easy enough that you actually do it — from a phone, in the minutes before service.
The mistakes that cost real money
- The PDF menu. Covered above; still the single most common failure.
- Instagram instead of a website. Instagram is where guests discover you; the website is where they check the menu and book. A profile can't hold hours, a bookable form, or a Google ranking.
- Renting your web presence from a portal. If your only online home is a listing on a booking platform, you're paying commission for guests who searched for you by name.
- A site you can't edit. If changing a price means emailing an agency, prices will be wrong by summer.
- Ignoring the search results page. Title tags, real menu text and a Google Business Profile cost nothing and decide whether “restaurants near me” includes you.
What it costs (honestly)
Frequently asked
How long does it take?+
With your menu and photos ready: an afternoon on a restaurant-specific builder; a weekend on a generic one; weeks with an agency.
Do I need to know how to code?+
No — for any of the three routes. What you need is your menu, your photos, and an hour of honesty about what makes your room different.
Can I do it from my phone?+
Increasingly yes, and you should insist on it: the menu edit you make at 5:40pm before service is the one that matters.