WalkUp Digital
Industry guide

Restaurant website design: what a restaurant, taverna or café site should include

A restaurant website is read in a hurry, on a phone, by someone deciding where to eat tonight or on next month's holiday. It has to show the menu, the hours and the way there within seconds, in the visitor's language. This guide sets out what a site for a restaurant, taverna, café or beach bar needs, where most go wrong, and how it works alongside a digital menu at the table.

Do restaurants need a website if they are on Google Maps?

Many guests find you first on Google Maps, in search results or on Instagram. Those profiles matter and should be kept current, but they sit on someone else's platform, laid out as the platform decides, with photos and menus that guests can upload as well as you.

A website is the one place where you decide what is said and in which order: the full menu, the story of the kitchen, the way to book. It is where your Google profile sends people, and for a visitor planning a holiday from abroad it may be the only page about you in their own language. It does not have to be large; it has to answer the questions your staff hear on the phone every day.

What should a restaurant website include?

What is on the menu, and what does it cost? Are you open today, and until when? Where exactly are you, and where can I park? Can I book, and for how many? Is the entrance accessible for a wheelchair? A good site answers each of these before anyone has to call.

In practice that means a menu page in real text, opening hours written as text rather than set in an image, the address with a map and a link that opens directions, a phone number that dials when tapped, and a clear route to booking. Add photographs of the real room, dishes and view, a short paragraph about who cooks, and practical notes such as card payments, space for groups and whether dogs are welcome.

The details change by venue. A village taverna needs parking and directions from the main road. A beach bar needs its season dates, how to reach the beach and whether sunbeds can be reserved. A café needs morning hours and takeaway, and a hotel restaurant should say whether non-residents are welcome. Hotels themselves are covered in our guide to websites for hotels and holiday rentals.

The menu: readable on a phone, current, and not a PDF

The menu is the reason many people open a restaurant website, and it is often handled badly. The usual answer is a PDF of the printed menu: on a phone, that means a download, then pinching and scrolling across columns set for an A4 page. It usually exists in one language and is replaced only when someone remembers, so last season's prices stay online.

A menu in real text fits the screen, can be enlarged and can be read aloud by a screen reader. Search engines read it too, as do the AI assistants people now ask where to eat. Each dish should carry its price, a line of description and its allergens: under EU rules, allergen information is mandatory for food served in restaurants and cafés.

The website menu should also agree with the price list in the venue. The Ministry of Development's market rules for catering set out what that list shows: it is written in Greek, with other languages optional; prices include VAT, as must any price you communicate, on the website too; frozen, pre-cooked or pre-fried items are marked; and a notice in Greek and English says customers are not obliged to pay without a legal receipt. The list must be available to every guest before they order, restaurants must also post it at the entrance, and venues must make sure people with disabilities can get its information, which a menu in text helps with and a scanned page does not. One menu, published everywhere, keeps all of this in line, as described below.

Bookings that suit how you fill tables

There are three common routes: a phone number, a request form that staff confirm, and a booking system with live availability. A taverna that works mostly with walk-ins may need only a phone number that dials when tapped and a line saying when it is answered. A restaurant that sells out every Saturday needs live availability, so that guests stop calling to ask whether there is room.

If you already use a booking platform, link to it or embed it cleanly, and keep the phone number visible in case the widget fails to load. If you take requests by form, ask only for what holds a table: name, date, time, party size and a phone number. Say who sees those details and how soon you reply, and make sure someone checks the inbox during service. Groups, events and private dining deserve their own page and enquiry form.

Languages for the guests you actually get

In a tourist area many visitors look for places to eat before they travel, in their own language, and a site in one language loses them before they arrive. Greek and English are the minimum for a venue that serves visitors; beyond that, add the languages your bookings and reviews show your guests speak.

Each language should live at its own address, declared in the code, so that search engines can show a German speaker the German page. Visitors should be able to switch language by hand, and the site should not redirect them by location: a Greek living in Munich may well want Greek. Our technical SEO checklist for a new website includes the language annotations.

Translation is where many menus lose their character. Kleftiko means nothing to most visitors, and a literal translation of the word means even less. Keep the Greek name, add one plain line saying what the dish is, and have someone who speaks the language read the result.

Google, the website and the menu should say the same thing

Your Google Business Profile, your website, your Instagram and the menu on the table are four places a guest may check. When they disagree, guests notice. A profile that says open while the website says closed for the season, or a two-year-old menu photo with prices that no longer apply, costs trust and sometimes a table.

Keep the name, address, phone number and hours identical everywhere. Google Business Profile lets you set special hours for holidays and events without changing your regular hours. It also has a field for a menu link: point it to the same live menu your website uses. Google may still find menus from other sources and show menu photos uploaded by guests, so check the Menu tab: there you can choose your preferred menu source and flag outdated customer photos for removal.

On the website, structured data tells search engines in code what the page says in words: a restaurant, its cuisine, its hours, its menu and whether it takes bookings. Nobody can guarantee a position in results, but search engines no longer have to guess. It is part of our technical SEO setup.

Fast on a phone, with photos of the real place

People look up a restaurant on a phone, often in the street or on a hotel balcony, on mobile data. The page has to load quickly on a weak connection and keep the hours, the menu, the phone number and directions within a thumb's reach. Background videos, large sliders and Instagram feeds are the usual reasons it does not.

Photos sell a restaurant, so they should be good and they should be yours: the room, the terrace, the dishes as they reach the table. Stock images of food you do not serve do the opposite. Each image should be served at the size the screen needs, so a phone does not download a picture made for a large monitor.

An embedded map loads content from a third party and can set cookies. In Greece, cookies that are not technically necessary may only be set with the visitor's consent, so a common approach is a static map image or an address link that opens the phone's map app, with the interactive map loading only when the visitor asks for it, which also keeps the page fast. Our page on website design and development explains how we build and measure for speed.

How does a website work with a digital menu and ordering at the table?

A website and a digital menu do different jobs. The website works before the visit, when guests find, choose and book you; the digital menu works at the table, where they read, order, call the waiter and ask for the bill. They should share one thing: the menu itself.

The practical rule is one menu, kept in one place and linked from everywhere. The website describes your cuisine and signature dishes in words that rarely change, and its menu button opens the live menu; the same link goes on your Google Business Profile, your Instagram bio and the QR code on each table. Change a price once, and every guest sees the same figure.

That is the idea behind Kalimenu, the studio's own QR menu with ordering at the table, for restaurants, bars, cafés and hotels, and on its Greek site for tavernas and beach bars too. Each venue gets a public menu link for its Google Business Profile and Instagram (with structured data on the Greek site), and the same menu opens from the QR code on every table in the language of the guest's phone, with no app. Dishes and prices are changed in the admin area and appear at once, with no codes to reprint.

At the table guests order, call a waiter and ask for the bill, and at kalimenu.com the venue closes it on its own POS. On the Greek site, where the venue has connected its own Viva Wallet account, guests can also pay from the phone; the menu shows the tax and receipt notices required in Greece and works next to the till, which still issues the legal receipt. Our Kalimenu case study sets out how it works in each kind of venue. Kalimenu has its own sites, kalimenu.com in English and kalimenu.gr in Greek, and our other products are on the products page.

What are the common mistakes on restaurant websites?

The same problems turn up again and again: a PDF menu with last season's prices; winter hours still showing in July, or no word that the venue is closed until April; a site only in Greek in a village full of visitors, or a machine-translated English page nobody has read; a phone number set inside an image, which cannot be tapped.

Others take longer to notice. Booking requests land in an inbox nobody opens in August. The domain lapses over the winter, and the site is down just as guests start planning their summer.

Most of these are maintenance problems, easier to fix before the season than during it. A short check before opening, covering the menu, hours, bookings, languages and the Google profile, catches nearly all of them. Our Website Care plans cover hosting, backups, updates and domain monitoring, and the larger plans include hours for changes each month.

If you are planning a website for a restaurant, taverna, café or beach bar, or rebuilding one that no longer works, tell us about the venue: what you serve, who your guests are and how you take bookings. The scope and the quote are set in writing before work begins.

Questions

Frequently asked.

How much does a website for a restaurant cost?

It depends on the number of pages and languages, the booking route, whether text and photos are ready, and whether we also look after the site through the season. We quote every project in writing after a first conversation.

How long does it take, and when should we start before the season?

Most business websites go live four to eight weeks after the project starts, and content and approvals usually set the pace. A seasonal venue should start in winter, so that the site, translations and Google profile are ready before guests plan their trips.

Can we change the menu, prices and opening hours ourselves?

Yes. Each site we build includes a content management system your team can use without technical help. If the menu lives in Kalimenu, prices are changed once in its admin area and the change appears wherever the menu link is used.

Is a one-page website enough for a café or a small taverna?

Often, yes. One fast page with the menu or a link to it, the hours, a map, a phone number that dials when tapped and a few real photos answers most of what guests ask. It can grow later.

Can guests book a table through the website?

Yes: by a phone number that dials when tapped, a request form that staff confirm, or a booking system with live availability. Whichever you choose, keep the phone number visible.

Does a digital menu like Kalimenu replace the website?

No. The website helps guests find and choose you before they visit; the digital menu serves them at the table. They work well together when they share one live menu, linked from everywhere guests look.

Does a restaurant website have to be in Greek and English?

The Ministry of Development's market rules require the price list in the venue to be written in Greek, with other languages optional. For the website, choose by your guests: where visitors come, Greek and English are a sensible minimum, plus the languages your guests actually speak.

Start a project.

Contact the studio