Restaurant website development in Europe in 2026: cost, timeline, and essential features
The 2026 guide to building a restaurant website that fills the dining room. Real prices by country, Zenchef and TheFork integration, local SEO, click and collect without commission.
By Mohamed SahbiA restaurant website in Europe costs between 1,200 and 6,500 EUR in 2026 for an independent establishment. Standard timeline: 2 to 5 weeks. But price is not the real question. The real question is how much your site earns you. A site that loads in 5 seconds on mobile and lacks direct booking costs you between 8 and 35% of your monthly revenue in commissions, no-shows, and lost customers.
Meanwhile, the restaurant next door captures "Italian restaurant [your city]" searches on Google, gets cited in AI Overviews when a tourist asks ChatGPT "where to dine in [your city]", and receives bookings without paying 2.50 EUR commission per cover to TheFork. 77% of customers check a restaurant's website before booking. 52% of bookings happen outside opening hours. If your site is not doing its job, those customers go to your competitors.
I am Mohamed. I have delivered 18 restaurant websites across Europe in 2025 and 2026, most of them visible as live demos on webcraftdev.com subdomains. This article is what I tell restaurant operators who reach out to me each week saying "my site looks bad and brings me zero customers." The method is not complicated, but it requires understanding where the money goes.
TL;DR: the key takeaways
Restaurant website price 2026: 1,200 to 4,500 EUR for an independent restaurant in France, Belgium, and Luxembourg, 2,500 to 7,500 CHF in Switzerland, 1,500 to 5,500 EUR in Germany and Austria.
Standard timeline: 2 to 5 weeks.
Mandatory features: mobile-readable online menu, direct booking, optional click and collect, local SEO with optimized Google Business Profile, Schema.org Restaurant.
The commission trap: TheFork charges 2 to 5 EUR per cover. On 600 monthly bookings, that is 1,200 to 3,000 EUR evaporated. A site with direct Zenchef booking at 69 EUR/month saves thousands per year.
The delivery trap: Uber Eats and Deliveroo charge 25 to 35% commission. An integrated click and collect costs zero commission.
AI visibility in 2026: without Schema.org Restaurant and Server-Side Rendering, you do not appear in ChatGPT or Google AI Overviews when someone searches for a restaurant in your city.
The hidden cost of a bad restaurant website
This section comes before pricing. Because an 800 EUR Wix site can cost you 30,000 EUR in lost revenue per year.
Take a 50-cover restaurant in Brussels, average ticket 35 EUR. Here is what happens with a template-based site.
TheFork bookings at 2.50 EUR/cover on 60% of flow (450 covers/month × 2.50 EUR × 12) : 13,500 EUR/year.
Uber Eats click and collect at 30% commission on 8,000 EUR/month delivery revenue : 28,800 EUR/year.
Mobile visitors lost to 5-second load time (53% mobile abandonment beyond 3s per Google 2025) : 15 to 25% of mobile traffic.
No-shows without automatic confirmation (8 to 15% of bookings without SMS reminder) : 4,800 to 8,400 EUR/year.
Google and AI invisibility on "restaurant [city]": traffic reduced 60 to 80% versus optimized.
Total annual hidden cost: between 47,000 and 65,000 EUR. The site that fixes this costs 3,500 EUR once plus 69 EUR/month for Zenchef. ROI in less than 30 days.
Yet most restaurants still think a website is a cost. It is the opposite. A bad site is the cost. A good site is what makes you money.
Real price ranges by country in 2026
Here are the figures I see across the European market. All prices exclude VAT.
France, Belgium, Luxembourg
Simple showcase site (3 to 5 pages): 1,200 to 2,500 EUR, 2 to 3 weeks.
Site with direct booking and dynamic menu: 2,500 to 4,500 EUR, 3 to 4 weeks.
Site with integrated click and collect: 4,000 to 6,500 EUR, 4 to 5 weeks.
Multi-establishment (chain, group): 6,500 to 15,000 EUR, 6 to 10 weeks.
Brussels and Paris carry a 10 to 15% premium over regional averages. Luxembourg sits between Belgian and Swiss pricing, with the SME Package Digital from Luxinnovation financing up to 5,000 EUR of the project for eligible restaurants.
Switzerland
Simple showcase site: 2,500 to 4,500 CHF.
Site with booking: 4,500 to 7,500 CHF.
Site with click and collect: 6,500 to 12,000 CHF.
Geneva and Zurich charge +30% over Valais or Ticino. nDSG compliance (Swiss Federal Data Protection Act, in force since September 1st, 2023) adds 300 to 800 CHF.
Germany and Austria
Simple showcase site: 1,500 to 3,000 EUR.
Site with booking: 3,000 to 5,500 EUR.
Site with click and collect: 4,500 to 7,500 EUR.
Berlin, Munich, Frankfurt, and Hamburg charge 15 to 25% above the federal average. Austria's KMU.DIGITAL program finances up to 80% of consulting and implementation for eligible restaurant SMBs.
For comparison with a generic multi-sector creation, see my complete guide to custom website development for European SMBs in 2026.
Essential features of a 2026 restaurant website
Here is what I include in every restaurant site I deliver. This is the baseline standard, not a wishlist.
Mobile-readable online menu
Not a downloadable PDF. An HTML menu with clickable categories, high-quality photos, allergen indicators, current prices. Restaurant operator updates in 2 minutes via a simple admin interface. 80% of restaurants in Europe still serve their menu as a PDF and automatically lose mobile visitors who do not want to zoom to read.
For a fine dining restaurant, plan a separate tasting menu version and seasonal menu.
Direct booking (without intermediary)
This is the number one feature in terms of return on investment. Three options depending on volume:
Option 1: Zenchef integration (recommended for most independent restaurants). 69 to 249 EUR/month subscription depending on features, no commission per cover. Widget integrated into the site, customer books without leaving your page. 25,000+ restaurants use Zenchef across 20+ countries.
Option 2: TheFork Manager. Freemium model then 2 to 5 EUR commission per cover depending on visibility tier. Advantage: massive traffic via the TheFork marketplace (55,000+ restaurants in Europe, Tripadvisor partnership since 2014). Disadvantage: commission climbs fast. On high volume, a fixed Zenchef subscription becomes more profitable.
Option 3: OpenTable (international restaurants, English-speaking expats). Premium positioning with strong international visibility. Common in Brussels EU restaurants, Geneva international, Luxembourg expat-serving practices. Commission model close to TheFork.
Option 4: Custom booking form + email confirmation. For a small restaurant with fewer than 80 monthly bookings, a simple personalized form with automatic email is enough. Cost: 0 EUR/month. Disadvantage: no real-time availability management, double-booking risk if you do not update quickly.
My advice: Zenchef for 95% of independent restaurants. The math is simple. On 600 monthly covers booked online, TheFork at 2.50 EUR/cover costs 1,500 EUR. Zenchef at 99 EUR/month = 1,401 EUR saved per month.
Integrated click and collect
If you do delivery or takeaway, integrate ordering directly on your site. Uber Eats and Deliveroo charge 25 to 35% commission per order, which on already tight restaurant margins turns you into a marketing service for these platforms.
Solutions to integrate on the site, without commission: Zelty, Innovorder, Sunday, Deliverect (multi-channel for international operators). Monthly cost: 30 to 150 EUR depending on solution. Customer orders and pays online, you prepare, they collect or you deliver.
Concrete calculation: on 8,000 EUR/month delivery revenue, Uber Eats at 30% = 2,400 EUR commission. A custom solution at 79 EUR/month saves 2,321 EUR per month, or 27,852 EUR per year.
Local SEO optimized for "restaurant [city]"
Your customers always type the same structure: "Italian restaurant Geneva", "brasserie Brussels center", "fine dining Luxembourg". For multilingual cities (Brussels, Luxembourg, Geneva), expect dual-language searches: "restaurant English speaking Brussels", "Italienisches Restaurant Frankfurt".
To appear on these queries:
Schema.org Restaurant complete: cuisine type, price range, photo, menu, hours, options (terrace, accessibility, parking, takeaway, delivery).
Google Business Profile optimized with professional photos of the dining room and dishes, precise hours, attributes (wine list, family-friendly atmosphere, etc.).
Local pages if you have multiple establishments or cover multiple zones.
Backlinks from TripAdvisor, TheFork, OpenTable, Tagesspiegel restaurant guides (DE), Le Soir Brussels guides, local press.
For Schema.org setup, see my practical guide to Schema Markup for SEO.
Professional photo gallery
The most profitable investment for a restaurant site. Photos of the dining room, signature dishes, the chef, the exterior. Responsive format (photos adapt to mobile without cropping the essential). If your budget allows, a professional photographer costs 400 to 800 EUR per session, and the photos serve 5 years.
Avoid stock photos. Users and Google immediately detect generic spaghetti or stock salad photos. This kills trust.
Story and team
Short section (2 to 3 paragraphs) on the restaurant concept, the chef, local producers, your values. Customers like to know who is behind the stove. This authenticity creates an emotional connection that tips the booking decision.
Practical info
Address with interactive map (embedded Google Maps), always up-to-date opening hours, click-to-call phone number on mobile, parking and transit access, group and private events policy, special options (birthdays, corporate events, full venue rental).
GDPR + nDSG compliance
CNIL/EU cookie banner with refusal as easy as acceptance, booking form with explicit consent, clear privacy policy, legal notices per applicable law.
For Switzerland: add nDSG privacy declaration (article 19, in force since September 1st, 2023). For Germany: complete Impressum per § 5 TMG, TTDSG-compliant cookie consent (stricter than GDPR baseline), Datenschutzerklärung. For Austria: § 24 ECG and § 25 MedienG mandatory mentions.
Local SEO for restaurants: capturing "restaurant [city]" on page one
This is what separates a profitable site from a decorative one.
Priority queries to target
"restaurant [city]": very high volume, very high competition. Strategy: Schema.org + GBP + local backlinks.
"Italian restaurant [city]": high volume, high competition. Strategy: cuisine-specific page.
"restaurant terrace [city]": high volume, medium competition. Strategy: mention terrace in H1 and Schema.org.
"best restaurant [neighborhood]": medium volume. Strategy: Google reviews, regional press.
"where to eat [event, e.g. Sunday brunch] [city]": medium volume, low competition. Strategy: targeted blog article.
"restaurant open [holiday] [city]": high volume in season, low competition. Strategy: real-time GBP updates.
"English speaking restaurant [city]": medium volume in expat zones, low competition. Strategy: bilingual content + Schema.org alternateName.
Google Business Profile: your number one weapon
70% of new restaurant customers come from Google Maps. The profile must be:
100% filled (primary category + secondary, attributes, services).
High-quality photos of the room, dishes, exterior (at least 20 photos).
Precise hours with holiday updates.
Menu linked to the profile (Google can display your menu directly in results).
Direct booking enabled via Reserve with Google (integrated with Zenchef, TheFork, OpenTable).
Weekly posts (daily special, event, news).
Reply to all reviews, positive and negative, within 48 hours.
The paid directory trap
Avoid paid "Top restaurants [city]" directories that charge 50 to 200 EUR/month to "list" you. Zero SEO impact, zero qualified traffic. Focus your effort on natural free directories: TripAdvisor, TheFork, OpenTable, Le Fooding, Gault et Millau, local guides.
GEO in 2026: getting cited by ChatGPT when someone asks "where to dine in [city]"
This is the new wave. 31.3% of the population uses generative AI search in 2026 according to EMARKETER. Tourists in particular use ChatGPT and Perplexity massively to plan dining outings, and English-language searches show the highest AI Overview density at 32%.
GEO foundations for a restaurant:
robots.txt allowing GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended.
Server-Side Rendering mandatory (Next.js does this natively) so AI bots see your content.
Bing Webmaster Tools activated: ChatGPT Search uses the Bing index, so Bing visibility equals ChatGPT citations.
IndexNow for real-time submission of new content.
Q&A structured content: FAQs are disproportionately cited by AI.
Schema.org Restaurant complete with cuisine type, options, price range, accessibility.
Multilingual content (EN + local language) for international zones: a Brussels restaurant with EN+FR+NL content has 3x the AI citation rate of a single-language site.
For the complete methodology, see my guide to getting your site indexed by ChatGPT and my article on appearing in Perplexity and Claude through GEO.
Why Next.js over WordPress or Wix for a restaurant
This part is technical but critical. The stack choice determines 80% of the final quality.
Mobile performance
62% of restaurant searches happen on mobile. A Wix site loads in 5 to 7 seconds on average. A WordPress with 12 plugins loads in 4 to 6 seconds. A well-built Next.js site loads in under 1.5 seconds.
Concretely: out of 1,000 mobile visitors, a 5-second-load site loses 530 (Google PageSpeed Insights 2025 data). A 1.5-second-load site loses 80. The difference: 450 visitors recovered per month, of which roughly 15 to 30 additional bookings depending on your conversion rate.
Guaranteed AI visibility
AI bots only read server-rendered HTML. A Wix site or a WordPress with a JavaScript theme (Elementor, Divi) loads content after the first render. AI bots see an empty page and move on. A Next.js site with Server-Side Rendering delivers complete HTML on the first request.
Total 5-year cost
Wix Premium: 2,200 to 2,800 EUR over 5 years (creation 0 to 1,000 EUR + subscription 1,200 to 1,800 EUR).
WordPress: 6,600 to 9,700 EUR over 5 years (creation 1,500 to 4,000 EUR + maintenance + premium plugins + mid-cycle redesign).
Next.js on Vercel: 2,740 to 5,240 EUR over 5 years (creation 2,500 to 5,000 EUR + 240 EUR Vercel Pro, no plugins, no redesign).
The math often surprises. A Wix site costs less than Next.js over 5 years, but it also costs you 30 to 80% less Google and AI visibility. On 30 additional monthly bookings thanks to better SEO, the Next.js premium pays back in under 60 days.
For more on this comparison, see my article on website redesign in 2026.
My method for delivering a restaurant site in 2 to 4 weeks
This is the process I apply with my restaurant clients. No step is skipped.
Week 1: scoping and strategy
30-minute call to understand your concept, customer base, goals (bookings, click and collect, private events).
Audit of your current online presence (existing site, GBP, TripAdvisor, TheFork, OpenTable).
Identification of 5 to 10 target keywords ("Italian restaurant Brussels", "Sunday brunch Frankfurt", etc.).
Architecture validation (typically: Home, Menu, Booking, Our story, Contact, Click and collect if applicable).
Week 2: design and content
High-fidelity mockups (Figma) desktop and mobile.
Brand guidelines adapted to your establishment (fine dining = elegant, brasserie = warm, fast-casual = modern).
Co-writing of texts (you validate, I optimize for SEO).
Photo preparation (your professional photos or stock backup if you do not have them yet).
Weeks 3 and 4: development and launch
Next.js project setup on Vercel.
Mockup integration into React components.
Complete Schema.org Restaurant implementation.
Zenchef, TheFork, or OpenTable integration per your choice.
Click and collect Zelty/Innovorder/Sunday if applicable.
GBP, GSC, Bing Webmaster Tools, IndexNow configuration.
Performance tests (target Lighthouse mobile 95+).
Launch, 1-hour training, 30 days of included support.
Concrete cases: 18 restaurant demos delivered in 2025-2026
To make this concrete, here are some of the restaurant sites I built and that are visible as live demos on webcraftdev.com subdomains.
Fine dining: maison-laurent.webcraftdev.com, maison-doree.webcraftdev.com, la-belle-epoque.webcraftdev.com, le-jardin-secret.webcraftdev.com. Elegant style, full-screen culinary photography, tasting menu, Zenchef booking.
Traditional brasserie: savora.webcraftdev.com, maison-blanc.webcraftdev.com, letoile.webcraftdev.com, le-petit-clos.webcraftdev.com. Warm style, daily blackboard, chef's special, family atmosphere.
Modern / creative cuisine: maison-lumiere.webcraftdev.com, lart-de-la-cuisine.webcraftdev.com, lart-de-la-gastronomie.webcraftdev.com, la-belle-cuisine.webcraftdev.com. Contemporary design, hero video, private events.
Neighborhood restaurants: la-maison.webcraftdev.com, la-maison-rouge.webcraftdev.com, belle-epoque.webcraftdev.com, la-belle-etoile.webcraftdev.com. Simple format, focus on daily specials, integrated click and collect.
All these demos achieve a Lighthouse mobile score between 92 and 99. All load in under 1.5 seconds on mobile. All have a complete Schema.org Restaurant and a robots.txt that allows AI bots. You can test any of them on PageSpeed Insights to verify performance yourself.
Pitfalls to avoid when choosing your provider
The provider who only offers a PDF menu
If you are offered to "scan your paper menu and put it as a PDF on the site", refuse. A PDF is not properly indexable by Google, unreadable on mobile without zoom, and invisible to AI Overviews. The menu must be in structured HTML.
The "all-inclusive" quote without booking detail
If direct booking is not explicitly listed in the quote with the mention "Zenchef integration" or "TheFork Manager integration" or "OpenTable integration" or "custom booking system", it is not included. You will pay extra development after the fact.
The provider who wants to sell you Wix or Squarespace
For a restaurant taking digital seriously, Wix and Squarespace are a false economy. Limited performance, restricted SEO, impossible GEO (AI bots cannot read JavaScript-loaded content). Over 5 years, you lose more in missed bookings than you save on creation.
The provider who mentions neither Schema.org nor AI Overviews
It is 2026, not 2020. A restaurant site that does not appear in Google AI Overviews is invisible for 30% of restaurant searches. The provider must be able to explain how they will make you visible in ChatGPT, Perplexity, and Google AI.
The "all-inclusive" package under 1,000 EUR
Very likely a template-based site sold in batches of 50, no customization, no real SEO optimization. The provider profitable at 800 EUR cannot afford to spend 20 hours optimizing your Schema.org and your GBP.
The number one strategic mistake: under-investing in bookings
I close on this point because it justifies every euro invested.
The calculation most restaurant operators make: "A 1,200 EUR site is enough, I do not need more."
The real calculation: this 1,200 EUR site without direct booking pushes 60% of your flow to TheFork at 2.50 EUR/cover. On 600 monthly covers, that is 1,500 EUR monthly commission. Over a year, 18,000 EUR evaporated.
Versus a 4,000 EUR site with integrated Zenchef: 99 EUR/month Zenchef subscription, so 1,188 EUR/year. The site pays back in less than 3 months on commission savings alone.
The real cost is not the price of the site. It is the price of everything you leave to platforms because your site is not up to par.
Next steps: how to launch your restaurant website project
If you got this far, you probably have a creation or rebuild project. Here is what I propose.
Free 48-hour audit: send me the URL of your current site (if any) and the link to your Google Business Profile. In 48 hours, I send back an honest audit: technical performance, Google visibility, AI Overview presence, SEO opportunities, and a price range for the project. No sales pitch, no commitment. Request a free audit.
Additional documentation:
Custom website development for European SMBs in 2026: the complete guide
Website redesign in 2026: when, why, and what it really costs
The real cost of a website in 2026
How to appear in ChatGPT and Perplexity
Schema Markup 2026: practical guide
My services dedicated to restaurants: