If you run a restaurant, your website has one job. Get people to book a table or walk through the door. Not to win a design award. Not to tell the story of how you fell in love with Italian food in Siena in 1998. Get them in.
Most restaurant websites fail at this because they're built around what the restaurant owner finds interesting rather than what a hungry person on their phone at 7pm needs.
Let's fix that.
The reality: 80%+ of restaurant searches happen on mobile
Before we talk about anything else, understand this: the person searching for your restaurant is almost certainly on their phone. They're hungry, they're deciding between you and three other places in the area, and they've got about 30 seconds of patience.
If your website takes more than three seconds to load on a phone, they've gone. If they can't find your menu, they've gone. If the menu is a PDF they have to download and pinch to read, they've gone.
Mobile isn't a version of your website. It's the primary version. If you build a beautiful desktop experience and treat mobile as a scaling exercise, you're building backwards.
Test this yourself. Get your phone out right now and open your website. Don't use your own wifi — switch to mobile data. Time how long it takes to load. Try to find your menu. Try to make a booking. Count the taps it takes. If the experience frustrates you even slightly, it's killing bookings.
The menu must be HTML, not a PDF
This is the single most common and most damaging mistake restaurant websites make. The menu is a PDF. Either a link to download it, or an embedded viewer that loads slowly, renders badly on mobile, and is completely invisible to search engines.
Why does this matter so much?
SEO. Google can't index the content of your PDF menu. That means your dishes, your cuisine style, your dietary options — none of it contributes to your search visibility. A competitor with an HTML menu that mentions "gluten-free pasta" or "halal certified" or "vegan tasting menu" will outrank you for those searches. You won't even know you're losing the traffic.
User experience. PDFs on mobile are horrible. They require downloading, they don't reflow properly for small screens, the text is often illegible without zooming. "Easy to read PDF" does not exist on a 5-inch screen.
Updating. Many restaurants say they use PDFs because they're easier to update. The opposite is usually true. Updating a CMS-managed HTML menu takes two minutes. Generating a new PDF, uploading it, updating the link — that's five or ten minutes of faff, which is why restaurant menus are so often months out of date.
Your menu should be a proper HTML page. Each section — starters, mains, desserts, drinks — with clear headings. Dietary symbols (V, VG, GF) visible and explained. Prices listed. Updated seasonally or whenever it changes.
This single change can meaningfully improve your organic search rankings.
Google Business Profile: your most important local SEO tool
Before we even talk about your website, let's talk about Google Business Profile (formerly Google My Business). For restaurants, it is the most important digital marketing tool you have. Full stop.
When someone searches "Italian restaurant Shoreditch" or "Sunday roast Harrogate", Google shows a map pack at the top of the results. Three businesses with photos, ratings, hours, and a booking link. If you're not in that map pack, you're invisible to a massive proportion of intent-ready searches.
Your Google Business Profile needs:
Accurate, complete information. Name, address, phone number, website URL. These must exactly match what appears on your website. Inconsistency confuses Google and reduces your ranking.
Opening hours — kept current. Including special hours for bank holidays, Christmas, Easter. There is nothing more damaging than Google telling someone you're open when you're closed. They turn up, you're shut, they leave a one-star review. Update your hours.
Photos — lots of them, added regularly. Google surfaces businesses with more and newer photos higher in local search. Add 10–20 good photos of food, interior, exterior, and team. Then add new ones monthly. This isn't bureaucratic busy-work — it directly affects visibility.
Respond to reviews — all of them. Positive reviews get a brief, genuine thank-you. Negative reviews get a thoughtful, professional response that acknowledges the issue without being defensive. Restaurants that respond to reviews rank better and convert searchers better. Reviews with no responses look abandoned.
Use the menu feature. Google Business Profile has a menu section. Fill it in. It surfaces in Knowledge Panel searches and is another way your dishes become searchable.
Getting your Google Business Profile right is free, takes a few hours to do properly, and can dramatically increase foot traffic. It's where we start with local SEO for restaurant clients.
Booking integration: which system to use
Online booking is expected now. If you don't offer it, you're losing bookings to restaurants that do. People search at 10pm on a Tuesday when your phone isn't answered. They want to book then, right now, while the impulse is there.
The main booking systems used by UK restaurants:
OpenTable. The biggest. Excellent brand recognition — the OpenTable name is a trust signal for some customers. Discovery platform means diners actively searching OpenTable might find you. Downside: commission per seated diner (typically £1–£1.50 per cover) adds up significantly. If you're doing 1,000 covers a month, that's £1,000–£1,500 you're paying OpenTable every month.
ResDiary. UK-based, popular with independent restaurants and small groups. Monthly subscription rather than per-cover fees — more predictable cost. Integrates well with EPOS systems. Good waiting list management.
Collins (formerly Bookingbug). Strong in the UK, good for venues with events and private dining as well as restaurant bookings. Waitlist, pre-payment, deposits. More feature-rich.
SevenRooms. More enterprise-focused, popular with larger restaurant groups. Guest data and CRM are strong points.
Custom booking via your website. For very simple operations, a custom form that emails you is workable — but it requires manual management and doesn't hold deposits. Not recommended for busy restaurants.
Our recommendation: for independent restaurants, ResDiary or Collins offer the best combination of features and cost. OpenTable makes sense if you're in a market where OpenTable discovery matters. The commission model works against you as volume grows.
Whichever system you choose, the booking widget needs to be visible and accessible from your homepage, not buried somewhere. "Book a Table" should be a primary CTA in your header and repeated throughout the page.
What goes on the homepage vs what to bury
The homepage of a restaurant website is often over-engineered. Story of the restaurant, about the chef, philosophy of food, seasonal sourcing — all of this matters, but it's not what the person looking to book a table needs to see first.
Homepage must-haves, above the fold:
- What you are (Italian restaurant, pub with food, tasting menu, Sunday roast — be specific)
- Where you are (area of city, specific address)
- "Book a Table" button
- One compelling food photo or short video
That's it. Everything else scrolls below.
Below the fold:
- Brief menu preview or link to full menu
- Opening hours
- Brief "about us" (2–3 sentences)
- Customer reviews (Google review widget or selected quotes)
- Location map embed
- Contact details and phone number
Separate pages for:
- Full menu (and keep it updated)
- Private dining / events
- Full about page / chef story
- Gallery
The chef's story and the sourcing philosophy are valuable for customers who are already interested and want to know more. They shouldn't be the first thing someone sees when they're trying to find out if you're open on Sunday.
Photography: it matters more here than anywhere else
You're selling an experience before someone tastes anything. Food photography is your sales team.
Bad food photography destroys trust. Flat lighting, amateur composition, dishes that look grey and unappetising — this is actively worse than no photography. It makes the food look bad even when the food is excellent.
Good food photography does the opposite. It creates desire. It makes people hungry. It convinces them that booking this restaurant tonight is the right decision.
The investment in a half-day with a proper food photographer is £400–£800 and produces images that will serve the website for 1–2 years. That's £5–£15 a week. If it brings in one extra booking a week at £40 average spend, it's paid for itself in a month.
Requirements for restaurant photography:
- Professional lighting — natural light where possible
- Hero shots of signature dishes (3–5)
- Interior atmosphere shots showing the dining space
- Exterior shot showing the frontage (customers use this to find you)
- Team shot if your team is a selling point
Video is increasingly valuable. A 30-second clip of kitchen activity, dishes being plated, the atmosphere on a busy evening — this converts browsers into bookers. Short-form video shot on a modern iPhone can be entirely sufficient.
Schema markup: the technical element most restaurants ignore
Schema markup is code added to your website that tells search engines explicit information about your business in a structured format. For restaurants, this means:
- Restaurant name, address, phone number
- Cuisine type
- Opening hours
- Price range (£, ££, £££)
- Menu URL
- Reservation URL
- Accepted payment methods
When done correctly, this information appears directly in Google Search results — opening hours shown in the SERP, price range displayed, booking link surfaced. Google can show rich results for restaurant searches when schema is implemented properly.
This isn't complicated to implement, but it does require someone who knows what they're doing. Most restaurant websites don't have it. Those that do have a visible advantage in search results.
Our SEO work for restaurant clients always includes schema implementation as a foundational step.
Local SEO for restaurants: the full picture
Beyond Google Business Profile and schema, local SEO for restaurants involves:
Consistent NAP (Name, Address, Phone) across all platforms. Your details on your website, Google Business Profile, TripAdvisor, Yelp, OpenTable, and any other listings need to be identical. Different formats or old phone numbers create citation inconsistency that harms local ranking.
TripAdvisor and other review platforms. Keep your profile updated, respond to reviews, add photos. These platforms have their own search visibility and feed back into Google's local ranking signals.
Local content. Blog posts or pages that reference your neighbourhood, local suppliers, seasonal menus tied to local events — these create local relevance signals. "Best restaurant in [area]" content that's genuine and specific performs well in local search.
Backlinks from local sources. Coverage in local food blogs, local newspapers, local business directories — these links tell Google you're a real part of the local community.
Common disasters we see on restaurant websites
Flash or animated menus from circa 2010. We still see these. They don't work on mobile, they're completely inaccessible, and they're baffling to anyone under 25.
Unoptimised images making the site unbearably slow. A 6MB hero image of a beautifully plated dish is a 15-second load time on mobile. Compress your images. WebP format. Responsive sizing. This is non-negotiable.
No online booking. "Call us to book." Fine if you're a Michelin-starred restaurant with a 6-month waiting list. Disastrous if you're a neighbourhood bistro competing with five other places within walking distance.
The phone number hidden or absent. It should be in the header. Always. Especially on mobile. Some people — particularly older diners — will always prefer to call. Make it a tap.
Seasonal menu unchanged since February. If your menu has changed and your website hasn't, you're advertising dishes you don't serve. That's a trust issue and a customer service issue.
Opening hours not updated for bank holidays. Already mentioned. Worth repeating. Update your hours.
Google Maps embed that doesn't work. Test it. Make sure it loads and the pin is in the right place.
What a good restaurant website costs
You don't need to spend a fortune. But you do need to spend enough to do it properly.
A well-built restaurant website — proper mobile design, HTML menu, booking integration, schema markup, local SEO basics, good photography — from a competent web design agency typically costs £2,500–£6,000.
That's not a small number for an independent restaurant. But consider: one additional booking per day over a year, at £40 average spend, is £14,600. If a proper website generates that (and a well-built site for a good restaurant absolutely should), the ROI is clear.
The websites that don't deliver results aren't typically the expensive ones. They're the cheap ones that missed the fundamentals.
If your restaurant's current website isn't generating consistent bookings, the problem is almost always fixable. And fixing it is almost always worth it. Talk to us about what that would look like for your specific situation.
For more on what outdated websites cost businesses in concrete terms, read our post on old websites losing you business — the principles translate directly to restaurants.