Business guides

What should a restaurant website have?

Guests open a restaurant website with a few practical questions: what you serve, when you are open, where you are and how to book. This checklist covers what a restaurant or café website should answer first, in Thai and English, and what to agree before anything is built.

O2 Design Studio

A menu guests can read on a phone

Put the menu on the page as text rather than only as photographs of a printed menu. Guests can read it on a small screen and zoom in, and search engines can read the words. Show what each set or course includes. Suan Zen Omakase used to send guests photos of its paper menu over LINE, so guests could not see what each course included before they reserved; the restaurant now sends its menu site, where every course has its own page.

  • Dishes and courses as text, with photographs where they help guests choose.
  • A note on what changes with the season or the day.
  • One person who updates the menu when it changes.

Hours, location and how to get there

Say when you are open, including the days you close, and where you are in a form a taxi driver or a map app can use. A map button and a LINE button save guests a message. Keep these facts the same everywhere they appear: on your website, your map listing and your social pages. A guest who finds two different closing times may not come at all.

Reservations: a request or a confirmed booking?

Decide how a reservation is confirmed before choosing the tool. A Reserve button can open your LINE with the guest's choice already in the message, as on Suan Zen's site; your team then confirms the table in the chat. Or a booking system lets guests choose a date and time and see a confirmation. The first suits a small team that confirms by hand; the second suits a venue that wants guests to book without waiting for a reply.

Thai and English, each written for its readers

Give each language its own pages rather than putting both side by side. Write the Thai for Thai guests and the English for visitors, keeping the facts identical: dishes, hours and conditions. Agree which dish names stay in their original language. Google recommends a separate address for each language version and works out a page's language from its visible text, so a page should use one language throughout.

Before you ask for a quote

Gather what a studio needs to scope the site: your current menu, photographs you have the right to use, your hours, your LINE Official Account and map listing if you have them, and who will update the menu. Decide whether guests should also order from the table: a QR menu that guests only read and QR ordering that sends orders to staff are different builds. The first conversation with O2 is free, online or in person.

Explore the relevant services

Restaurant and café websites

QR ordering for restaurants and cafés

QR menu or QR ordering: which do you need?

Sources and further reading

Google Search Central: managing multilingual sites

Bring us the part you want to improve.

Tell us how the work runs today. We can discuss a useful first step and what should stay with your existing tools.