A venue website has eight jobs, and they are the same eight whether the venue is a forty-cover restaurant, a twelve-room hotel or a bar with a menu that changes every week. Get the first one wrong and the rest stop mattering, because a guest who cannot find the site never sees the room, the menu or the booking button. What follows takes each job in turn: the failure most venue sites make, and the check you can run against your own site tonight.
Being found for the venue's name and its area
A guest searching the venue's name plus their town should land on the venue's own website. Most independent venues lose this because the name and address are written slightly differently across the website, the booking platform and any directory listing, and search engines trust whichever version turns up most often. Writing the venue's name and postcode the same way everywhere it is listed fixes most of this on its own. The check: search the venue's own name in a private browser window and see what appears before the third result. The mechanics of hours and listings data get fuller treatment in Opening Hours, Listings and Being Found for Your Own Name.
Showing the room
A website's photography has one job: help a guest decide whether to book a table or a room. The common failure is a set of food photographs that could belong to any restaurant, sitting beside two or three phone shots of an empty dining room taken under the overhead lights. Guests read a badly lit empty room as a warning, whatever the food turns out to be. The check: look at the homepage as a stranger would and ask whether the photographs show this specific room on a specific evening, with people in it. If every image could belong to a competitor, it is not doing its job.
Showing the menu, and keeping it current
The menu answers the question a guest actually has, which is not what the kitchen does well but whether they can find something here, quickly, on a phone. The common failure is a PDF scanned from the printed menu, small enough to need pinching and zooming, and stale enough to list a dish the kitchen stopped making months ago. A menu built as ordinary web text rather than a scanned image lets a guest read it without effort and lets the venue update a price or a dish in minutes rather than at the next reprint. The check: open the site on a phone with one hand and see whether reading the starters means zooming in. If it does, the menu is built for the kitchen wall.
Taking the booking in the fewest taps
Once someone decides to book, a website has perhaps two taps before they give up and ring a competitor instead. The common failure is a booking link tucked inside a navigation menu the guest has to open first, or a "Book now" button sitting below several screens of atmosphere copy a phone user never reaches. The booking action should be visible without scrolling, on every page. The check: hand the site to someone who has never seen it and time how long they take to find the booking button from the homepage. If it needs more than a glance, move it.
Answering the questions guests ring about
Every venue fields the same handful of phone calls: is there parking, do you take dogs, is the ground floor accessible, do you do a set menu on Sundays. A website that answers these on the page itself takes calls off the phone and off a member of staff who would rather be serving. The common failure is an FAQ page that answers questions nobody asks while leaving out the one guests ring about weekly. A tool that answers a guest's specific question directly on the site, such as step-free access or whether children are welcome, is one way to carry that load without adding to a receptionist's evening; that approach is set out on AI Concierge for Venues. The check: ask whoever answers the phone what the last five questions were, and confirm each one has a clear answer on the site without a PDF to open.
Carrying allergen information lawfully
The Food Information Regulations 2014, enforced by local authority environmental health, require a venue to be able to tell a guest which of the fourteen listed allergens appear in every dish it serves. Food made on site and sold in its own sealed pack, such as a sandwich from a chiller cabinet (prepacked for direct sale, or PPDS), falls under Natasha's Law, the Food Information (Amendment) (England) Regulations 2021, which requires full ingredient labelling on the pack itself. "Ask the staff" is not a system if the online menu makes no reference to allergens at all, because a guest deciding whether to book cannot ask anyone yet. The common failure is an allergen note buried in a PDF nobody has opened since the menu was last printed. The check: open the online menu and see whether each dish states, or clearly links to, its allergen information. A venue should verify its own obligations with its local authority environmental health team or the Food Standards Agency's allergen guidance, since what counts as PPDS and how the fourteen allergens must be declared can depend on exactly how a dish is prepared and sold.
Loading fast on a phone at a bus stop
A homepage that takes ten seconds to load on patchy mobile data has usually already lost the guest standing at the bus stop deciding where to eat. The common failure is a homepage built around a full-screen video or a slideshow of unoptimised photographs, each taken straight off a camera without ever being compressed for the web. A page built to become usable within a couple of seconds on a slow connection keeps that guest on the site long enough to see the menu and the booking button. The check: switch off wifi, load the site on mobile data somewhere the signal is poor, and time how long the homepage takes to settle. If it is still loading a photograph after five seconds, something on that page needs to shrink.
Telling the truth about what the venue is
The website's description of the venue sets a guest's expectations before they arrive, and a mismatch between that description and the room they walk into is the fastest way to lose a repeat booking. This covers plain matters such as whether the venue holds a licence for live music or late opening under the Licensing Act 2003, and whether the accessible entrance the site describes is actually kept clear. It also covers the website itself: the Equality Act 2010 and the WCAG 2.1 accessibility standard set out what good practice looks like for a guest using a screen reader or navigating by keyboard, and a site that fails basic contrast or leaves images without text alternatives is making a claim of welcome it cannot back up. What the Equality Act specifically requires of a given venue's site sits outside what any checklist can tell you, and is worth checking against the venue's own legal advice. The check: read the site's own description of the venue against what a guest actually finds on arrival, line by line, and fix whichever one is wrong.