Creating a Restaurant Website Diners Actually Book From

To create a restaurant website, start with what a diner wants in the first ten seconds: the menu as readable text, the opening hours and a way to book a table. Build those three first. Then add allergen information, your events and private dining, and the story of the place. Everything else is a bonus.

• AI Web Maker built the fictional Olive Table sample, 6 pages, in 54 seconds, from a short description of the business. See the sample page
• The sample lists 3 bookable services, each with its length; a visitor picks one, a day and a time, and the owner accepts or moves the request. See the sample page
• Almost all food businesses (97%) report providing allergen information to consumers, and 94% provide it in writing. Food Standards Agency research
• Google uses the mobile version of a site's content for indexing and ranking. Google Search Central

What must a restaurant website do for diners?

It must help a diner decide, book and arrive. Everything on the site should serve one of those three jobs, and anything that does not can wait.

Think about the person holding a phone outside a cinema, deciding where to eat. They want to know what you serve, whether it suits them, whether there is a table and where you are. If your homepage makes them hunt for any of that, they will go to the next restaurant on the map. They will not write to you to ask. They will simply leave, and you will never know they came.

Diners come with different jobs. One wants to read the menu before choosing. One wants a table for six on Saturday. One is planning a birthday for twenty and needs to know if you can host it. One has an allergy and needs to know if it is safe to come at all. A good restaurant website gives each of these people a short path to the answer.

This is why a restaurant website is not a brochure. A brochure says what you are proud of. A restaurant website answers questions fast and then lets the food speak. The Olive Table, our fictional sample restaurant, opens with its H1 "Green, bright and made for sharing" and then moves straight into plates, dates and a booking link. You can see this on the Olive Table homepage.

Write down the three questions your own diners ask most. For most restaurants they are "What is on the menu?", "Can I get a table?" and "Where and when are you open?" Keep those three answers within one tap of every page. The rest of this guide follows the order you would build in.

Which pages does a restaurant website need?

Six pages cover most restaurants: home, menu, book a table, events, your story and contact. Add more only when you have something real to put on them.

Here is how the Olive Table sample is laid out. It has 6 pages, and each one has a clear job.

Page	What it must do	Where to see it on the sample
Home	Show the food, the hours and a booking button	Home
Menu	List dishes, descriptions and prices as text	Menu
Book a table	Let a diner choose a day, a time and a party size	Book a table
Events	Explain private dining, group menus and set menus	Events
Our Story	Say who you are and how the food is made	Our Story
Contact	Give the address, the phone and an enquiry form	Contact

You may be tempted to add a blog, a gallery page, a gift card page and a careers page on day one. Resist that. A restaurant with six honest pages beats one with fifteen thin ones. A diner who finds a "coming soon" page loses a little trust in everything else. Each empty page also gives you one more thing to keep up to date.

The sample also has a page that browses bookings by category. That is a feature of the booking system rather than a page you write, and you can see it at Browse by Category. Treat it as a convenience for diners who want to compare options.

Keep the navigation short. Five or six links in the menu bar is enough. Put "Book a table" in the same place on every page, so a diner who is ready never has to look for it. A visitor who has to search for the button may decide not to bother.

What should each page of a restaurant website say?

Each page should answer its own question in plain words, with the practical details first and the personality second. Be specific and avoid filler.

Home. Lead with one strong line and one good photo of food, not of the building. Then show what you are serving, a button to book, your hours and your address. The Olive Table home page has sections called "Plates worth sharing", "What we are serving", "A table for your celebration", "Before you arrive", "Visit The Olive Table" and "Questions, answered". That order moves a visitor from appetite to action. Copy the idea, not the words, and use your own dishes and your own details.

Menu. Write every dish as text a visitor can read, search and copy. Give the name, a short honest description and the price. Group dishes the way a diner reads them: starters, mains, desserts and drinks, as on the sample menu. Mention the main ingredients, because that is what people scan for. Update it when the dishes change, and say if a section changes with the season.

Our Story. Tell the truth about how the place began, what you care about in the kitchen, who works there and what the room feels like. The sample's story page uses just those four ideas, and then ends with an invitation to come and sit. Skip the grand claims. Diners trust a short, specific story more than a long, polished one. A single true detail, such as why you chose the neighbourhood, does more than a paragraph of adjectives.

Events. Say which occasions you host, how many guests fit, what group and set menus exist and how to enquire. Add a form that asks for the date, the number of guests and the kind of event. The sample's events page is built in just this order, from the occasions you can host to a form titled "Tell us about your event".

Contact. Give the full address, the phone number, the opening hours and a short form. Keep the name, address and phone number the same as everywhere else you appear online, which matters for local search later. If parking or public transport is awkward, say how guests usually arrive.

Write in short sentences, and use the words your guests use. If regulars call a dish "the lamb," do not rename it on the site. Read every page aloud before you publish it. If a sentence sounds odd when you say it, rewrite it until it sounds like something you would tell a guest at the door.

How should the menu appear on a restaurant website?

Put the menu on the page as real text, not only as a PDF or a photo. Text loads fast, reads well on a phone and can be found by search.

A PDF menu is the most common mistake on restaurant websites. On a phone it forces a download, a pinch and a zoom. Screen readers may struggle with it, and the words inside it are harder for search engines to read. A photo of a menu is worse, because the text is not text at all. The diner sees a blurry image and gives up.

Build the menu page as headings and lists. A clear structure is enough: a heading for each course, then each dish with its name, description and price. If you want a printable version, offer a PDF as an extra link, never as the only way in. That way the page works for the person on a phone and for the person who wants to print it for a table of eight.

Think about how a diner scans. They look for a category, then a dish, then a price, then a note about ingredients. Put the price in the same place on every line. Mark vegetarian and vegan dishes clearly. If a dish is a sharing plate, say so, as the Olive Table does with its theme of plates made for sharing. A diner who knows a dish is meant to be shared will order differently and spend more time deciding with friends.

Keep the menu honest. If a dish is not available, take it off. If prices change, change them the same day. A menu that does not match the restaurant is worse than no menu, because the diner finds out at the table. That moment costs you more than the sale. It costs you the next visit.

Finally, link from the menu to the booking page. Someone who has just decided on the lamb is at the best moment to book, so put a button at the foot of the page. The sample does this with a closing section called "Ready to taste the menu?" Place yours in the same spot and word it in your own voice.

How do table bookings and enquiries work?

A diner picks a service, a day and a time, adds their party size and sends a request. You then accept it or suggest a new time.

In AI Web Maker, the Booking Manager lists each bookable service with its length. A visitor picks one, chooses a day and a time and sends a request, and the owner accepts or moves it. The Olive Table sample lists 3 bookable services, and you can try the flow on its booking page. Try it as a diner would, from a phone, before you set up your own.

For a restaurant, think of the bookable services as the kinds of table you offer. That might be a standard dinner table, a longer tasting experience and a group table. Give each one a sensible length, so your calendar reflects how long a table is actually taken. Be honest about it, because a table you promise for one hour and need for two causes problems at the door. Your own experience of a busy Saturday is the best guide to the right length.

Party size matters more in a restaurant than in almost any other trade. Say plainly what the largest online booking is, and tell larger groups to use the events enquiry form instead. Say how far ahead you take bookings and what happens if a diner needs to cancel or change their plans. A short note beside the form saves you phone calls and spares the diner an awkward surprise.

Not every request is a booking. Some people want to ask about a birthday, a menu for a group or a private room. Give them a separate enquiry form on the events page and the contact page, with fields for the date, the number of guests and what they have in mind. Reply quickly. A restaurant that answers an event enquiry within a day wins work over one that answers in a week. Large events are often the most valuable bookings you take, so treat the form with the same care as the front door.

Finally, make the confirmation clear. Tell the diner what happens next: when you will reply, how you will contact them and who to call if it is urgent. A request that disappears into silence feels like a rejection, even when it is not.

How do allergens and reviews build trust?

Be open about allergens, and keep your reviews real. Both are matters of trust, and both are covered by rules that differ from place to place.

Start with allergens. The UK Food Standards Agency publishes allergen guidance for food businesses, covering how to provide allergen information and best practice for handling allergens. Its guidance applies to England, Northern Ireland and Wales. If you run a restaurant in another country, check your own food regulator, because the rules are not the same everywhere. The FSA also explains the rules on food labelling, including that labels must be accurate and not misleading.

The FSA's research gives a useful lesson for your website. It found that while most businesses report providing allergen information, consumers do not always recall receiving it, particularly when it is not clearly signposted or proactively offered. It also found that consumers generally feel more confident in written allergen information than in information given verbally by staff. Read the full research findings to see the detail.

For your site, this means two things. First, say clearly where diners can find allergen information, and invite them to ask staff when they book. Second, never promise more than your kitchen can deliver. A good statement on the menu page says what information you hold and that guests with allergies should tell the team when booking and again at the table. Written information is trusted more, so put the main points in writing and use staff conversation to confirm them. Our companion guide on allergen information for restaurant websites goes deeper.

Now reviews. The US Federal Trade Commission announced a final rule on 14 August 2024, in force from 21 October 2024, that bans fake or misleading consumer reviews and testimonials. You can read the FTC announcement. Since April 2025, UK law bans posting or commissioning fake reviews, and the CMA can fine a company up to 10% of its global turnover, as the UK government announcement explains.

The practical lesson is simple. Show only reviews from real guests who really ate with you, and never write your own. The people, reviews, prices and contact details in the Olive Table sample are invented, because it is a demonstration. Your site must use real ones. Rules vary by place, and this is general information rather than legal advice, so check with your own regulator or trade association.

How does a restaurant website work for every visitor?

It must load quickly on a phone and be usable by everyone, including people who use screen readers or only a keyboard.

Most diners look at your site on a phone, often on the move. Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking, and you can read how this works in Google's mobile-first indexing guidance. So check every page on a small screen first, not last. Buttons should be big enough for a thumb, text should be readable without zooming and the booking form should be easy to complete with one hand. Ask a friend who has never seen the site to book a table on their phone while you watch. You will learn more in two minutes than in an hour of guessing.

Speed matters too. Use a few good photos and not a dozen heavy ones. A slow page loses a hungry visitor quickly. Choose photos that show real dishes in good light, and drop any that add weight without adding appetite.

Accessibility is both good manners and good business. The US Department of Justice's guidance of 18 March 2022 says Title III of the ADA prohibits discrimination against people with disabilities by businesses open to the public. It names the Web Content Accessibility Guidelines as helpful technical standards, and lists common barriers. These are poor colour contrast, colour alone used to give information, images without alt text, videos without captions, inaccessible online forms and mouse-only navigation. Read the DOJ web guidance for yourself. WCAG 2.2, the current version, became a W3C Recommendation in October 2023, and you can find it in the WCAG 2.2 standard.

For a restaurant, here is what that means in practice. Give every food photo a short description in plain words. Make sure text stands out clearly against its background. Do not mark a vegetarian dish with a green dot alone; add the word too. Label every field on your booking form. Check that a visitor can reach the book button using only a keyboard. These are small jobs that make the site better for everyone, including diners squinting at a phone in bright sun. They also cost far less than fixing a complaint later.

How will local diners find a restaurant website?

Local diners find you through Google searches and maps, so your website and your Business Profile must tell the same true story.

Google's guidelines for a Business Profile ask a business to represent itself as it is consistently represented and recognised in the real world, with its real name, address, phone number and hours. Keep those identical on your website, your profile and anywhere else you are listed. Read the Business Profile guidelines before you set yours up.

Google also supports LocalBusiness structured data, which can tell it your hours, departments and other details, as described in its LocalBusiness guidance. And its ranking systems are designed to prioritise helpful, reliable information created to benefit people, not content made mainly to rank, as its helpful content guidance says. For a restaurant, helpful means a real menu, real hours and a real booking route.

That is the short version. For the full picture of getting found, including reviews and the map, read Restaurant SEO in 2026: How to Get More Diners From Google.

You can also check a finished site for the problems that keep pages out of search results with AI Website SEO Tools, which says how to fix each one.

How do you build a restaurant website with AI Web Maker, step by step?

Describe your restaurant, watch the pages appear, then edit the words, photos, prices and hours before you go live. It follows the order of this guide.

1. Start on the homepage of AI Web Maker. Enter your restaurant's name, an email address, a phone number and a short description of what you serve and who you serve it to.
2. Watch it build. AI Web Maker plans the pages, writes the words, chooses the photos and sets up the forms. The Olive Table sample took 54 seconds from a short description.
3. Open the editor. Every page can be changed before going live: the words, the photos, the sections, the services, the prices and the hours. Start with the menu. Replace every dish, description and price with your own.
4. Set up your bookable services. In the Booking Manager, list each kind of table with its length, so diners choose from real options.
5. Add your allergen statement and your story. Write them in your own voice, using only facts you can stand behind.
6. Preview everything. Check each page on a phone, then on a larger screen.
7. Go live. Building and previewing cost nothing. Going live costs $119 a year of hosting, and the domain name is paid separately. Optional AI work, such as extra blog posts, is paid with credits of about $0.65 each.

The editor is where the site becomes yours. The first draft gives you a structure and a starting set of words, and your job is to make every line true. Replace anything generic with the detail only you know: the name of the farm that grows your vegetables, the dish guests ask for by name, the real size of your private room. Then read the whole site once as a stranger would, from the homepage to the contact form, and fix anything that makes you hesitate.

If you want to see a finished result first, open this restaurant website example and click through it. It is a fictional restaurant, so you can judge the structure without any pressure. When you are ready, you can build your own.

Frequently asked questions

How many pages does a restaurant website need?

Six is a good start: home, menu, book a table, events, your story and contact. That is the layout of the Olive Table sample. Add pages only when you have real content for them, such as a gift card page once you actually sell gift cards.

Should my menu be a PDF?

No, not only a PDF. Put the menu on the page as text so it is quick on a phone and easy to read and search. You may offer a PDF as an extra download, but the page itself should carry every dish and price.

Do I have to list allergens on my website?

Rules differ by country, so check your own food regulator. In England, Northern Ireland and Wales, the Food Standards Agency publishes guidance for food businesses on providing allergen information. A clear note on your site about how guests can get that information, and a prompt to tell staff about allergies, is a sensible habit everywhere.

Can I put customer reviews on my restaurant website?

Yes, if they are real. The US FTC rule in force from 21 October 2024 bans fake or misleading reviews and testimonials, and UK law has banned fake reviews since April 2025. Show only genuine reviews and never write them yourself. This is general information, not legal advice.

How much does it cost to put a restaurant website online?

Building and previewing with AI Web Maker cost nothing. Going live costs $119 a year of hosting, and the domain name is paid separately. Optional AI work, such as extra blog posts, uses credits of about $0.65 each.

Can diners book a table directly on the site?

Yes. A visitor picks a service, a day and a time and sends a request, and you accept it or move it in the Booking Manager. For large parties or events, send diners to the enquiry form instead.

What can you do this week to start your restaurant website?

Work through this short plan, one task a day, and you will have a site ready to preview by the weekend.

• Monday: Write your menu as plain text, with every dish, description and price. Mark what is vegetarian or vegan.
• Tuesday: Decide your table types, their lengths, your largest online booking and how far ahead you take bookings.
• Wednesday: Write three or four short paragraphs about how the restaurant began, how you cook and who works there. Use only true details.
• Thursday: Write down your exact name, address, phone number and opening hours, and make sure they match your Google Business Profile.
• Friday: Write a short allergen note and list the occasions and group sizes you can host. Collect a few real photos of your food.
• Weekend: Open the builder, enter your details and let the pages appear. Replace the placeholder words with yours, preview it on your phone and fix anything that is slow or hard to read.

If you want to compare against a finished example while you work, keep the Olive Table open in another tab. When the preview feels right, go live.