- The menu needs to be genuinely readable on a phone, not a scanned PDF.
- Hours, location, and a booking link need to be visible without scrolling.
- Photography of actual dishes outperforms stock imagery by a wide margin.
The menu page: your most important page
For most restaurant sites, the menu is the single most-visited page, and it's where the biggest, most common mistake shows up: a PDF menu, often scanned or exported from a design tool, that's slow to load and painful to read on a phone. A proper HTML menu page — text you can actually zoom and scroll normally, not a fixed image — loads faster, reads better on mobile, and is the version search engines can actually index, which matters for showing up when someone searches a specific dish or cuisine type.
Beyond format, keep the menu current. An outdated menu, whether wrong prices or dishes that no longer exist, damages trust the moment a customer notices the mismatch in person — worse than not having a menu online at all.
What needs to be visible immediately
A visitor deciding whether to come in, or where to book, needs four things instantly, without scrolling or hunting: current opening hours (and clearly flagged if hours differ today, for a bank holiday or similar), the address with a map, a phone number, and a clear path to book a table if you take reservations. Burying any of these below a scroll or inside a secondary menu item is a common, avoidable reason someone picks a competitor instead.
Reservations and ordering
If you take reservations, link directly to whatever booking system you already use rather than routing everything through a generic contact form — the fewer steps between "I want a table" and a confirmed booking, the better. The same logic applies to online ordering for takeaway or delivery: a direct, prominent link to your ordering platform beats a buried mention in body text.
Photography that actually sells food
Real photos of your actual dishes, well-lit and reasonably current, do more to convert an undecided visitor than any amount of descriptive copy. Stock food photography is easy to spot and tends to undercut trust rather than build it — visitors can generally tell, and it raises the question of what else on the page might not be accurate. A modest number of genuinely good photos of real dishes outperforms a large gallery of generic ones.
Local search: where most restaurant traffic actually starts
A large share of restaurant discovery happens through "restaurants near me" or cuisine-plus-location searches, decided largely from the Google Maps pack before someone ever reaches a website. That makes a complete, actively maintained Google Business Profile — accurate hours, menu links, photos, and responded-to reviews — arguably as important as the website itself. See our local SEO guide for the full detail on how this works together with the site.
Mobile speed matters more here than almost anywhere
Someone deciding where to eat right now, standing outside or scrolling between options, won't wait for a slow page to load — they'll simply move to the next result. Heavy, unoptimised photography is the most common cause of a slow restaurant site, which makes image compression and fast loading a genuine business priority here, not just a technical nicety.
Dietary information and accessibility
A growing share of diners check for allergen and dietary information before choosing where to eat, and having this clearly available on the site — rather than only available by asking staff on arrival — removes a real barrier for a meaningful segment of potential customers. It's also a legal requirement in the UK to provide allergen information for food sold, so a clear, accurate summary alongside the menu serves both a compliance purpose and a genuine conversion one; the Food Standards Agency's allergen guidance is worth reviewing when preparing this.
Events, private hire, and seasonal menus
If you host events, offer private hire, or run seasonal menus (a Christmas set menu, a summer terrace offering), these deserve their own clear space on the site rather than being mentioned only in passing — they're often higher-value bookings than a standard table and are frequently planned well in advance, giving a website more time to actually influence the decision than a same-day dinner choice would. A simple dedicated page or section, updated seasonally, captures this demand at the point people start planning.
Reviews and reputation
Restaurant decisions are unusually review-driven compared to many other small business categories — a potential diner will often check reviews as a near-automatic step before booking or visiting. Genuine, recent reviews mentioning specific dishes or aspects of the experience carry real weight, and responding professionally to any negative reviews (acknowledging the issue, not being defensive) matters as much here as anywhere, since a public, gracious response is itself visible to every future reader deciding whether to book.
Group bookings and larger parties
Larger group and party bookings are often higher value and more time-sensitive than a standard table, and a clear, easy-to-find path for them — a dedicated section explaining any group booking process, minimum notice, or deposit requirements — captures this demand properly rather than forcing an organiser to phone and ask basic questions that could have been answered on the page. This matters particularly around predictable peaks: Christmas, Valentine's Day, graduation season.
Delivery and takeaway platforms versus your own site
Third-party delivery platforms bring real reach but usually take a significant commission per order, which makes a direct, well-presented ordering path on your own site genuinely valuable for repeat customers who already know and like you — worth actively encouraging existing customers toward your own ordering link rather than leaving every order to go through a platform taking a cut. The two aren't mutually exclusive: platforms for new customer discovery, your own site for retaining and rewarding existing ones.
Seasonal hours and one-off closures
Hospitality hours change more than most business types — bank holidays, early closures for private events, seasonal trading patterns. An out-of-date hours listing is a specific, common source of a frustrated wasted trip, which damages goodwill disproportionately given how easily avoidable it is. Keeping both the website and your Google Business Profile updated for any temporary change, ideally as a standing habit rather than an occasional afterthought, prevents this entirely predictable problem.
Sourcing and provenance
Where sourcing is genuinely part of your story — local suppliers, particular provenance, a specific culinary tradition — this is worth telling properly rather than mentioning in passing, since increasingly diners actively look for and value this kind of detail when choosing where to eat. A short, honest section covering this (not overstated marketing claims about sourcing that isn't actually distinctive) adds real substance to an About section that otherwise risks being generic.
Atmosphere: showing, not just telling
Diners are often choosing an experience as much as a meal, and photos or short video of the actual space — genuinely representative, at a realistic time of day rather than an empty, artificially staged shot — help someone picture themselves there before booking. This matters especially for occasions like a date, celebration, or family gathering, where the atmosphere is as much a factor in the decision as the food itself, and it's an area where real, current photography consistently outperforms professionally staged but unrepresentative imagery.
Accessibility for a wider range of guests
Practical accessibility information — step-free access, accessible toilets, space for a wheelchair or pushchair, outdoor seating availability — is frequently what decides where a group with mixed needs actually chooses to eat, and it's information that's often missing from restaurant websites entirely. Including it plainly, even in a short list, removes real uncertainty for exactly the guests most likely to need that reassurance before committing to a booking, and is a small addition that consistently pays for itself in goodwill.
Should my menu be a PDF or a proper web page?
A proper HTML page, not a PDF. It loads faster, reads better on mobile, and can actually be indexed by search engines — a scanned or exported PDF menu is one of the most common, avoidable mistakes on restaurant websites.
What should be visible without scrolling on a restaurant homepage?
Opening hours, address, phone number, and a clear path to book or order — the four things someone deciding where to eat needs instantly.
Do I need professional food photography?
Not necessarily professional, but it needs to be real and reasonably current. Genuine photos of actual dishes consistently outperform stock imagery, even when the stock photos are technically higher quality.
Is a Google Business Profile more important than the website for restaurants?
It's at least as important — a large share of "restaurants near me" decisions are made directly from the Maps pack before someone clicks through to a site at all. See our Google Business Profile guide.
Should I build online ordering into my own site?
For most small restaurants, linking prominently to an established ordering platform is simpler and more reliable than building custom ordering functionality from scratch.
How often should I update my menu online?
Every time it changes in the restaurant itself. An outdated online menu — wrong prices or discontinued dishes — damages trust the moment a customer notices in person, which is worse than the inconvenience of updating it.
Pair your site with a fully optimised Google Business Profile — for most restaurants, that combination decides more bookings than the website alone.