Create a restaurant website with AI

A restaurant website is not there to “be online.”
It has one job: help someone decide to come (or order) in under a minute.

On a phone, in the street, between two messages: “What’s the vibe? The prices? Open tonight? How do I book?”

What your guests actually look for

Before design, answer these on the home page:

1. What: cuisine, atmosphere, price level
2. Where: address + easy access
3. When: today’s hours (and closed days)
4. How: book, order, call
5. Why you: one clear promise (not “quality food”)

If those five points are fuzzy, the prettiest site in the world will not convert.

The v1 that works (without a factory)

For most restaurants, an excellent v1 includes:

• Home with a real photo and an identity line
• Menu (or PDF + highlights) readable on mobile
• Hours kept up to date
• Address + Maps link
• Reservation (OpenTable / TheFork / phone / simple form)
• Contact (tappable phone, Instagram)

Not required on day one: full online shop, loyalty program, food blog, 12 languages.

Frame: What is an MVP?.

What matters in the restaurant niche

Photos

People eat with their eyes.
Prefer 5 real photos (dishes, room, team) over 20 generic images.
Bad photo = “not sure.” No photo = “I skip.”

Menu

• Visible prices (or a clear range)
• Allergens / options if that is your reality
• Easy updates (you will change the menu)

Mobile first

Most people look for a restaurant on a phone.
Big buttons: Call, Directions, Book.

Local trust

• Google reviews (link or widget, your choice)
• Press mentions / “since 20xx” if true
• Room photos (people want to know where they are going)

Local SEO (without jargon)

On Google, you win with:

• the restaurant name + city / neighborhood in titles and copy
• a careful Google Business Profile (as important as the site)
• consistent info everywhere (address, phone, hours)

The site complements the profile. It does not replace it.

Reservations: pick one simple path

Three honest options:

Avoid three buttons leading to three different systems. One main path.

Index10 path

1. Describe: cuisine type, neighborhood, tone (bistro, fine dining, street food…).
2. Ask for a mobile-first home with clear CTAs.
3. Add menu + practical info.
4. Publish a *.index10.app link to test with the team (security scan on publish).
5. Connect a real domain later (Pro plan) when you are happy.

General guide: How to build a website or app with AI.
How to phrase it: What is a prompt?.

Starter prompt (example)

Create the website for a [type] restaurant in [city/neighborhood].
Home: photo, identity line, buttons Book / See menu / Call.
Pages: Menu, Hours & access, Contact.
Style [warm / modern / minimal], very readable on phone.
No online shop for now.

If you want more later…

• Space for events / private hire
• Separate wine list
• Ordering (that is real software + payments)

Client accounts / orders = Index10 Cloud and much more complexity. Do not do it “because you can.”

Common mistakes

• Menu PDF unreadable on mobile
• Wrong hours (worse than no hours)
• Stock photos that do not look like your room
• Heavy music / animations that slow the page
• Forgetting the phone button

In short

A good restaurant site answers fast and makes people want to come.
On Index10: clear identity, practical info, menu, one booking path, mobile first, then iteration.

The useful question: in 30 seconds on a phone, would a stranger know if they want to come tonight?