ContactBook a call

Industries/ Hospitality/ Fast, image-led venue websites

A restaurant website your managers keep up to date, fast on any phone

Guests decide from your photographs, your menu and your opening hours, usually on a phone and often in a hurry. We build a site that shows all three quickly, that your own team keeps current, and that hands guests to your reservations system with nothing lost on the way.

Two friends at a cafe table choosing a restaurant on a phone, the screen showing large food photos.
Used by
Guests, general managers, head chefs and marketing leads
Takes the place of
PDF menus, out-of-date hours and emails to a web supplier
Connects to
Your reservations system, booking engine and map listings
Built with
Our company websites service

Where it hurts today

A normal week, before it exists

The menu on your website is a PDF someone uploaded in spring. It takes a while to open on a phone, the text is too small to read without pinching, and two of the dishes came off in July. Search engines cannot read it properly, so a guest searching for a Sunday roast nearby may never learn that you serve one. Changing it means exporting a new file from the design software, finding the login and hoping the old link still works.

Your photographs are the reason people book, and they are also why the site is slow. Full-size files straight from the photographer's camera take an age on a weak signal, so the guest scrolling at a bus stop sees grey boxes and goes back to the search results. Meanwhile the opening hours on the site, on your maps listing and on the door each say something slightly different, and the bank holiday hours were never added at all.

Then the phone rings with questions the site should have answered. Is there parking? Can we bring the dog? Is there a step-free entrance? Is the terrace open in October? Reception answers the same handful of questions every afternoon, and the private dining enquiry that came through the contact form sat in a general inbox for four days because nobody owned it. On a hotel site, the room pages still show the carpet you replaced two winters ago.

What it does

Fast, image-led venue websites, feature by feature

What the site does, built around the things a venue actually changes from one week to the next.

  1. 01

    Digital menus built from dishes, not PDFs

    Each dish is entered once, with its description, dietary tags and allergens. The website menu, the printable menu and the version search engines read all come from that same list, so changing a dish changes it everywhere, and a dish that comes off in July disappears from every version at once.

  2. 02

    Restaurant photography that loads quickly

    Your team uploads the photographer's full-size files and the site produces smaller versions for each screen in modern formats, showing the first picture straight away and loading the rest as the guest scrolls. A large screen keeps the quality, and a phone on a weak signal does not have to wait for it.

  3. 03

    Opening hours, special hours and exceptions

    Kitchen hours, bar hours and breakfast service are set separately, with bank holidays, private hire closures and seasonal changes entered ahead of time. The site shows today's hours first, and the same details are labelled in the page code so search results can show them correctly.

  4. 04

    Events and seasonal menus on a schedule

    Quiz nights, live music, tasting menus, Mother's Day and the festive set menu each get a start date and an end date. The Valentine's menu goes live on the right morning and disappears on the fifteenth, without anyone having to remember to take it down.

  5. 05

    Book a table buttons that keep the guest

    Every Book a table or Check availability button opens your reservations system or hotel booking engine directly, carrying the site, date and party size across where that system accepts them. We count the clicks on each button, so you can see which pages actually send guests on to book.

  6. 06

    Pages for each site, room and event space

    A group gets a page per site with its own menu, hours and directions. A hotel gets a page per room type. Private dining rooms and event spaces show capacity, layouts and what is included, and the enquiry form goes to the named events manager rather than a general inbox.

A day with it

How the day runs instead

A normal week for a two-site restaurant group once the new site is running.

  1. Monday, 10am
    Head chef

    Updates the autumn dishes in the editor, adding a new starter and ticking sesame and mustard from the allergen list. The changes save as a draft for the general manager to check, and the live menu stays exactly as it was.

  2. Tuesday, 3pm
    General manager

    Previews the new menu on a phone, corrects one description and schedules it to go live on Friday at 4pm on both sites. Adds the Bonfire Night supper as an event, with its own page and a booking link.

  3. Thursday, 7.40pm
    Guest at a bus stop

    Finds you from a search, sees the first photograph straight away and reads the menu as proper text. Picks Friday and a party of four on the site, taps Book a table and lands in your reservations system with both already filled in.

  4. Friday, 4pm
    Front of house team

    The autumn menu switches over on the website, and the printable version updates with it. The summer menu is archived rather than deleted, in case anyone needs it. Nobody stayed late to make it happen, and nobody emailed a supplier.

  5. Sunday evening
    Owner

    Reads a short weekly email: visits by site, clicks on each booking button, the pages guests read most and two private dining enquiries, both already answered by the events manager earlier in the week.

What it connects to

Works with what you already run

The site does not try to take bookings itself. It hands guests to the systems that already do, with as little lost as possible.

  • Reservations system

    Booking buttons and embedded widgets open your table booking system at the right site, carrying the date and party size where it accepts them, for example ResDiary or SevenRooms, where they offer booking links or widgets.

  • Hotel booking engine

    Room pages link to your booking engine with dates and room type ready. Where the engine offers an API, the site can show live rates or availability rather than keeping its own copy that drifts out of date.

  • Maps and listing services

    Opening hours, special hours and addresses kept consistent between the site and your business listings, sent automatically where the listing service's API allows it, and as a checklist for your team where it does not.

  • Email marketing tool

    Newsletter sign-ups pass to the tool you already use, with the wording of the consent the guest gave and the date they gave it, so your marketing list stays one list rather than three.

The first version

Start small, then grow it

A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.

In the first version

  • Home, menus, opening hours, find us and booking pages for each site
  • Menus built from dishes and allergens, with a printable version from the same source
  • An editor with previews, approvals and scheduled publishing for your managers
  • Automatic resizing and conversion of every photograph your team uploads
  • Booking buttons into your reservations system, with clicks counted per page

Once it is in use

  • Private dining and event space pages with enquiries routed to a named person
  • Gift voucher pages that hand guests over to your voucher provider
  • Further languages for guests planning a visit from abroad
  • Opening hours sent to listing services automatically, where their APIs allow

Buyer's guide

Before you commission one

Four things worth deciding before you commission a restaurant website, whoever builds it.

  1. 01

    A website builder or a built site

    If you run one restaurant, change the menu twice a year and take bookings through one widget, a website builder or a hospitality website platform that bundles menus and booking buttons is probably the better buy, and the money left over is better spent on photography. A built site earns its place when you run several sites, rooms or event spaces, change menus often, or your photographs make a template crawl on a phone.

  2. 02

    Gather photographs and facts first

    No code makes a dim photograph of an empty room look inviting. Before the build, plan a shoot of the dishes, the rooms at their best hour, the team and the outside of the building. Gather the dish list with allergens signed off, your access details, and the questions reception answers by phone every week, because those answers belong on the site.

  3. 03

    Name the editors and the approver

    Decide who will actually update the site and who signs off allergens and prices. If nobody owns it, it drifts out of date within a season, however easy the editor is. One named person per site, usually the general manager, plus the head chef for menus and a marketing lead for events and offers, is normally enough.

  4. 04

    Decide how you will judge it

    Record a few signals on the old site before launch: clicks on booking buttons, calls and direction requests from your maps listing, private dining enquiries, and the Core Web Vitals for your busiest pages on phones. Watch the same signals for a couple of months afterwards, and judge the site on them rather than on how it looks in a meeting room.

Terms worth knowing

The words you will meet

Core Web Vitals
Google's three measures of how a page feels on a real phone: how quickly the main content appears, how quickly the page responds to a tap, a measure that replaced an older one in 2024, and whether the layout jumps about while loading. Large, unprepared photographs can hurt all three, so we check them on every image-heavy page.
Structured data
Labels in the page code, written in the shared schema.org vocabulary with types such as Restaurant and Menu, that tell search engines which text is your address, opening hours and menu. It helps search engines and maps show those details correctly, though nobody can make them display it, and a PDF menu offers none of it.
WCAG 2.2
The current version of the Web Content Accessibility Guidelines, the usual reference point for accessibility audits, with level AA as the normal target. For a venue it covers things guests notice: menus a screen reader can read, booking buttons large enough to tap, enough contrast over photographs, and forms that work with a keyboard.

Handled with care

The details that matter here

The details on a venue website that cause real trouble when they are wrong.

  • Allergens on the published menu

    Allergens come from the dish record, and a dish cannot be published until your chosen person, usually the head chef, signs them off. In the UK, food law names 14 allergens and the Food Standards Agency recommends written information backed by a conversation. US federal labelling rules mostly do not cover restaurant food, so there we follow your own policy.

  • Access information and accessible pages

    Guests with access needs often check before they travel. We write step-free access, accessible toilets and hearing loops as plain text, design to WCAG 2.2 level AA and keep menus as real text, never pictures. If guests in the EU book or order through the site, we check with your adviser how the European Accessibility Act applies.

  • Moving from the old site

    Old menu links, room pages and event pages are mapped to their new addresses, so search results and saved links keep working. We leave your domain and email where they are, and switch over at a quiet time of the week, never the Friday before a bank holiday.

  • Who can change what

    We agree with you who drafts and who publishes. A chef might edit dishes while only the general manager publishes them. Every change records who made it and when, and any page can be put back to an earlier version in one step if something goes out wrong.

Guides

Worth reading first

Questions

What buyers ask first

Can a restaurant website connect to our reservation system?

Yes. Book a table buttons and embedded widgets send guests to the reservations system or hotel booking engine you already use, so your diary, deposits and guest records stay where your team expects them. We design the pages around it. If its booking widget is slow or awkward on a phone, we will tell you, and improving that journey is a separate piece of work rather than a reason to switch systems.

How do we update the menu on our restaurant website?

Your head chef or manager edits dishes in a simple form, with fields for the name, description, dietary tags and allergens, and the design is applied automatically. There is nothing to drag around and no way to change the fonts by accident. At handover we ask the chef to add a real dish while we watch, and we keep adjusting the editor until that feels easy.

Will a new website affect our Google ranking?

We do the groundwork to protect it: every old address is redirected to its new page, the menu becomes readable text, opening hours are labelled for search engines and the site loads quickly. We record where you stand before the switch and watch it closely afterwards. Nobody can promise a ranking, because it also depends on your reviews, your listings and the venues around you.

Does a restaurant website need to be accessible?

It should be, for your guests and increasingly for the law. In the EU, the European Accessibility Act has applied since 28 June 2025 to many consumer services sold online, which can include booking and ordering, with an exemption for the smallest service businesses. Rules elsewhere differ, so we check your position with your adviser. Either way, we design to WCAG 2.2 level AA.

Who owns a restaurant website once it is built?

You do. The domain stays registered to your business with a login you hold, the code sits in a repository in your name, and the hosting and editing accounts are yours with us added as users you can remove. The photographs remain under whatever licence your photographer gave you. If you ever leave us, nothing needs to be rebuilt.

Send us the link to your menu page

We will open it on a phone, the way your guests do, and reply within 48 hours with what we would change first and what is fine as it is.

More for hospitality

What else we build for hospitality