AI website builder for restaurants and cafés

Almost every visitor to a restaurant website is standing somewhere with their phone out, deciding where to eat in the next two hours. They are not browsing. They want the menu, they want to know if you are open, and they want to know how to get a table.

Siteglade builds that site from a description. You type what the restaurant is, the agent writes the project, and a live preview updates as it works. You can then click into the preview and change text, images and spacing directly, which matters when the only person available to update the site is whoever is not on shift.

Below: the sections a restaurant site needs, why menus are the part that decays fastest, how to handle reservations honestly, and a prompt you can adapt in a couple of minutes.

The three things every guest came to your site for

Menu, hours, and how to book or find you. That is the entire brief. Everything else on a restaurant site is supporting material, and any design decision that pushes those three below the fold is costing you covers.

The most common failure is a full-screen video hero with the restaurant name and nothing else, forcing a hungry person on a phone to scroll blind. A hero is fine. A hero that does not also carry todays hours, a phone number and a menu link is not.

Put the practical block near the top: address as text, not only on a map embed, opening hours by day, a tappable phone number, and one obvious button to the menu. Then let the atmosphere photography do its work underneath.

• Address written as selectable text, so it can be copied into a maps app.
• A phone number that is a real tel link, tappable on a phone.
• Opening hours by day, including the day you are closed.
• One primary button: menu, or reserve, depending on what you want more of.

Menus that stay current without a redesign

A menu as a PDF is the classic mistake. It is unreadable on a phone, it is invisible to search engines, and it forces a pinch-and-zoom experience on exactly the device most people are using. Put the menu on the page as real text.

The maintenance question is what actually decides your menu format. If prices move twice a year, plain text in the project is fine, and you change it by asking the agent or by editing the file directly in the built-in code editor. If you run a menu that changes weekly, you want the menu in one file that is easy to find and edit, not scattered through the markup, and it is worth saying that in the prompt.

For a genuinely dynamic menu that a non-technical team member updates without touching code, Siteglade Cloud can provision a database and authentication for the project on the Pro and Max plans, behind a consent step you approve explicitly. That is more setup than most restaurants need, so start with text and only move if the editing burden proves it.

• Real text, not a PDF or a photographed chalkboard.
• Group by course, with prices aligned and allergen notes where you are required to give them.
• Keep the menu content in one obvious file so updates are a two-minute job.
• If you run a daily special, give it a defined slot rather than editing the layout each time.

Being found by someone standing two streets away

Restaurant discovery is local, and the words people search with are ordinary: the cuisine, the neighbourhood, and something about the occasion. Your page should contain those words naturally, in sentences a human would write.

Write your location into the copy rather than leaving it to a map widget. Name the neighbourhood, the nearest landmark and the parking situation, because those are the things people actually search and ask about. If you take walk-ins, say so, because that is a distinct search intent.

In Site settings you control the site title, description, favicon and social share image. For a restaurant, the share image is doing a lot of work: your link gets pasted into group chats where people decide together, and a link with no appetising preview loses that vote.

A general point rather than a statistic: your site is one of several places holding your hours, alongside map listings and social profiles. Whenever you change them, change them everywhere, because a guest who arrives at a closed door does not check which source was wrong.

Reservations: choose the booking path before you build

Decide this before you generate, because it changes the whole layout. There are three honest options and you should pick one as primary.

Phone only works for small rooms and older audiences, and it is the lowest-friction thing to build: a tappable number, prominent, with the hours you actually answer it. A booking platform you already pay for is the most common answer, in which case the site links to it and your job is to make that link impossible to miss. A form that emails you is the fallback, and it is worth being clear that a form is a request, not a confirmed table, so guests are not left waiting.

What Siteglade does not do is process reservations for you. There is no built-in booking engine, and pretending otherwise would leave you with a site that quietly loses tables. Build the path to whatever system you already run, and make it one tap from every page.

• Pick one primary action and make every other option secondary.
• If you use a booking platform, put its link in the header, not only in the footer.
• If you use a form, state your response time so guests know what to expect.
• Large-party and private-hire enquiries usually deserve their own short page.

Writing the prompt for a restaurant site

Be concrete about cuisine, room, neighbourhood and tone. The difference between a generic restaurant template and something that feels like your place is entirely in the detail you give.

A workable prompt: 'Build a one-page site with anchor navigation for a 34-seat Neapolitan pizzeria in the Ostkreuz neighbourhood of Berlin. Warm, low-light, unfussy. Dark background, cream text, one bold condensed display face. Sections in this order: a hero with the name, one line of description, todays hours and two buttons for menu and reserve; a practical block with address as text, a tappable phone number and opening hours by day; the full menu as real text grouped into antipasti, pizza, dolci and drinks with prices right-aligned; a short story section about the oven and the dough; a gallery of six photographs of the room and the food; a footer with address, hours, phone and social links. Reservations go to an external booking link that I will paste in. Must be fast and legible on a phone in a dark room.'

Once it exists, refine in small pieces. Ask for the hours block to appear in the header too. Ask for the menu section headings to be sticky while scrolling. Small, specific instructions land much more reliably than a rewrite request, and the preview shows you each change as it happens.

Food photography, and what you must not generate

Media Studio can generate images on every plan, including Free, and video on Pro and Max. For a restaurant, there is a hard line: do not generate pictures of food you serve. A guest who orders based on an image that does not match what arrives at the table is a guest you have lost, and depending on where you trade, advertising rules may treat it as a misleading representation.

Use real photography of your real dishes and your real room. If you have none, one evening with a phone, good window light and a tripod beats anything generated, because the point of the image is proof.

Where generation genuinely helps is everything that is not a menu item: abstract background textures, a pattern for section dividers, an illustrated map motif, a placeholder while you wait for the real shoot. Anything Siteglade generates carries machine-readable AI provenance markup in the published page, so generated media is labelled rather than passed off.

Last updated: 2026-08-16