How to Make a Restaurant Website With AI (Menu + Orders)

To make a restaurant website with AI, gather your menu, opening hours, address and a few real photos, then describe the site in one message. The builder creates the pages, a menu you can edit from an admin area and optional reservations or pickup orders, all live on a link you can move to your own domain.

• Diners come for five things: the menu with prices, today's hours, the address, a phone number and a way to book or order. Put them on the first screen of a phone.
• Store the menu as editable text, not a PDF or photo, so price changes go live within about a minute without a rebuild.
• Use your own dish photos. WisyLink doesn't generate photos, and stock images of food you don't serve set the wrong expectation.
• Print QR codes only when the site is on its final domain: free links expire, and moving to a domain retires the old address.
• Reservations use the same no-double-booking guard as any booking site; pickup orders can take payment through your own Stripe account.
• Restaurant structured data, a sitemap and the links in your Google Business Profile do most of the local SEO work.

What diners look for on a restaurant website

Most visits to a restaurant website are short and practical. Someone is choosing where to eat tonight, standing outside the door, or checking whether you're open on a holiday. Design for that visitor first:

Notice what's missing: autoplay video, a splash page and a PDF menu. A PDF is hard to read on a phone, can't be filtered by diet and is one more file to replace every time a price changes.

Gather your content: menu, photos, hours, address

An hour of gathering saves several rounds of corrections. Collect:

• Your current menu as a PDF, Word file, spreadsheet or clear photo of the printed menu. You attach it to the chat as a reference file, up to 25 MB each, and the builder works from it.
• Real photos. Six good ones beat thirty average ones: a few signature dishes, the dining room and the front door so people recognize it. Use JPEG, PNG or WebP, which every browser shows; if your phone saves photos as HEIC, export them as JPEG first.
• Hours, including the kitchen's last orders if they differ, and your next holiday closures.
• Address, phone and email, written exactly as on your Google Business Profile.
• Reservation rules: the largest party you take online, time slots, tables per slot, how long you hold a table.
• Pickup rules: preparation time, pickup windows, and whether guests pay online or at the counter.
• Allergen information as your local food rules require. You're responsible for it, so write it yourself.
• A short story: who cooks, since when, what you're known for. Three sentences are plenty.

One firm rule on images: WisyLink doesn't generate photographs. It uses your photos, stock photos and hand-drawn vector illustrations. For anything on the menu, use your own pictures; a stock plate of pasta that doesn't look like yours sets an expectation your kitchen then has to miss.

Build it: steps and a prompt template

1. Create a free Community account (no card) and open a new chat on the web or in the WisyLink app on your phone.
2. Attach your menu file and photos, and paste the prompt below with your details.
3. Answer Wisy if it asks a question; otherwise the build starts and reports its progress in the chat.
4. Read the final note. It tells you how to sign in to the admin area and which integrations still need your details.
5. Check every dish, price and allergen against your real menu. The builder works from your file, but a wrong price is still your problem.
6. Ask for changes in the same chat. Each change is a new build, and a failed build never replaces the live version.

Build a website for [restaurant name], a [cuisine] restaurant in [neighborhood, city]. Time zone: [Europe/Madrid]. Language: [English], plus a [Spanish] version with its own URLs.

Home: our name and one line about us, today's opening hours with an "open now" status calculated in the visitor's browser, our address with a maps link, a tap-to-call button for [phone] and a [Book a table] button. Use only the attached photos, no stock photos of food.

Menu: use the attached menu. Store every dish as editable data with name, description, price, category, dietary labels ([vegetarian], [vegan], [gluten-free]) and allergens, plus a sold-out switch. Show it as text grouped by category, with filters for the dietary labels.

Admin: a private admin area where I edit dishes and prices, upload dish photos, change opening hours, add holiday closures and show a short notice banner.

Reservations: parties of [1–8], start times every [30] minutes from [18:00] to [21:30], at most [6] tables per time. Never accept more bookings than tables, even if people book at the same moment. Larger groups see our phone number.

Also: Restaurant structured data with our address, phone, hours, cuisine and menu URL, and a printable table card page with a QR code that opens the menu.

On the free plan, Wisy keeps each build to a working first version, so it may build the menu, hours and admin first and add reservations in a follow-up build. That's a sensible order anyway. Our prompt templates have more patterns, including how to word follow-up changes.

A menu you can edit from an admin area

Can you update the menu and prices yourself? Yes, and where the menu lives decides whether the site stays right. When dishes are stored as data, you change a price in the admin area, save, and the public menu shows it within about a minute: no rebuild, nothing to upload. Editing in the admin doesn't use your AI usage allowance either. Asking Wisy to change prices in the chat does, because that's a new build.

Worth asking for in the admin:

• a sold-out switch per dish, for the night the fish runs out;
• categories you can reorder, and a daily specials section you clear and refill;
• lunch and dinner menus shown by time of day;
• a photo upload per dish;
• holiday closures and a notice banner ("Closed Friday for a private event");
• a field per language for each dish, so translations stay attached to the dish.

The admin area is a web page with its own login, so it works on the phone in your apron pocket. Give staff their own logins if they will update specials.

One detail changes how you prompt. Pages are cached and refreshed whenever your data changes, so a price edit shows up quickly. The clock doesn't trigger a refresh, which is why "open now" should be calculated in the visitor's browser, as the prompt above asks.

A QR code menu for your tables

A QR code menu is a printed code that opens your menu page. The code holds a web address and nothing else, so it never needs reprinting while that address keeps working. The common mistake is printing the wrong address:

• Don't print a free link. Community links are deleted after 30 days plus a week.
• Don't print the default address if you plan to add a domain. When a link moves to your own domain, its previous address stops serving it.
• Point to a page, not a file. yourrestaurant.com/menu stays current as you edit; a PDF has to be replaced.

So connect your domain first (any plan works), then print. Ask for "a printable table card page with a QR code that opens /menu, with our name and the short address underneath". The printed address helps guests who would rather type than scan.

Before you laminate fifty cards, test one at a table: scan it with a few different phones, in evening light, from a seated distance. Print it large enough and leave a white margin around the code, because scanners need that quiet space.

Table reservations and pickup orders

Table reservations

Reservations work like any booking system with capacity: each time has a number of tables, and a booking is accepted only if one is still free at that instant. WisyLink's data layer does the check and the booking as one step, so two guests can't both take the last table at 20:00. Our guide to building a booking website with no double-booking explains the mechanism and how to test it with two phones.

Keep the form short: party size, date, time, name, phone, email and a note for allergies or a high chair. Send large groups to the phone. Confirmations go through your own SMTP account, added under Integrations; until then nothing is sent, but every reservation is saved and listed in your admin for the night.

Pickup orders

Can customers order and pay online? Yes, for pickup:

1. The guest builds an order from the live menu, where sold-out dishes can't be added, and picks a pickup time.
2. The site saves the order and sends the guest to a Stripe checkout page, on your own Stripe account.
3. Stripe confirms the payment with a signed webhook, and only then does the order count as paid.
4. The order appears on an orders screen in your admin that updates live, and the guest gets an email confirmation once SMTP is set.

Two settings protect the kitchen: a cap on orders per pickup window, and a "pause online orders" switch for a packed Friday. If you'd rather not take cards yet, ask for pay at pickup and add Stripe later; check that Stripe supports your country first. Delivery through third-party platforms isn't something to expect out of the box: a platform with a public API can be connected with your own keys, but treat that as its own project.

Local SEO: structured data, sitemap and Google Business Profile

Will your restaurant website show up on Google? It has the foundations: every WisyLink site serves complete HTML that search engines can read, with titles, descriptions, social share tags, a sitemap and robots.txt. Three additions do most of the local work:

1. Restaurant structured data. Google's local business structured data guide requires your name and address and recommends cuisine, menu URL, opening hours, phone, price range and map coordinates. Ask for it and keep the hours in the admin, so the data follows your edits. Don't mark up star ratings for your own restaurant; Google's guide reserves review markup for sites that collect reviews of other businesses.
2. Google Business Profile links. Your profile is what people see on Maps. You can add links for your menu, reservations and orders there; point each one at the matching page on your site.
3. The same details everywhere. Name, address and phone written identically on your site, your profile and any directory listing.

In tourist areas, add a second language. WisyLink builds multi-language sites with the language in the URL (/en/, /es/) and the tags search engines use to show the right version. Pages stay in the language you built them in unless you explicitly ask for a translation, so name the languages you want and have a native speaker check the menu.

Then verify the site in Google Search Console and submit the sitemap. None of this guarantees a ranking; it makes sure search engines know what you are and where you are.

Launch checklist for restaurants

• Every dish, price and allergen matches your real menu.
• Opening hours, last orders and the next holiday closure are right, and "open now" is correct in your time zone.
• The call button dials, and the map link opens at your door, not the street behind.
• Two phones booking the last table at the same moment: exactly one succeeds.
• A pickup order paid with Stripe's test keys appears in the admin; then the keys are switched to live.
• Your SMTP account is set under Integrations and confirmations arrive outside the spam folder.
• The site is on a paid plan, so it stays live, and on your own domain; our guide to connecting a custom domain walks through it.
• QR table cards are printed from the final address and tested at a table.
• Your Google Business Profile links point to the menu, reservation and order pages.
• Staff know how to mark a dish sold out and pause orders.
• Any legal pages your country requires, such as a privacy notice, are in place.

WisyLink's terms make reviewing and testing what the AI builds your job; this list is that job for a restaurant. Budgeting the paid plan and domain? Our breakdown of what it costs to build and run a web app lists every line, payment fees included.

Put your restaurant online today

Describe it in one message and get a live link: start free on Community, no card needed. Attach your menu and photos, paste the prompt above and check the result on your phone the same day.

When it's ready for guests, compare plans to keep it live on your own domain, and browse the use cases for what else you can add.