Numuno Digital /
Restaurant websites: menu, bookings and contact without confusion
A restaurant website should quickly answer three questions: what can I eat, when are you open and how do I ask for a table? When a menu is an unreadable image, hours omit holidays, or a form looks like it confirms a booking when it only sends a request, customers do not know what to expect. Design the journey by separating these states.
By Numuno Digital, an independent web design and marketing studio in Marbella.
Make the menu readable on a phone
Publish dishes in HTML with clear sections, names, short descriptions and current prices. A photo or PDF can supplement the menu, but should not be the only way to read it: on a small screen, visitors have to zoom, scroll and guess. Check contrast, text size and clipped content.
Assign someone to review the menu and set a date for the next check. When a recipe or price changes, update the website and any channels you manage, including the Business Profile where relevant. If you offer a lunch or seasonal menu, state the days or dates so it does not appear permanent.
Prepare content your team can maintain
Give your website designer a menu reviewed by the restaurant, authorised photographs and allergen information your team has validated. Decide who approves those details and how a recipe change is communicated. The website developer should not infer ingredients or allergens from a photograph or the name of a dish.
Place the validated information beside the menu in a readable format and provide a way to ask your team questions. Also prepare short descriptions of the cuisine, access and available services. A change list with a responsible team member makes updates easier without redesigning the page each time.
Say whether a request or table is confirmed
A booking form may send a request without access to live availability. If so, label the button “Request a table” and explain on the confirmation screen when the restaurant will reply and that the table is not yet confirmed. Confirmation follows through the channel the business uses.
If you connect a tool with live availability and automatic confirmation, check what it synchronises: sittings, party size, closures, cancellations and messages. Integration, limits and costs depend on the provider and agreed scope; do not assume it is included or always free. For a simple request, ask for date, time, party size and contact details, and say what happens if the sitting is full.
Keep opening hours and access consistent
Show days and service periods clearly, including whether kitchen and dining-room hours differ. Mark exceptional closures and how last-minute changes will be shared. Review these details after seasonal changes and before holidays; outdated hours can ruin a visit even when the rest of the website works well.
Include the address, phone number, useful directions and direct links to the right action. If you offer delivery or collection, state whether orders go through your website or an external provider. Do not mix table bookings with takeaway orders.
Keep business details and channel reporting clear
Use a consistent business name, address, phone number and hours on the website and Business Profile. Google recommends accurate information and lets restaurants manage menus and links; available features depend on the account and market. Structured data can help Google interpret local business information, but it does not guarantee an enhanced result or bookings from Search.
Measure menu views, phone taps, submitted requests and confirmed bookings separately. If your integration allows it, compare received requests with bookings actually accepted. This helps show whether people cannot find the menu, abandon the form or wait too long for a reply.
If your Estepona restaurant serves customers in Spanish and English, our Estepona website and marketing guide expands on consistency between the ad, menu and customer response. It covers manual bookings or integrations and who updates hours and conditions.
Your checklist before starting.
- HTML menu and prices checked by a named owner
- Clear route for allergen questions
- Booking request and confirmation explained separately
- Current hours, closures, address and phone number
- Integration scope, responsibilities and possible costs agreed
- Separate click, received request and confirmed booking metrics