Website builder

One restaurant website for
every menu, table and location.

Tell Netiva’s AI agent how your dining rooms run and it builds a site with dietary-tagged menus, dated specials, event pages and reservation requests, taking shape in a live preview.

Start building free More website ideas
Starter prompt

Build a website for an independent restaurant group with a flagship bistro and two smaller cafés. Each location gets a page with its address, phone, opening hours, holiday closures and parking notes. Keep one menu collection with brunch, dinner and bar sections; each dish has a price, dietary tags, the major allergens it contains and the locations that serve it, and diners can filter by tag. Specials and events have start and end dates and show only while they run. Add a reservation request form: parties larger than eight become a large-party inquiry, and hosts sign in to confirm, waitlist or decline each request.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this restaurant website is for

Before booking a table, diners want three answers: whether the kitchen can handle their dietary needs, whether there’s a table and whether the nearest location is open tonight. Too often the answers sit in a PDF from last season, a phone that rings mid-service and an hours box that missed the holiday closure. A restaurant website built with Netiva keeps dishes, specials, events and every location’s hours in collections your team edits. Guests send reservation requests your host confirms by email, and each location gets a page of its own.

Key features

What your restaurant website can do

  • Menus with dietary tags

    Every dish lives in one menu collection with its section, price, dietary tags and the major allergens it contains, so the brunch, dinner and bar menus all render from the same records instead of a PDF.

    • Tag filters for vegetarian, vegan and gluten-free dishes
    • A required allergen field, so no dish is published without one
    • Each dish linked to the locations that serve it
    • Market-price dishes shown without a number

  • Reservation requests

    Guests choose a location, date, time and party size, and the request lands on a host screen. The host confirms, waitlists or declines it, and the guest hears back by email either way.

    • Parties over a location’s limit sent to a large-party inquiry
    • Requests grouped by location and service for the host
    • Confirmation, waitlist and day-of reminder emails
    • Hosts and managers sign in with their own accounts

  • Specials and events on a schedule

    Happy hours, weekly specials, tasting dinners and holiday prix fixe menus carry dates, days and times, so the home page shows what’s on now and the events page lists what’s coming up.

    • Recurring specials such as Tuesday to Friday, 4 to 6 p.m.
    • Finished events drop off the events page by date
    • Ticketed dinners sold as seats through a hosted checkout
    • Specials tied to one location or shown at all of them

  • A page for each location

    Each location’s page is built from the locations collection: address, phone, regular and holiday hours, parking and access notes, and only the dishes and specials served there.

    • Holiday closures listed ahead of the date
    • Today’s hours for every location on the home page
    • A map from a maps provider’s API, with the key stored securely
    • A reserve button that preselects the location
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Locations

Each dining room you run, with the details guests check before they set out.

  • Name (required) Neighborhood or street name guests know it by Text
  • Address (required) Paragraph
  • Phone (required) Text
  • Opening hours (required) Per day, including split lunch and dinner service Paragraph
  • Holiday hours Dated closures and special hours Paragraph
  • Largest online party (required) Bigger groups are sent to a large-party inquiry Number
  • Parking and access Parking, transit and step-free entrance notes Paragraph
  • Photo Image

Menu items

Every dish and drink, with the dietary and allergen details diners filter by.

  • Name (required) Text
  • Section (required) Brunch, dinner, bar, kids or dessert Text
  • Description (required) Paragraph
  • Price Leave blank for market-price dishes Number
  • Dietary tags Vegetarian, vegan, gluten-free — only tags the kitchen can stand behind Text
  • Contains (required) Each major allergen in the dish, or none Text
  • Raw or undercooked (required) Yes or no; yes adds the consumer advisory asterisk Text
  • Served at (required) One or more locations Relation to Locations

Specials and events

Happy hours, weekly specials, holiday menus and events, each with the dates it runs.

  • Title (required) Text
  • Type (required) Special, happy hour, prix fixe, live music or tasting dinner Text
  • Location Leave blank to show it at every location Relation to Locations
  • Starts on (required) Date
  • Ends on Blank for ongoing specials Date
  • Days and times (required) e.g. Tue–Fri, 4–6 p.m. Text
  • Details (required) Paragraph
  • Seat product Store product SKU for ticketed dinners; blank for walk-in Text

Reservation requests

Every table request from the website, from a table for two to a private dinner for 30.

  • Guest name (required) Text
  • Email (required) Used for status updates and the reminder Text
  • Phone (required) Text
  • Location (required) Relation to Locations
  • Requested for (required) Date & time
  • Party size (required) Number
  • Notes Occasion, high chair or allergies to flag to the kitchen Paragraph
  • Status (required) Requested, confirmed, waitlisted, declined, canceled, seated or no-show Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Home

    What’s on today across your locations: current specials, the next few events, each location’s hours and a button to request a table.

    Public

  • Menu

    Brunch, dinner and bar sections for the location a diner picks, with dietary tag filters, allergens and consumer advisory footnotes.

    Public

  • Location

    One location’s address, phone, hours and holiday closures, parking and access notes, a map and the specials running there.

    Public

  • Event

    One event or holiday menu with its date, times and details, plus a buy-a-seat button or a link to request a table.

    Public

  • Request a table

    Location, date, time, party size and notes; parties over the location’s limit switch to a large-party inquiry.

    Public

  • Host desk

    Requests for each location and service in time order, with covers per half hour and buttons to confirm, waitlist or decline.

    Your team
How it works

From prompt to a live restaurant website

  1. Describe your dining rooms

    Tell Netiva how many locations you run, which services each one offers and how bookings work today. The agent drafts collections for locations, menu items, specials and events and reservation requests.

  2. Enter the menu with your chef

    Add dishes in the spreadsheet-like grid, or describe them to the collection assistant and review the rows it drafts. Then have the chef check every dietary tag and allergen field before anything goes public.

  3. Walk the site as a guest

    Invite your general manager and chef into the workspace to comment on the preview. Send a request for a party of ten, try the menu filters and annotate anything the agent should change.

  4. Go live ahead of the weekend

    Publish in one click, then point your own domain at the site from the Starter plan up. When the seasonal menu turns, each edit is checkpointed, so you can compare versions or roll one back.

Why Netiva

Netiva vs a traditional build

Building a restaurant website with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Table requests A request form for each location, a host desk to confirm or waitlist and status emails to the guest Voicemails and direct messages returned between lunch and dinner service
Hours at each location A page per location with its own regular hours, dated closures, dishes and specials One contact page with every address, updated by whoever remembers the holiday closure
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A neighborhood bistro with one dining room

    With 12 tables, Fridays fill early. Requests for more than six go to the owner as large-party inquiries, the chef keeps gluten-free tags current as the seasonal menu turns, and the Tuesday prix fixe appears only on Tuesdays.

  • A taqueria group with three locations

    Each location has its own page, hours and holiday closures. Most dishes are shared, but the downtown spot runs a late-night menu, so those items are linked to that location alone and never appear on the other two pages.

  • A counter-service café with a supper club

    By day there are no reservations, so the request form is switched off for the café. Twice a month it hosts a 20-seat supper club, sold as seats through checkout, and each dinner leaves the events page once its date passes.

Good to know

Before you build

  • Tags and allergens are your kitchen’s call

    The site shows what your team enters, so recheck dishes when a recipe, supplier or fryer changes. Sesame joined the major US allergens in 2023, and FDA says restaurants’ gluten-free claims should be consistent with its federal definition.

  • Menu notices your health code may require

    Where your state or local code follows the FDA Food Code, raw or undercooked animal foods need a disclosure and reminder, and the 2022 edition adds written allergen information for unpackaged dishes. Massachusetts also requires a fixed allergy notice on menus.

  • Calorie counts if the group grows

    Federal menu labeling covers chains with 20 or more locations that do business under the same name and sell substantially the same menu items. Most independent groups aren’t covered, but check the FDA requirements before you reach that size.

  • Requests, not live table management

    The form doesn’t hold tables on its own; your host confirms each request. Netiva doesn’t replace your POS, a table management system or delivery platforms. If your reservation provider offers an API, you can ask the agent to connect it.

Compliance note

Dietary tags and allergen details on your restaurant website are only as accurate as the menu collection behind them. Netiva displays what your team enters and doesn’t review recipes. Update dishes when ingredients, suppliers or prep change, note shared fryers and prep surfaces, and ask guests with food allergies to tell their server before they order.

FAQ

Questions about building a restaurant website

How do diners find vegan or gluten-free dishes on a restaurant website?

Each dish carries the dietary tags your chef sets, such as vegetarian, vegan or gluten-free, plus the major allergens it contains. The menu page has filter buttons for those tags, so a diner can narrow brunch or dinner to what they can eat at the location they picked. A tag appears only where you set it, so leave it off when cross-contact makes it unreliable.

Can guests book a table instantly, or only send a request?

The form sends a request, not an instant booking. Guests choose a location, date, time and party size, and a signed-in host confirms, waitlists or declines it from the host desk. The app emails the guest at each step and can send a reminder on the day. For live availability, connect your reservation provider’s API if it has one, or link to its booking page.

Can each location have its own menu and hours?

Yes. Locations are a collection with their own address, phone, opening hours and holiday closures, and each dish is linked to the locations that serve it. A location’s page shows only its dishes and specials, so a late-night menu or a patio-only special stays where it belongs. Prices are shared across locations unless you ask the agent for a price field per location.

How do I sell seats for a tasting dinner or holiday menu?

Ask the agent to add the dinner as a store product with stock equal to the seats you have. Guests pay through a hosted one-page checkout that takes cards and handles tax automatically, and the event page shows how many seats are left. After the date passes, the event drops off the events page, and the order pipeline keeps a record of refunds and customer notes.

Which Netiva plan does a restaurant website need?

You can build and preview the whole site on the free plan. Connecting your own domain starts on the Starter plan, which also adds basic SEO tools and analytics. Plans differ in how many store products you can list, which matters if you sell seats for dinners. Compare the current plans on Netiva’s pricing page, and remember the code is yours to export at any time.

Keep exploring
All ideas
Compare

How Netiva compares

All comparisons

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your restaurant website today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.

Start building free Browse more ideas