How much does a restaurant website cost?

What budget should you plan for your restaurant's website?

Budgets are given excluding VAT for the volumes and features listed. For a new build: scoping, site structure, UX/UI, CMS development, integration of the copy and visuals you provide, testing and handover. For a redesign, migration or upgrade: the work is done on an existing site. These services do not add up automatically. Copywriting, translations, new visuals, licences, subscriptions and third-party costs are specified in the quote.

What makes the price of a restaurant website vary?

To prepare private hire requests, the team does not need the same information as for confirming a table. Specify whether groups go through a form handled outside service hours and whether regular bookings stay in the booking software. This separation avoids building a single journey that is too long for diners and too thin for organising an event.

A menu that is easy to read and update

A menu shown as an image or a downloadable document does not require the same design as a menu structured within the site. In the second case, you need to plan categories, dishes, descriptions, prices and how they are updated.

The level of autonomy you expect also changes the scope. Should a manager be able to change a dish? Hide a menu that has ended? Schedule a holiday menu? Can the team handle these changes during service? These questions determine the editing fields and the training needed.

Start by listing the information guests look for on a restaurant website. A readable menu, reliable opening hours and clear access to booking should be in the quote before secondary visual effects.

Booking: link, widget or custom connection

Three solutions need to be distinguished. A link sends guests to the booking service. A widget displays the provider's booking journey within the site. A custom connection exchanges data with the software and may require extra development, testing and maintenance.

The choice depends on what the provider allows, the journey you want and the level of customisation. A standard integration can be enough for an independent restaurant. A group that wants to guide visitors between several venues may need more detailed scoping.

To make guests want to book a table, the menu, photos and booking terms must stay easy to see before choosing a time slot. On mobile, also test returning to the site after opening the widget: guests may still need to check the address or opening hours.

Ordering, payment and gift vouchers

Takeaway adds operational decisions: available products, options, pickup times, kitchen capacity, minimum order and cancellations. A button to an existing tool and a journey built into the site do not carry the same responsibilities.

The quote should also state who handles payments, confirmations and refunds. For gift vouchers, specify how they are sent and how the team checks they have been used. Features that look small in a mock-up can require several business rules.

Photos, copy and visual identity

The price of a website depends on the content already available. Do you have recent photos of the venue and the food? Is the menu ready? Are the positioning and copy defined? A photo shoot, a translation and creating a brand identity must be kept separate from building the site.

Web design work organises this content so the restaurant's atmosphere comes through and actions are easy to find. List the photos and copy available before the quote: you will know what still needs producing and who will do it.

Languages and locations

A menu in French and English must stay consistent when a dish, price or set menu changes. The quote should separate the initial translation, how fields are organised and who will make updates. A menu renewed every week does not need the same organisation as an offer that stays the same for several months.

For several locations, the site must keep menus, directions, opening hours and bookings separate. Above all, you need to know who updates each venue, what that person can change and how changes are checked. Reusing a template reduces design variations; it does not remove the work on data and journeys.

Which services make up the price of a restaurant website?

The price of the site covers a set of tasks to define. Designing the journey, producing the content and integrating booking can be handled by different providers. Compare their deliverables and responsibilities before comparing the final amount.

Structuring an editable menu, designing a private hire page and reusing photos of the venue are different pieces of work.

Who prepares the content and who can edit it?

A menu in a file, a set of selected photos and approved copy reduce the project's unknowns. If the agency has to run an interview, write, retouch or translate, the quote describes this work and the approvals. Developing a "dish of the day" field does not include writing its content every day.

Training should start from a task the team will actually do: change a price, hide a menu or announce a closure. Ask which fields are editable and what requires design work. A free-form section does not give the same autonomy as a template built for frequent changes.

A web agency specialising in restaurants must in particular plan separate journeys for booking a table, ordering takeaway and requesting private hire. These uses determine the pages to design and the tools to connect.

SEO support can target searches related to your cuisine, your neighbourhood or your group offers. To attract local customers, your opening hours, address, menu and booking links must also stay consistent between your site and your Google Business Profile. Ask which actions are planned each month and how the requests they generate are tracked.

How do you redesign a restaurant website without losing access to the menu and bookings?

A redesign starts with an inventory: useful pages, outdated menus, old URLs and content to keep. Decide what will be kept, rewritten or merged before going live. The quote should separate this migration from the design of new pages.

The SEO migration must preserve the paths guests rely on: the link from your Google listing, the QR code on a printed menu, old menu or event pages and access to booking, in every language concerned. Specify how old URLs are handled and the checks after the switch. Accounts must stay accessible to the people in charge of the site and related tools.

For tracking actions, distinguish a click on "Book" from the confirmation provided by the software. Tracking depends on what the provider makes available and the measurement rules you choose. A private hire request can be followed up by the team without funding the same set-up as a booking paid online.

How do you reduce the website budget without complicating bookings?

For an independent restaurant, it is better to first make the journeys that come before a visit reliable. An extra feature earns its budget when it meets a need the team will actually use.

Prioritise:

• Mobile browsing: menu, prices, opening hours and directions that are easy to read.
• Booking: a clear journey, tested all the way to confirmation.
• Reusable content: photos of the venue, dishes and practical information kept up to date.
• Administration: a named person to change the menu, closures and opening hours.
• Measuring actions: completed bookings, calls or private hire requests, depending on the tools available.

Postpone features with no owner or no clear use. An abandoned events section, a second language never updated or a form nobody follows up add work without delivering the expected service.

The best trade-off also depends on your model: a restaurant that mostly takes phone bookings can focus on that journey; a venue with prepaid menus needs to scope payment and its rules more carefully.

How do you check menus and languages before the site goes live?

For several restaurants, each change must apply to the right location: lunch prices, opening hours, holiday menu and booking link. Shared elements can be reused, while variations stay assigned to each venue. Acceptance testing must check a menu change and how it displays in each language, without assuming a translation updates itself.

How do you compare quotes to create your restaurant's website?

Ask for a verifiable scope

Send every provider the same information: the venue concerned, current tools, languages, available content and priority actions. Then ask each proposal to detail:

• The number of page templates and the content to integrate.
• Exactly how the menu and booking work.
• The copywriting, photos and translations included or to be supplied.
• Mobile testing, training and account access.
• Subscriptions, maintenance and upgrades billed separately.
• The approval stages and what must be supplied before launch.

This list makes price differences explainable. It also shows what is missing from a proposal before you compare its final amount. Attach your current menu with prices, set menus and the origin of meats. To create a website for a restaurant in France, these details are part of the scope: restaurant display rules also apply to the online menu, which must give the same information as the one on the table, dish by dish rather than in a simple PDF.

Which costs remain separate from the web service?

Hosting, the domain, the booking software and any payment fees follow their own contracts. Ask who subscribes to them, who receives the invoices and who steps in if something goes wrong. Technical maintenance does not automatically cover a new menu, a translation or a change to the journey.

Before asking for a custom connection, check the features of your booking software: embeddable widget, data access and support. The payment provider's fees are separate from the booking software's terms; no commission per cover does not necessarily mean no payment fees.

SEO can be a launch service or separate ongoing support: content about your cuisine and neighbourhood, consistent practical information and request tracking. Gemeos offers SEO/GEO support from €1,000 excl. VAT per month, with a scope defined for each venue.

To get a suitable budget, prepare your menu, current tools, booking needs and available content. You can then request a quote for your restaurant's website on a concrete scope.

FAQ on the cost of a restaurant website

What are the web priorities when opening a restaurant on a tight launch budget?

First publish the confirmed information: address, opening date once it is set, opening hours, a menu ready to publish and a way to book or get in touch. Photos must show the actual venue or clearly state what they are. A shop, a loyalty programme or elaborate features can be considered later. Scoping should specify what the team will be able to update before and after opening, so you don't pay for changes every time the menu changes.

How do you update the lunch menu without paying for an intervention every time?

The menu can be managed from an interface where your team changes dishes, prices and set menus without touching the layout. Ask for a demo with a real menu change: replace a dish, change its price and remove a set menu that has ended. The quote should include the necessary fields, training and any access limits. Also think about translated versions and the menu published on your other channels.

Can you keep Zenchef or your booking software when redesigning the site?

Yes, if your plan and the software's integration options allow it. The redesign can keep a link or re-embed its booking widget. Have the choice of service, number of guests, time slots and confirmation tested from a phone. The quote should separate this integration from a custom connection with the software. Also check that bookings stay attached to the right venue after launch.

How do you handle deposits and cancellation terms for large tables?

First define which bookings are concerned: groups above a certain number of guests, a tasting menu or a special evening, for example. The site must explain the terms before confirmation, then pass the guest to the right journey. The chosen software must be able to handle the expected deposit or card guarantee rules. Setting them up, transaction fees and confirmation tests must be priced separately from simply having a "Book" button.

Should a private hire request go through the same form as a table booking?

Private hire usually requires information that a regular booking does not collect: preferred date, number of people, meal format, space required and budget. A dedicated page can present capacities and services before the form. Plan who receives requests and how they are followed up. The cost then covers the page, the content, the form and any connection to your sales follow-up tool.

What do you need on the site to offer click and collect at lunchtime?

The journey must account for available dishes, options, pickup times and kitchen capacity during service. Specify how an order reaches the kitchen and whether it must be sent to the till. Redirecting to an existing tool is different work from an integrated ordering journey. Before pricing, also test out-of-stock items, late orders and the confirmations sent to customers.

Do you need a separate site for each restaurant when you have several locations?

A shared site can work if the venues share the same brand and each location has its own page, menu, opening hours and booking link. Guests must always know where they are booking. Very different concepts can justify separate sites. The quote should specify the shared elements, the content specific to each venue and the permissions of the teams who update them.

Which content should a restaurant in a tourist area translate?

Start with what helps people decide and get there: menu, prices, opening hours, directions, booking and terms that matter to groups. Check that the journey stays clear all the way to the booking software; translating only the home page leaves part of the work to the guest. The budget depends on the volume to translate and how changes are managed. A seasonal menu also needs a process to update each language at the right time.