A PDF is unreadable on a phone
The guest has to zoom, pan, zoom again. Someone hungry and in a hurry gives up after a few seconds and looks at the place next door instead.
Industry solution · Gastronomy
A restaurant website with a menu that actually makes people hungry
The menu is the most important page a restaurant has — and on most websites it is a PDF from last year. SaaleWeb builds it as its own maintainable page: dishes with photo, description, price and allergens, sorted into categories, readable on a phone in seconds and connected directly to the reservation path.
- Update the menu yourself — no agency appointment, no new PDF
- Dishes with photo, price, allergens and labels such as vegetarian
- Two real references from the region: Waldschlösschen and Neue Liebe
This is one dish entrysaaleweb.de
Seasonal
Tarte flambée with green asparagus
€16.90
Wild garlic cream, red onions, spring leek and grilled asparagus from a farm in the region.
VegetarianRecommendedAllergens: A, G, L
Example content. Dishes, prices, images and labelling later come from your own menu.
In brief
Who builds restaurant websites with a digital menu?
SaaleWeb is a digital studio based in Halle (Saale) building websites for restaurants, inns, cafés and event gastronomy. The focus is the menu as its own maintainable and indexable page — with dishes, images, prices, allergen labelling and categories — plus a short path to a table reservation. Two completed examples are publicly online: the Waldschlösschen restaurant in Nebra and Neue Liebe in Nebra (Unstrut).
- Provider
- SaaleWeb — digital studio and web agency based in Halle (Saale)
- Focus
- Digital menu · reservations · Local SEO · GEO/AIO
- Region
- Halle, Leipzig, Merseburg, Saalekreis, Saale-Unstrut
- References
- Waldschlösschen Nebra · Neue Liebe Nebra (Unstrut)
- Entry level
- Landing page from €990, multi-page restaurant website from €1,990 plus VAT
- Next step
- Free initial consultation or a review of your current website
The real problem
A menu as a PDF costs you guests — every evening
Almost every guest checks the menu before visiting. Usually on a phone, usually on the move, usually right before deciding. This is exactly where most restaurant websites fail — not because of the design, but because of a file format.
Google cannot see the dishes
Content inside a PDF is captured poorly and is almost impossible to structure. Searches for individual dishes, categories or a style of cooking find nothing.
AI systems have nothing to quote
When someone asks ChatGPT or Google for a nearby restaurant with vegetarian options, the answer needs readable, unambiguous data — not a document behind a download link.
Every change costs time
New price, seasonal menu, a dish sold out: if each change means re-typesetting and re-uploading a document, in the end nothing gets updated at all.
Outdated prices annoy guests
When the online menu says €14.50 and the plate costs €16.90, an avoidable conflict starts right at the table.
Instagram is not a menu
Many businesses maintain only the social channel. Guests find atmosphere there, but no complete menu, no opening hours and no reliable way to reserve.
A digital menu solves all of it at once: readable on mobile, usable for search engines and AI systems, editable by your own team in minutes and connected directly to reservations.
The centrepiece
The digital menu
This is how a menu works for guests, Google and AI systems at the same time: switchable categories, every dish with image, description, price and labelling. Try the categories below — the content is an example, the structure is real.
What this menu does technically
Its own URL instead of a download
The menu is a real page with its own address, title and description — linkable, shareable and indexable by Google.
Categories and filters
Starters, mains, desserts, drinks, seasonal menu: guests jump straight to what they want instead of scrolling twelve pages.
Image and video clip per dish
A good photo sells a dish better than any description. At Waldschlösschen a short clip sits behind many of the images.
Allergens and labelling
Allergen data plus vegetarian, vegan, lactose-free or gluten-free sit directly on the dish — not in a footnote on page four.
Prices changed in minutes
Price adjustment, new dish, change of season: you edit it yourself in the admin area and the page is immediately current.
Connected to reservations
From any point in the menu there is a visible path to a table request — exactly when the appetite is there.
Multilingual when needed
German and English as a base, Russian or further languages depending on your guests — dish names and descriptions included.
Structured data for menus
Menu, MenuSection and MenuItem as JSON-LD: that is what allows Google and AI systems to understand individual dishes, categories and prices in the first place.
Two menus we built, both publicly online
Both projects were built by SaaleWeb and are live. Look at the menus before you talk to us — that says more than any description.
Waldschlösschen Nebra
Hotel and restaurant in one presence. The menu is organised by category, every dish carries an image, description, price and allergen data, and many dishes additionally have a short video clip. The menu is maintained by the business itself and changes with the season.
- 12 categories from asparagus season to spirits
- More than 120 items with price and description
- Photo and short clip on many dishes
- Allergens and vegetarian labelling on the dish
Neue Liebe Nebra (Unstrut)
Restaurant with terrace, dance and events. The menu lives on its own URL, is bilingual, filterable by category and connected directly to reservations. On the menu page itself an FAQ answers typical guest questions.
- Its own /menu URL with its own metadata
- 8 category filters from starters to beer & drinks
- German and English
- FAQ directly on the menu page
The second step
From appetite to reservation — without a detour
The best menu achieves little if all that follows is a phone number in the footer. We build the reservation path to fit the business — not every restaurant needs a booking system.
Call with one tap
On a phone the number is a link. For many businesses the telephone remains the best channel — it just has to be instantly reachable.
A structured inquiry form
Date, time, number of guests, occasion, requests such as terrace or a high chair. The request arrives complete instead of being clarified over five callbacks.
Your existing reservation tool
If you already use one, we integrate it — as an embedded widget or as a link with pre-filled details. You keep your system.
WhatsApp and messengers
For many guests the fastest route. On request with a prepared message so the inquiry already carries the right details.
Groups and celebrations separated
A birthday party for 30 is not a table reservation. Larger occasions get their own form with menu preference and time frame.
Opening hours that are correct
Regular hours, last orders, closing days and public holidays — maintained identically on the website and in the Google Business Profile.
We do not sell reservation software and we will not sell you a system you do not need. For many restaurants in the region a clean form plus a phone number is entirely sufficient — and carries no monthly fee.
Guest journey
How a guest actually finds you
Between the first impulse and a reserved table there are rarely more than ten minutes — and almost always a phone. Each phase makes a different demand on your website.
- 01
Impulse
The guest
Is hungry, has an occasion or visitors — and searches for a restaurant in Halle, Merseburg or along the Saale-Unstrut.
Your website must
appear at all: a maintained Google Business Profile, current photos, a named style of cooking and a clear location.
- 02
Check the menu
The guest
Opens the menu — by far the most common reason anyone visits a restaurant website.
Your website must
show the menu immediately and readably on mobile: categories, dishes, prices, allergens. No download, no zooming.
- 03
Does it fit?
The guest
Checks opening hours, terrace, parking, whether children are welcome and whether there is something vegetarian.
Your website must
answer those questions before they are asked — on the page, not on the phone.
- 04
Reserve
The guest
Wants a table now — usually in the evening, often for today or tomorrow, almost always from a phone.
Your website must
offer a visible, short path: call with one tap, a form, or your reservation tool.
- 05
Afterwards
The guest
Has been there, recommends the place, writes a review or comes back for the next occasion.
Your website must
make reviews visible, offer events and celebrations and prepare the next occasion.
Scope
What we actually build for restaurants
Not every business needs everything. Scope is defined in the first consultation based on style of cooking, size, event business and how much you want to maintain yourself.
Digital menu
Its own page with categories, dishes, images, prices, allergens and labelling — maintained by your own team.
Seasonal and rotating menus
Asparagus, game, a Christmas menu or a lunch offer as separate sections that can be switched on and off again.
Reservation path
Phone with one tap, a structured form, integration of your tool or messenger — whatever fits your operation.
Atmosphere and rooms
Dining room, terrace, beer garden, fireplace room or private room with their own images and descriptions instead of one shared gallery.
Events and celebrations
Weddings, corporate parties, birthdays and Christmas events as separate pages with capacities, format and an inquiry form.
Opening hours and closing days
Regular hours, last orders, holidays and annual closures — maintained cleanly and aligned with the Google profile.
Real reviews
Guest voices from Google, Tripadvisor or other sources with a recognisable origin. No invented quotes.
Local SEO and Google profile
Consistent contact data, the menu link in the profile, attributes such as terrace or accessibility, photos and questions & answers.
Structured data
Restaurant, Menu, MenuSection, MenuItem, opening hours and FAQ as JSON-LD — the foundation for Google and AI answers.
Speed on a phone
Images are compressed properly and delivered in modern formats. A menu with 120 dishes may still load fast.
Multilingual content
German and English as a base, Russian or further languages depending on your guests — dishes included.
Vouchers and offers
Gift vouchers, lunch deals or seasonal campaigns as maintainable sections that match the occasion.
SEO · GEO · AIO
Found on Google — and quotable for AI answers
Guests stopped typing keywords a while ago; they ask questions — in Google, in Maps and increasingly in ChatGPT, Gemini, Claude or Perplexity. Those systems can only recommend a restaurant when kitchen, menu, location and opening hours are unambiguous and machine-readable on a page they can reach.
Typical questions your website should answer
- Restaurant in Halle (Saale) with a terrace and regional cooking
- Where can you eat well in Nebra or along the Unstrut?
- Restaurant with vegetarian options in Merseburg
- Inn for a company party for 40 people in the Saalekreis
- Which restaurant in Halle is open on Sundays?
- Restaurant with Saale-Unstrut wines and a beer garden
None of these needs a separate doorway page. Each needs a clear answer in the right place: on the menu page, in the opening hours, on the events page or in the FAQ.
Dishes as data, not as an image
When dishes, categories and prices exist as text and structured data, a system can read them. A photographed menu card is invisible to search and AI.
An unambiguous entity
Name, address, phone number and opening hours are identical on the website, the Google profile and the portals. Contradictions are the most common cause of hesitant answers.
Name your style of cooking
Regional, German, seasonal, vegetarian, game, tarte flambée: what you do not write down, nobody can associate with you.
Local grounding
Directions, parking, proximity to Arche Nebra, the wine route, the station or the city centre — information guests look for that anchors you regionally.
Being current
Changed opening hours, annual closures, the seasonal menu. Outdated details damage AI answers more than they damage classic search results.
Honest expectations
Whether a specific system names your restaurant is decided by that system, not by an agency. We do not sell guarantees; we build the foundations that improve the odds.
Often underestimated
Celebrations and events are the second revenue channel
A wedding, a company Christmas party or a birthday with 40 guests is worth more to many businesses than an average evening. Yet most websites give it a single sentence.
A page per occasion
Wedding, corporate party, birthday, funeral reception, Christmas party: separate pages with their own search terms instead of one line in a paragraph.
Capacities and rooms
How many people fit in the hall, the private room, on the terrace? That number is often the first question — and rarely answered.
Menu suggestions and format
Sample menus, packages and a rough schedule give confidence before anyone picks up the phone.
An inquiry form with the right fields
Date, number of guests, occasion, budget range, catering, technical needs. A complete inquiry saves both sides several calls.
Photos of real events
A festively set hall convinces more than any text — provided the images come from your own house.
Seasonal visibility
Christmas parties are searched for in September, weddings a year ahead. These pages have to be online and findable early.
Reliability
What should be correct on a restaurant website
Allergen labelling
For food sold loose, the 14 allergens subject to labelling must be accessible to guests. The website can carry that information clearly; factual accuracy stays with the kitchen.
Additives
Declarations such as colourant, preservative or flavour enhancer belong visibly with the dish. We build the fields, you maintain the content.
Price display
Guests see final prices including VAT. The menu should show the same state online and in the house — otherwise the conflict happens at the table.
Opening hours and closing days
Wrong hours are the most common cause of disappointed guests and poor reviews. Website and Google profile are therefore maintained together.
Images and rights
Your own photos are legally safe and simply work better. For images of guests or events we make sure consent is properly handled.
Imprint, privacy, reviews
Complete provider identification, documented forms and recipients, and real reviews with a recognisable source. Invented testimonials are legally risky.
We implement carefully on the technical and editorial side and flag open questions. That does not replace legal or food-law advice — the final review of labelling, price presentation and your privacy policy stays with you and your advisors.
Orientation
Entry levels for restaurant projects
The figures below are for orientation. The fixed price follows the free initial consultation and depends on menu size, languages, event business and available imagery.
Compact presence
from €600
Café or small business with a manageable menu
- One-pager on a WordPress basis
- Menu as a readable page instead of a PDF
- Opening hours, directions, phone with one tap
- Google Business Profile aligned
Restaurant with a digital menu
from €990
Restaurants where the menu is the most important page
- Individual build with Next.js
- Digital menu with categories, images and allergens
- Dishes and prices maintained by your team
- Reservation path and structured data for Google and AI search
Full gastronomy website
from €1,990
Businesses with events, rooms, seasonal menus or an attached hotel
- Food menu, seasonal menus and drinks list maintained separately
- Dedicated pages for celebrations, rooms and occasions
- German, English and Russian
- Local SEO, GEO/AIO structure and measurability
- Maintainable content plus optional ongoing support
All figures exclude 19% German VAT. Additional scope such as food photography, video clips per dish, copywriting in several languages or special integrations is calculated separately.
FAQ
Questions from the restaurant trade
What does a restaurant website cost at SaaleWeb?
For orientation: a compact WordPress one-pager starts at €600, a restaurant website with a digital menu at €990, and a full gastronomy website with events and rooms at €1,990 — each plus 19% VAT. Food photography, video clips per dish and further languages add scope. We name the exact fixed price after the free initial consultation.
Can we really maintain the menu ourselves?
Yes, and that is the whole point. Dishes, descriptions, prices, categories, images and labelling are edited in the admin area and the page is immediately current. That is exactly how the Waldschlösschen menu works, changing with every season.
Why is a PDF menu a problem?
A PDF is hard to read on a phone, almost impossible to structure and is evaluated far less well by search engines and AI systems. Then there is the practical point: if every price change means re-typesetting a document, in the end nothing gets updated.
Do we need a photo of every dish?
Not necessarily, but images work hard. A good photo sells a dish better than three lines of description. A sensible start is the 10 to 15 most important dishes; the rest of the menu can stay text-based and be extended later. Food photography is not part of the base scope and is calculated separately.
Can short videos of dishes be embedded?
Yes. At Waldschlösschen many dishes have a short clip behind the image that plays on tap. Technically that is no problem as long as the clips are short and properly compressed so the menu stays fast.
How are allergens displayed?
As a field directly on the dish, using the letter code common in Germany, complemented by labels such as vegetarian, vegan, lactose-free or gluten-free. For food sold loose, the allergens subject to labelling must be accessible to guests. We build the structure; the kitchen is responsible for factual accuracy.
Can we keep using our existing reservation tool?
Yes. We integrate an existing tool as an embedded widget or as a link with pre-filled details. If you do not use one yet, we often recommend a structured form plus telephone — enough for many businesses in the region and with no monthly cost.
How long does a restaurant website project take?
A compact build is often finished in two to four weeks, a full gastronomy website usually in four to eight weeks. In our experience the biggest time factor is not the technology but capturing the menu, imagery and approvals from the business.
Will our restaurant then also be named in ChatGPT or Google AI Overview?
The chance rises considerably when style of cooking, dishes, prices, opening hours, location and answers to typical guest questions are unambiguous and machine-readable on your website — with structured data for the restaurant and its menu plus FAQ sections. Whether a specific system names your business is decided by that system; no one can seriously guarantee it.
Is a website worth it when we already have Instagram and Google?
Both channels are valuable, but neither replaces a website. Nobody reliably finds a complete menu on Instagram, the Google profile carries no event description, and neither platform belongs to you. The website is where menu, opening hours, celebrations and reservations come together completely and permanently.
How do you handle reviews?
We embed real reviews with a recognisable source, for example from the Google Business Profile or Tripadvisor. We do not implement invented quotes or polished averages — they are legally risky and destroy exactly the trust they are meant to build.
What happens after launch?
After going live we check loading times, mobile use, forms, indexing and the reservation paths. Menu, seasonal offers, event pages and FAQ can then be extended step by step. Ongoing support is available but never a condition — the website belongs to you.
Read on
Pages that fit your project
Show us your menu — we will show you how it works online.
In the free initial consultation we look at your menu, your current website, your reservation path and your Google profile. Afterwards you know which step is worth taking — even if the answer turns out to be no new project.
No obligation, no contract commitment and an honest assessment, including when it argues against a project.