What Should a First Restaurant Website Include?
A practical menu, hours and mobile checklist you can give a designer—and test yourself before launch.
Ryan Speier
A first restaurant website needs a readable menu with prices, accurate hours, the right address and a working way to order, book or call. Put those ahead of an opening animation, a long founder story or an email popup. A guest should be able to decide whether to visit without creating an account.
A September 18 discussion about a brunch cafe website asked what each section should contain and whether anything important was missing. The replies touched on photos, reviews and layout. Here is an owner's acceptance checklist: what to ask a designer to build, and what to test before accepting the finished site. This is a recurring question, not a new search trend.
Build around five guest questions
| Guest's question | What the website should show | How to check it |
|---|---|---|
| What can I eat, and what does it cost? | A current menu with item names, short descriptions and prices; say which menu applies at which time. | Find the price of a main dish on a phone without pinching to zoom. |
| Are you open when I want to come? | Day-by-day hours, holiday exceptions and any different kitchen or pickup cutoffs. | Compare the site with today's actual service schedule and Google Business Profile. |
| Where are you? | Full address, correct map destination and useful entrance or parking directions. | Tap Directions. Verify that the destination is your entrance, not another branch. |
| How do I get food or a table? | Clearly labelled Order Pickup, Order Delivery, Reserve or Call buttons, as applicable. | Follow each button to the correct location and service. A generic platform homepage is not enough. |
| Will this work for my visit? | Practical information about reservations or walk-ins, accessibility, large parties and how to ask about allergies. | Ask the manager whether every stated policy is accurate. |
Only promise services you actually offer. If you are walk-in only, say so instead of displaying a reservation button that goes nowhere. If you have not opened, show the opening status clearly and avoid accepting orders before the kitchen can fulfill them.
A simple homepage you can hand to a designer
The following is fictional sample copy, not a real restaurant listing:
Willow Counter — breakfast and lunch in Exampletown
Tuesday–Sunday, 8 a.m.–3 p.m. Kitchen orders close at 2:30 p.m. Closed Monday.
View Menu · Order Pickup · Directions
Walk-ins welcome. For parties of six or more, call before visiting.
Under that first section, show a few real dishes, a short description of the food, then the location and useful visit details. A founder story can follow. For several locations, give each one its own accurate hours, menu and ordering destination.
Use photos of food and portions you actually serve. Do not borrow another restaurant's food photos or fill the page with invented review counts. If you display a rating, identify its source and keep it current.
Make the menu usable before making it decorative
Prefer menu items written as normal webpage text, with clear section headings and prices. A printable PDF can be an additional option; it should not be the only practical way a phone user can read the menu. Avoid a photograph of tiny print that requires repeated zooming and sideways scrolling.
Be explicit about differences between dine-in, pickup, delivery, breakfast and dinner menus. If prices or availability vary by service, label that. Keep allergy information tied to your actual ingredients and procedures. Do not describe an item as safe for an allergy just because a website template supplied a dietary badge.
Run this phone test before launch
Ask someone who did not build the website to use it. Watch where they hesitate; do not tell them which button to press.
- Find tomorrow's hours. Can they distinguish opening time from the last kitchen order?
- Choose a meal and identify its listed price. Is the menu legible without sideways page scrolling?
- Find the entrance. Does the map go to the right building and branch?
- Start an order or reservation. Check the location, service type and dates. Stop before submitting unless you have arranged a real test with the team; do not create a surprise kitchen ticket or occupy a table.
- Call the restaurant. Check the displayed number and the dial screen; coordinate any test call with staff.
- Use the site with a keyboard. Can they reach the menu and buttons, see which control is selected and dismiss overlays without a mouse?
- Try a narrow screen and larger text. Make sure buttons, menu prices and important instructions remain visible.
Repeat the critical checks on more than one phone/browser where possible. Also open the site on a mobile connection rather than relying only on office Wi-Fi. These checks are useful acceptance tests, not a complete accessibility audit.
Give Google accurate information
Use a descriptive page title such as “Willow Counter | Breakfast and Lunch in Exampletown,” with the real business and place substituted. Keep the restaurant's name, address, phone number and hours consistent with its Google Business Profile. Google's local ranking guidance recommends complete, accurate business information and identifies relevance, distance and prominence as important factors.
Ask the developer to verify that the public pages return successfully, are crawlable and do not accidentally contain a noindex instruction left over from staging. A private administration or unfinished preview page can appropriately stay out of search; the finished public menu and location pages should not inherit that setting.
If the developer adds Restaurant structured data, it should describe the information visible on the page. Google's LocalBusiness documentation shows how hours, address and menu information can be supplied. Markup is not a promise of enhanced results or a top ranking. Never invent ratings to fill it.
Assign upkeep to a person
A correct launch can become an incorrect website after the next menu change. Keep a short update sheet:
Change: ____________________
Effective date and time: ____________________
Person approving the information: ____________________
Website updated and checked: ____________________
Google Business Profile checked: ____________________
Ordering/reservation platform checked: ____________________
Printed menus and staff briefing checked: ____________________The owner should control the domain and know who can renew it and edit the website. The manager should be able to report a closed kitchen, holiday hours or a wrong price without waiting for a redesign.
Track useful actions such as clicks on the menu, directions, ordering and reservation links if your analytics setup supports them and respects visitors' privacy choices. A click is not a completed sale or a seated guest. Use confirmed orders and reservations separately when evaluating the site's business results.
For the work surrounding the website, use the free restaurant opening plan and the guide to finding your first paying customers. The website is ready when a guest can get accurate answers and take the next step, and someone is responsible for keeping it that way.
Source question and scope
Prompted by a September 18, 2026 public discussion about a brunch website; question and available relevant replies read September 19. The checklist and fictional example are original guidance, not an audit of that cafe or a claim that it has these problems. Google documentation checked September 19, 2026. No search-volume, conversion lift or ranking result is claimed.