Restaurant Website Essentials That Actually Fill Tables
What a restaurant website needs to turn searches into bookings: menu, hours, booking, local SEO, fast mobile pages and structured data. A practical guide.
A good restaurant website answers four questions within seconds: what is on the menu, where you are, when you are open and how to book. Get those right, make them work on a phone with a patchy signal, and the rest of the site supports them. This guide covers what we build into restaurant sites and why.
What a hungry visitor needs in the first 10 seconds
Someone searching for somewhere to eat is usually deciding right now, often on a phone, often outside. They are not looking for your story. They want to know whether you are open, whether there is a table and whether the food looks right for them.
Your homepage, without scrolling, should show:
- Your name and cuisine in plain words, such as “Neapolitan pizza in Leeds”, not a vague tagline.
- Opening hours for today, including any bank holiday changes.
- A visible Book a table button (and an Order button if you offer it).
- Your address with a tap-to-open map link, and a tap-to-call phone number.
- A clear link to the menu, not hidden in a hamburger menu three levels deep.
- One strong photograph of the food or the room.
Everything else, such as your history, chef bio and press mentions, can sit lower down or on its own page. If you want to see how we approach this, our restaurant website design service starts from exactly this list.
Why PDF menus hurt you
A PDF menu is easy to produce, which is why so many restaurants use one. It is also one of the most common problems we see.
- They are awkward on a phone. Visitors wait for a download, then pinch and zoom to read tiny text.
- They are hard for search engines to use. Dish names and ingredients inside a PDF rarely help you appear for searches such as “vegan brunch” or “Sunday roast”.
- They are poor for accessibility. Screen readers often struggle with scanned or design-heavy PDFs.
- They go out of date. An old PDF cached by Google, or shared on social media, can show last year’s prices.
What to do instead
Build the menu as a normal web page with real text, grouped under clear headings (Starters, Mains, Desserts, Drinks). Keep prices as text, mark dietary information clearly, and make the page quick to scan. If you change the menu seasonally, update the page rather than uploading a new file. A print-friendly PDF can still exist as a secondary download, but it should never be the only version.
Reservation systems and their trade-offs
There is no single right answer here. It depends on how many covers you do and how much admin you want to carry.
| Option | Good for | Watch out for |
|---|---|---|
| Dedicated platforms (OpenTable, ResDiary and similar) | Busy venues that need table management, reminders and no-show controls | Subscription or per-cover fees; the platform’s branding and its own marketplace can compete with your site |
| Simple booking form on your site | Smaller venues, cafes, family-run restaurants | You manage the diary yourself; double bookings are possible without discipline |
| Phone and email only | Very small places with regular customers | Nobody can book when you are closed or in the middle of service |
Check current pricing and terms directly with each provider, as they change. Whichever route you choose, put the booking button in the header, on the homepage and on the contact page, and make sure it still works on mobile. If you use a simple form, send a confirmation email so guests know the request arrived.
Direct ordering versus third-party delivery
Delivery apps bring visibility and drivers. They also charge commission on every order, and you do not own the customer relationship. Over a year, that can be a significant cost, so it is worth looking at your own agreement and working out what you actually keep per order.
Ordering through your own website avoids marketplace commission, but you are responsible for:
- Payment processing fees (these still apply, though they are usually lower than marketplace commission).
- Delivery, either with your own drivers or a courier service.
- Getting people to your site in the first place.
A common middle path is to stay on delivery apps for discovery while encouraging repeat customers to order direct, for example through a clear “Order direct” button on your site, your Google Business Profile and a flyer in the bag. Collection orders are often the easiest place to start, because you do not need drivers.
Photography that sells the room and the food
Photos do more persuading than copy on a restaurant site. A few rules we follow:
- Show real dishes and your real room. Generic stock photos of someone else’s food are easy to spot and disappoint when the plate arrives.
- Show the atmosphere. Many guests are booking an evening, not just a meal. Include a shot of the dining room at the time of day when you are busiest.
- Shoot in natural light where you can, and photograph food soon after it leaves the pass.
- Show people and staff if you are comfortable with it, with their agreement.
- Compress properly. Large photos are the main reason restaurant sites load slowly (more on that below).
A short, well-chosen gallery beats a huge one. Give every image sensible alt text, such as “Slow-cooked lamb shoulder with seasonal greens”, which helps accessibility and image search.
Google Business Profile and local search
For most restaurants, local search starts with Google Maps and the local results, not the website. Your Google Business Profile deserves as much attention as your homepage.
- Make sure your name, address and phone number match your website exactly.
- Choose accurate categories, such as “Italian restaurant”, and add secondary ones where they apply.
- Keep opening hours current, and set special hours for bank holidays and private events.
- Add your menu link, booking link and order link.
- Upload your own photos regularly.
- Reply to reviews, good and bad, politely and promptly.
Your website supports this by having a clear page for each location, mentioning the area you serve, and being easy to crawl. If you want a wider look at how local visibility works, our post on local SEO for tradesmen covers principles that apply to restaurants too, and our SEO services page explains how we approach it. No one can promise a particular ranking, but accurate, consistent information gives you the best foundation.
Structured data for menus and opening hours
Structured data is code in the background of your page that tells search engines exactly what your content means. For restaurants, the useful schema.org types and properties include:
Restaurant(orCafeOrCoffeeShop,BarOrPub) for the business itself.address,telephoneandgeofor location.openingHoursSpecificationfor regular hours, plus special dates.servesCuisineandpriceRange.hasMenupointing to your menu page, andacceptsReservationspointing to your booking link.
Structured data does not guarantee special treatment in search results, and Google decides which features to show. Used correctly, though, it removes ambiguity and keeps your details consistent. It must match what is visible on the page, so update it whenever your hours or menu change.
Events and private dining pages
Private dining, Christmas parties and celebrations are often your highest-value bookings, yet many sites bury them in a footer link. Give them their own pages:
- Private dining: capacity, room photos, sample menus, minimum spend if applicable, and an enquiry form asking for date, group size and budget.
- Events: a dated, up-to-date list with a booking link for each. Remove past events promptly, as an outdated events page looks neglected.
- Gift vouchers if you offer them.
Each page targets different searches, such as “private dining room in [town]”, and gives you a natural place to collect enquiries.
Mobile speed on a poor signal
Diners often check your site from the pavement, on a train or inside a building with weak reception. A heavy page that takes ages to appear will be abandoned.
The usual fixes are straightforward: properly sized, compressed images; no auto-playing background video; fewer third-party scripts; and a fast host. Test on a real phone with mobile data turned on, not just on office Wi-Fi. If your current site is built on a heavy theme, a lean rebuild is often more effective than patching, and our WordPress website design work focuses on speed from the start.
Accessibility and dietary information
Accessible sites are better for everyone, including diners with visual or motor impairments and anyone using a phone in bright sunlight.
- Use sufficient colour contrast, and avoid text over busy photographs.
- Make buttons large enough to tap and fields easy to complete.
- Provide alt text for images and real text for menus.
- Label dietary information clearly (vegetarian, vegan, gluten-free) using plain words as well as symbols.
- Include an allergen statement and tell guests how to flag allergies when booking. Allergen rules in the UK are strict, so make sure your information is accurate and that your team can answer questions in person.
Next steps
If you would like to know how your restaurant website measures up, we offer a free website audit covering your menu, booking flow, mobile speed and local search basics. Get in touch through our contact page, message us on WhatsApp at +44 7460 610320, or email hello@webygrowth.com, and we will tell you plainly what we would fix first.
Related service
Restaurant Website Design
Appetising, mobile-first websites that fill tables for restaurants and cafés.