Restaurant website: a menu that reads well on mobile, table booking and delivery
Restaurant website: why an HTML menu beats a PDF, how to connect table booking and delivery, and when to take orders on your site, not only on platforms.

Your diners open your website on their phone and get a PDF menu they have to pinch to zoom? Building a restaurant website should start with the question of what the diner has come to do: see the menu, check whether you are open, book a table or order in. Some of that already happens in your table-booking system, in the delivery apps and on your Google Business Profile. So the website doesn't need to replace them; it needs to connect them and do what they don't. In this article we break down what has to be on the website, why an HTML menu beats a PDF, how to connect table booking and delivery, and when it is worth taking orders directly on your website.
What diners come to do on a restaurant website
A diner who visits a restaurant's website has usually not come to read about the concept. They have come to get a task done, so every task needs a button on the first screen. Most of these tasks already happen somewhere else, and the website needs to connect them:
| What the diner wants | Where it happens today | What the website does |
|---|---|---|
| See the menu | Instagram, your Google Business Profile, delivery apps | One up-to-date menu page that all of them link to |
| Know whether you are open | Your Google Business Profile | Exactly the same hours, holidays included |
| Book a table | A table-booking system, such as Ontopo | A button that leads to your page on that system |
| Order in | Wolt, 10bis | Buttons to the platforms, and perhaps direct ordering too |
| Ask about an event | Phone and WhatsApp | An events page with a form |
In our experience, the common mistake is a website that tries to replace everything: a booking calendar of its own, a menu that doesn't match Google, and hours that were last updated a year ago. A good restaurant website is the place where all the information is correct and the buttons lead to the systems you already work with. And one more thing: real photos of the dishes and of the place, not stock photos, at a size that suits mobile.
Restaurant website: an HTML menu, not a PDF

A PDF menu is convenient for the person who makes it, not for the person reading it on a phone. You have to pinch to zoom, scroll sideways, and sometimes wait for a download. On top of that, every price change needs a new file, so PDF menus tend to go out of date. A menu built as text inside the website page (HTML) adapts itself to the screen, is updated one dish at a time, and a screen reader can read it aloud. We set out what else making a website accessible involves in our guide to website accessibility.
This is how to build a menu page:
- Categories with quick jumps. Starters, mains, desserts and drinks, in a bar that stays at the top while you scroll.
- Name, short description and price. One line of description is better than a paragraph.
- Labels only when they are accurate. Vegan, gluten-free, spicy: a wrong label is worse than no label at all.
- One address for the menu. The same page serves the QR code on the table, the link on Instagram and the menu address on Google.
According to the Google Business Profile Help Center, a restaurant can manage its "menu URL" there, and can also use the menu editor to "create a detailed menu with sections, dishes, descriptions, and prices". If you use both, update prices in both places on the same day.
Table booking and delivery: connect, don't rebuild
If you already work with a table-booking system, the "Book a table" button on your website should lead straight to your page on that system. There is no point building a separate calendar: two calendars are a recipe for double bookings. Your Google Business Profile has table booking too: the same help centre says "Manage your Bookings and Waitlists directly on Google", through scheduling providers that Google supports. If you have a booking system, check whether it is among them.
The same principle applies to delivery: a button for every platform you work with, so the customer carries on in the app they already know.
And what about the commission? This is where it pays to be precise. The page for businesses on Wolt says: "A commission is charged on every order received through the platform, and the rest is yours", and also: "Wolt does not charge subscription fees, activation fees or cancellation fees", but "in certain cases and in certain areas, there may be a small charge for using the platform or for optional extras" (quotes from Wolt's Hebrew page, and from Israeli legislation further down, are our own translation of the Hebrew). The commission rate itself does not appear on the page, as of our check on 3 November 2026. So don't rely on percentages that circulate online. Compare according to your own agreement with each platform.
Direct orders on your website or through the platform: how to decide

This is the central decision, and it doesn't have to be either-or. The platforms bring customers who don't know you yet, and the website can serve your regulars, who already know what they want. To decide, answer four questions:
- Who delivers the order? Without couriers of your own, direct ordering starts with pickup.
- How many returning customers do you have? If most of your orders come from regulars, you have someone to offer direct ordering to.
- What does an order on the platform cost you? Work it out from your agreement, including any charges for optional extras.
- Does your POS support it? For example, according to Tabit, Tabit Order is based on the same items, prices and availability that are managed in Tabit's POS inside the restaurant, and you can link to it from your website. When the menu and prices come from the POS, there is no extra menu to maintain.
Our decision rule: if most of your orders come from regulars (question 2) and your POS supports direct ordering (question 4), try direct ordering for pickup and leave delivery on the platforms. If not, buttons to the platforms are enough. And if you are thinking of selling products, such as sauces or catering platters, that is already an e-commerce website, and we wrote about it in our guide to building an online store.
Hours, getting there, kashrut and events
Hours. The hours on your website should be identical to the hours on your Google Business Profile. According to Google's help page on special hours, "It's a good idea to confirm your hours for official holidays, even if they're the same as your regular hours." In addition, according to the help page for restaurants, you can set "more hours" on your profile "for specific services your business offers such as delivery, takeout, drive through and pickup". Show those hours on the website too, and before every holiday, update both places.
Getting there. Address, a button for Waze and for Google Maps, parking, and the accessibility of the venue. We explained how your profile, your reviews and your local pages work together in our guide to local SEO.
Kashrut. Section 3(a) of the Kashrut (Prohibition of Deceit) Law, 1983 (חוק איסור הונאה בכשרות) states: "The owner of a food establishment shall not present the food establishment in writing as kosher, unless a kashrut certificate has been issued to them." In our view, it is worth treating the text on your website as a presentation in writing in every respect. If you have a certificate, write who issued it, and update the text when the certificate is renewed or changes. If you don't have one, don't write "kosher". We are not lawyers, so consult a lawyer about any other wording.
Events and private functions. A separate page with a short form: date, number of guests, type of event, name and phone. A WhatsApp button with a pre-filled message works especially well here, as we explained in our guide to the WhatsApp button for your website.
Who this suits, and who it doesn't
A good fit:
- A restaurant whose menu changes, and which wants to update it in one place.
- A restaurant that takes table bookings and wants the booking button one click away from the menu.
- A restaurant that hosts events and private functions, and needs a place to take enquiries about them.
- A chain with several branches, which needs a page for each branch with its own hours and address.
Less of a fit:
- A stall or pop-up with a small menu. A Google Business Profile, Instagram and one menu page can be enough.
- A kitchen that sells only through delivery apps, with no seating and no pickup. A website will do little there, and the budget is better spent on the platform.
What Simple Web does about it
Simple Web is an AI-first marketing agency from Bnei Brak, certified Meta partners and Google advertising experts, working with 200+ businesses and holding 35 five-star Google reviews. We build with AI, and people on our team decide the structure, the messaging and the design. A brand website with us starts at ₪5,000, in a range of ₪5,000 to 15,000+ depending on scope, with a final price agreed up front. It includes the specification, content writing and SEO foundations, accessibility under Israeli law, and training so you can manage the website yourself, which means you can update the menu and the opening hours on your own. In the specification stage we define with you which buttons appear on the first screen and which systems they lead to. The website is ready within 3 months, depending on the size of the project, and includes 6 months of SEO content as a gift (worth ₪4,500) and 3 months of free warranty and fixes. If you are comparing quotes, we broke down what a website costs depending on who builds it.
Summary
A restaurant website works when it handles the visitor's tasks quickly: seeing the menu, knowing whether you are open, booking a table, ordering in and asking about an event. One HTML menu, hours identical to Google and buttons to the systems you already work with do most of the work. Direct ordering on your website is worth testing when most of your orders come from regulars and your POS supports it, and either way, it pays to compare according to your own agreement with the platforms. Want to plan your restaurant's website? Book a free diagnostic call with us.
Sources
- Google: Get started with a Business Profile for your restaurant (Hebrew version): the menu URL, the menu editor, bookings and waitlists, and more hours for delivery and pickup
- Google: How to set special hours (Hebrew version): the recommendation to set holiday hours, even when they are the same as your regular hours
- Wolt for Merchants (Israel, Hebrew): a commission on every order, which fees are not charged, and what may apply in certain areas (checked 3 November 2026)
- Tabit Order: online orders based on the menu and prices in Tabit's POS, and linking to them from your website
- Kashrut (Prohibition of Deceit) Law, 1983 (Wikisource, Hebrew): section 3(a): presenting a food establishment in writing as kosher only with a kashrut certificate
Tags:
Growth


