Restaurant and Cafe Website Guide: What Really Fills Your Tables

A restaurant website has one job: turn the person reading your menu on a phone into someone sitting at your table. Hungry people decide fast. If they cannot find the menu, see when you close or work out how to book, they are somewhere else two minutes later.

Your map listing and your site do different halves of the job

Most guests find you on a map, not on your website. A listing shows your name, rating, photos, hours and a link, and that is what makes you visible.

The decision happens on your site: whoever sees the listing checks the photos, then taps through for the menu and the prices. Keep the hours and the phone number identical in both places, because a guest who sees two different closing times trusts neither. Our Google Business Profile guide covers the listing itself.

The menu must be a page, not a PDF

The most common mistake is publishing the menu as a PDF or a photo. On a phone it loads slowly, forces pinching and dragging, and blurs when you zoom. Worse, search engines cannot read text inside an image, so nobody hunting for a vegan brunch or your best known dish will find you.

Publish it as a real page: categories, dish name, a short description, the price, all as plain text. It opens instantly, it can rank, and changing a price means editing one line. Vegetarian, spicy and allergen labels also become easy to add, and they answer questions before anyone flags down a server.

A QR menu at the table is not the menu on your site

Whoever scans the code is already seated and needs speed: a list that opens the moment the code is read, installs no app, downloads no PDF, and moves between categories in one tap. Marking a dish sold out belongs here.

The menu on your site is for the person still deciding whether to come, so it has to be findable in search and look right when the link is shared. Put one set of data behind both views: change a price once and the table QR and the website update together.

Booking and ordering

Do not force one route. Give people the one that fits their habit:

• Phone. On mobile the number must start a call when tapped. Usually the most visible button on the page.
• Messaging. Many guests would rather type than call, and a link that opens with a ready made message gets more replies.
• Booking form. Date, time, party size, name, phone and a note is enough. Send it to your inbox and your panel, confirm quickly, and ask only for what you need.
• Delivery platforms. If you do takeaway, link them, but below your own channels. They take a commission on every order; your own phone number does not.

Photos that sell your food, not stock food

Stock photography does particular damage in hospitality: the guest compares the plate in front of them with the picture, and the gap costs you trust.

You do not need expensive equipment. Daylight near a window, a plain surface, one angle, no heavy filter. Shoot your 8-10 best sellers, then the room: empty and set, busy in the evening, the terrace if you have one. People look at where they will sit as much as at what they will eat. Compress the files, or the page turns heavy on mobile.

Hours, address, parking and directions

These look like boring details and they are the most viewed part of the site. Put them on the page as text:

• Opening and closing times per day, and when the kitchen stops.
• The full address, a map, and a directions link that opens in one tap.
• Parking: valet or not, paid or free, which car park is nearby.
• How to reach you by public transport.
• What people actually ask: terrace, heating, dogs, high chairs, steps at the entrance.

Special nights and seasonal menus

Prices move, the summer menu arrives, a live music night gets added. If changing any of that means emailing an agency, the site freezes within two months and an old price stays published.

So the panel matters. Adding a dish, changing a price, marking something sold out and posting this week's note belong in your hands. For special nights, a dated event page gives you a link to share and a place to collect bookings.

Common mistakes

• The site living only in an Instagram bio.
• The menu as a JPEG, invisible in search.
• No address or opening hours anywhere on the site.
• Music or video that plays on load. Most visitors just close the tab.
• Thin script fonts, or pale grey text over a dark photo. A menu nobody can read is not a menu.
• A phone number as plain text that does nothing when tapped.
• Booking forms that land somewhere nobody checks.

The order is simple: publish the menu as text, make hours, address and the booking route obvious, then replace the photos.

At Oktoks a single page site starts at $500 + VAT and goes live in 1-2 business days; a full site with a menu, a gallery and a booking form is $1,200 + VAT in 1 week. Prices are published openly, every project comes with a management panel, and the source code belongs to you, so you update the menu yourself.

Tell us about your menu and your weekly rhythm through the quote form and we will say which one is enough.