Questions owners ask What should a restaurant website have?

Start with your name and what kind of place you are, whether you're open now, where you are and how to call. Put the menu on the page as text, with prices. Then add your hours and photos. Add reviews too, and answers to the questions diners ask about parking or dietary options. All of it should work well on a phone.

What makes the best restaurant websites good?

They answer a diner's questions in the first few seconds and they're fast on a phone. Above all, they're accurate. Good design helps, but a beautiful site with last year's hours loses to a plain one that's right.

Should I use a restaurant website template?

A template gives you the look. It doesn't give you the content, and the content is what diners and search engines care about. If you use one, budget the time to fill it in properly and to keep it current.

How many pages does a restaurant website need?

Usually five to eight: home, menu, hours and directions, photos, about, reviews, and private events or catering if you offer them. Each one should answer one kind of question well.

What Should a Restaurant Website Have? A Checklist

On the first screen

Your name, and what kind of place you are, in words ("Neighborhood Italian, open since 1998")
Whether you're open right now, and until when
Your address, with a link that opens directions
Your phone number, as a link that dials on a phone
The menu, one tap away
Your ordering or reservation link, if you take either

The pages diners look for

Menu. Text, not a PDF, with prices. Mark the vegetarian, vegan, gluten-free and spicy dishes, and add your allergen note in your own words.
Hours and directions. Every day of the week, with holiday hours posted ahead of the holiday. Say where to park, and where the entrance is if it's hard to find.
Photos. The food and the room, plus the outside so people recognize it. Real ones, described in words for people using screen readers.
About. Who runs the place and since when. A paragraph is plenty.
Reviews. What guests actually said, with your replies.
Private events or catering, if you do them: how many people fit, which rooms you use, and how to ask.

The answers people ask before they come

Can I bring kids? Is there a bar? Do you take reservations? Is it wheelchair accessible? Is there outdoor seating? Can I park? These questions decide where a family or a group ends up, and they're the ones AI assistants get asked too. Answer each one plainly, somewhere a diner can find it.

Under the hood

Built for a phone first, because most diners are on one
Fast, even on a weak signal in a parking lot
Readable with a screen reader, with real text and described images
Structured data (schema.org) on every page, which lets machines read your hours and address as facts
On your own domain, so the name and the history belong to you
The same name, address, phone and hours as your Google Business Profile

What to leave off

Autoplay music and video. A splash page before the real one. The menu as a PDF only. A popup asking for an email address before anyone has seen the food. Stock photos of food you don't serve. Hours that were right two years ago.

How Arara builds to this list

Every item above is part of an Arara site. Arara starts from what's already online about your restaurant, asks you to confirm each fact, and asks the diner questions once. It builds the pages from your answers, phone first, with structured data on every page. See what's on an Arara site, or see what it costs.