Restaurant Website Design: Menus, Bookings and Local Discovery

What is someone looking for at seven in the evening?

Picture the visitor honestly. She is in an auto, or on the pavement outside, or arguing with four friends in a group chat, with your website open on a phone with one bar of signal. She wants four things: what the food is and whether there is something for everyone, roughly what it will cost, whether you are open and where exactly you are, and whether six people can get a table at eight.

Everything else — the chef’s training, the sourcing, the photograph of the wood-fired oven arriving on a truck — matters, and it matters after those four answers. Most restaurant websites reverse the order, opening with a full-screen video and a scroll prompt while the menu hides behind a hamburger icon.

Why the menu should be pages, not a PDF

The PDF menu is the most common fault in restaurant websites, and the most quietly expensive. It downloads, opens in another app and arrives laid out for a sheet of A4, so the reader is left pinching and dragging across a page designed for a printer. WCAG 2.2 asks, at Level AA, that content reflow without loss of information or functionality and without scrolling in two directions at a width equivalent to 320 CSS pixels. A fixed A4 layout fails that by design.

Pages also let the menu keep up with the kitchen. Prices change, a supplier fails, the tasting menu is rewritten in July. On web pages, someone in the restaurant edits a line before service. In a PDF, that means finding the designer and re-exporting the file, which is why so many menus online are a year old.

Structure it the way the printed menu is structured: sections in the order people eat, dish name as the kitchen says it, one honest line of description, and the price. Photograph a few dishes rather than all of them; a half-lit picture of every item does more harm than none.

Prices, dietary marks and what the regulations expect

Show the prices. A menu without prices asks people to telephone and ask, and most of them will simply choose somewhere else. If prices move often, date the menu rather than hiding the numbers, and say whether taxes are included so nobody is surprised by the bill.

India’s food regulations are specific about menus. Under the Food Safety and Standards (Labelling and Display) Regulations, 2020, food service establishments must mention, against the food items displayed on menu cards or boards, information relating to food allergens — which “may be depicted by easy to understand symbols” — and the logo for veg or non-veg. Establishments holding a central licence, or with outlets at ten or more locations, must also show the calorific value in kcal per serving with the serving size, together with the line “An average active adult requires 2,000 kcal energy per day, however, calorie needs may vary.” The regulations exempt some cases, including premises operating for fewer than 60 days in a year and items modified at a customer’s request.

• The dish name the kitchen and the servers actually use.
• One honest line of description, not three adjectives.
• The price, and whether taxes are included.
• Veg or non-veg marking, and allergen symbols with a key.
• Spice level where it genuinely varies between dishes.
• A note where a dish takes twenty minutes or is limited to a few portions.

A booking flow your team can actually keep

There are two honest designs. The first is live availability, where the site holds real tables and confirms immediately. The second is a request: “Send us the details and we will confirm on WhatsApp within the hour, between 10 am and 6 pm.” The dishonest third design is the one most restaurants have — a form that looks like a booking, produces a cheerful confirmation screen and is in fact an email nobody reads during service.

Ask for the date, the time, the number of guests, a name and a phone number, the occasion if there is one, and a single free line for anything else: a wheelchair, a high chair, a cake, a table away from the speakers. Nothing more. Then repeat the details back and say what happens next, including what to do if plans change.

Our fictional EMBER restaurant concept shows the shape of it: guests, a time, a prepared request, and a line stating plainly that no reservation has been made. On a working site, that last line is where you name who confirms and how quickly. When requests outgrow one person’s phone, the capture and follow-up can be handled as a workflow — our guide to automating customer enquiries covers where a person should stay in it.

Hours, location and the details people check last

Hours are the detail most often wrong and most costly when it is. Publish them per service, with the last kitchen order, and treat the exceptions as content: the weekly off, festival closures, the Sunday brunch that stops during the monsoon.

Location needs the same care in Indian cities, where an address is rarely enough. A map pin on the block is not a map pin on the entrance, and a landmark line saves a driver two phone calls.

• Opening times by service, with the time the kitchen stops taking orders.
• Weekly off, festival closures and any special hours.
• A map pin on the entrance, plus a landmark line for drivers.
• Parking, valet and the nearest metro station or bus stop.
• A tappable phone number, and someone who answers it during service.
• Access stated plainly: steps, a lift, an accessible toilet.

Keeping Google and your website telling the same story

Many people never reach your website first. They see the Business Profile in Search or Maps, and decide from that. Google says local results are based on relevance, distance and prominence, and states plainly that there is no way to request or pay for a better local ranking. What it does recommend is within your control: verify the business, keep the information complete and current, including your full address and special hours, respond to reviews, and add photographs.

Consistency is the part a website can help with. Google’s guidelines for representing your business ask that your name reflect your real-world name as used on your storefront, website and stationery, that you use a precise, accurate address, and that you provide your regular customer-facing hours. Your website is where a customer goes to check all three. Mismatches are what leave someone standing outside a closed door on a Tuesday.

The profile can carry the menu too. Google’s menu editor lets food and drink businesses list items with descriptions and prices, grouped into sections, and changes can take 24 to 48 hours to appear on Maps and Search. Keep it in step with the site, and point the profile’s menu link at your menu page rather than at a PDF.

Photographs, events and private dining

Photograph the room at the hour people visit it, not at three in the afternoon with the lights off. Photograph a few dishes as they are actually plated, by the person who plates them, in consistent light. Photograph the staff. Stock images of pasta and generic candlelit tables are the fastest way to look like every other listing, and diners have learned to distrust them.

Private dining and events deserve a page that answers what an enquirer would otherwise send in three emails: how many people seated and standing, whether the space is exclusive, whether there is a minimum spend and what it is, sample set menus with prices, whether an outside cake is allowed, and who to contact with a phone number and a realistic reply time. Put it in text on the page. A PDF that has to be requested loses the enquiry to the restaurant that published its numbers.

Delivery links, mobile care and what to measure

If you are on delivery platforms, link to them clearly and keep the links working; a dead link to a closed listing is worse than none. If you take direct orders, state the area, the timings and the minimum order. Keep the delivery invitation below the table-booking one if the room is what you would rather fill.

Then read the whole site on a phone, standing up, with one thumb. Tap targets that are comfortable, a phone number that dials, a menu that loads on a mobile network in a basement, and nothing covering the page before a word has been read. Our guide to mobile website experience goes further into the details.

A restaurant site is small and unforgiving: eight pages, four questions, one impression made in ninety seconds. That is the kind of brief our Website Design & Development work is built for, from the menu structure and the booking flow to the visual direction and the launch checks, with your team reviewing the journeys before anything goes live.