HOSPITALITY
Someone two streets away, hungry, on their phone, gets your menu and your booking form in one tap — instead of giving up on a PDF and eating somewhere else.
Short answer
A restaurant website needs four things a hungry person can get in seconds on a phone: the full menu as real web text and never a PDF, today's opening hours including public holidays, where you are with parking, and a way to book a table or order directly. Photos of the actual food do the rest.
They are on a phone. They are often already nearby — sitting in a car outside the centre, or standing on the pavement with three other people deciding. And they want four answers, in this order, in under a minute.
What's on the menu, and what does it cost? This is the first tap, every time. They are checking two things at once: is there something here I actually want, and is this place in my budget tonight. If the menu takes more than a couple of seconds to appear, or arrives as a document they have to zoom into, a good share of them leave right there.
Are you open right now? Long weekends are where restaurants lose people. Someone checks on a Monday of a public holiday, sees hours that are clearly generic, doesn't trust them, and phones a place that says plainly "open today until 21:00". Load shedding makes this worse — if stage 4 changes your kitchen hours or your last order time, that has to be visible on the site, not just posted to Instagram Stories that expired yesterday.
Where exactly are you, and where do I park? "Off Main Road" is not an address. They want a map pin that opens Google Maps in one tap, and a straight answer on parking, because in a lot of suburbs that is the deciding factor.
How do I book or order? A table for six on Saturday, or a large pizza in the next forty minutes. Both should be one tap. If the booking path is an email address and the order path is nothing, they go to the app instead and you pay commission on a customer who was already looking at your website.
The menu is a PDF. It downloads instead of opening, it comes up sideways, and the customer is pinch-zooming to read the starters one-handed. This is the single most common thing that kills a booking in this niche.
A menu built as normal web text — sections you can jump to, readable at arm's length, loads instantly on a bad 3G signal, and Google can actually read the dishes in it.
Hours are out of date or vague. Over Easter, 16 June or the December stretch, nobody knows if you're open, so they don't risk the drive.
Live hours that state today's status in plain words, with public holiday exceptions you set in advance and a load shedding note when your kitchen hours shift.
No booking path. Just a phone number that goes unanswered during service, so a table of eight books somewhere that let them do it at 23:00 from bed.
A booking form taking date, time, party size and any occasion note, landing in the inbox and on WhatsApp so the floor manager confirms in a minute.
Everything routes through Mr D and UberEats, so you're paying commission on every single order — including from customers who found you, typed your name into Google and came to your own site first.
A direct order path front and centre with the delivery apps kept as a secondary option, so the customers already looking for you by name order at full margin.
Never a PDF. Sections for starters, mains, grills, sides, desserts and drinks, jumpable from the top. You change a price, mark a dish 86'd or add tonight's special from your phone in under a minute.
Today's hours stated in words, per-day listings, public holiday overrides set ahead of time, and a slot for a load shedding notice when the kitchen closes earlier than usual.
Date, time, party size, occasion, dietary note. Straight to the inbox and WhatsApp so someone confirms while the customer is still deciding, plus a clear line about walk-ins and large groups.
A collection or delivery order that comes to you at full margin, with Mr D and UberEats linked underneath for the customers who insist on their apps. Every direct order is money you were handing over.
Your actual plates, shot and sized properly so they load fast on mobile. No stock photos of a burger nobody in your kitchen has ever made — customers spot it immediately and it costs you trust.
A private bookings enquiry for birthdays, year-ends and rehearsal dinners, your licensed or BYO status stated up front with corkage, plus parking, wheelchair access and whether the venue is child-friendly.
Most of your discovery happens on Google Maps, not on Google's blue links. Somebody types "pizza near me" or "steakhouse Sandton", scans the map results, and picks from photos, star rating and whether the place looks open. Your Google Business Profile is doing that work, and the most under-used field in it is the menu link — pointing it at your live menu page means the dishes and prices are right there in the listing before anyone taps through. Our guide to getting a Google Business Profile right in South Africa covers the categories, the hours, the holiday overrides and the photo cadence, and for a restaurant it beats almost anything else you could spend an hour on.
Photos are the ranking and conversion lever most owners neglect. Profiles with recent, real food photos get materially more taps than ones with a single exterior shot from 2019. Post a few every month — the actual plates going out, not styled stock.
On the site itself, the menu page is your search asset. When your dishes are real text, you start appearing for the specific things people search: "prego roll Durbanville", "wood-fired pizza Greenside", "halaal steakhouse Fordsburg". A PDF gives you none of that. Add the suburb by name where it is true, keep a short page for functions and one for the Sunday lunch or the rib night if you run one, and let the reviews do the rest — replying to them, especially the bad ones, is read by every person deciding whether to book.
Because a PDF opens as a tiny page the customer has to pinch and drag around one-handed, it often downloads instead of opening, and Google cannot read the dishes inside it properly. A menu built as normal web text loads instantly on a phone, scrolls like everything else, and shows up when someone searches for a dish you serve.
We build the menu so you edit it, not us. Change a price, mark a dish sold out, add the Wednesday rib special or swap the winter menu in, from a phone if that is all you have. No design software, no waiting on a developer, no reprinting a PDF every time the beef price moves.
Yes. We build a direct order path that sends the order to your kitchen or WhatsApp with no commission taken off the top. The delivery apps still get a place on the site because plenty of customers prefer them, but the direct option sits first, and every order that comes through it is worth noticeably more to you.
It depends on the build. A single-site pizzeria that needs a menu, hours and a booking form is not the same job as a steakhouse with three branches, functions enquiries and direct ordering. Send us what you run through the quote form and we come back with one fixed number, free, before you commit to anything.
Tell us what you run — one site or three, sit-down or takeaway, delivery or collection — and we'll come back with a plan and a fixed quote. Free, and you'll know exactly what you're getting before you decide.
Get a free quote →