Restaurant website content checklist
A restaurant site needs a current menu, real photos of the room and the food, opening hours that match Google, and a clear way to book. Most delays come from menu PDFs and photos.
Where to start
- Brand and legal. Logo files and legal text have the longest lead time, because other people own them.
- Menu. The menu is the most visited page, and its layout drives the rest of the design.
- Gallery. Photos take the longest to arrive and decide how much design room each page needs.
- Visit and contact. It is short and factual, so it can be done the same day while the owner is engaged.
- About. Writing takes thought, so give the owner a week with it while you build the other pages.
The checklist
Home
The first screen has to say what kind of restaurant this is, where it is and how to book, so these answers set the whole site.
- Restaurant name as it should appear Short text, requiredWrite it exactly as it appears on the sign, including any 'The' or accents. The designer uses it in the logo lockup and the page titles.
- One-line description of the restaurant Short text, requiredCuisine, neighbourhood and one distinguishing fact, in under 15 words. For example: 'Neapolitan pizza from a wood oven, two minutes from the station.'
- Hero photo Image upload, requiredOne landscape photo of the dining room at its best or the dish you are known for. At least 2000 pixels wide, no text or logo on the picture.
- Primary action Single choice, requiredPick the one thing a visitor should do first. The home page is built around it.Book a tableOrder onlineView the menuCall us
- Booking or ordering link LinkThe address of your booking page or ordering platform, such as OpenTable, Resy, Tock or your own. Leave empty if guests only phone.
Menu
The menu is the most visited page and the one most often out of date, so it needs a single source the owner will actually keep current.
- Current dinner menu File upload, requiredThe file you hand to guests. A Word or Google Doc export is best because the text can be copied. A photo of a printed menu slows the build down.
- Lunch or brunch menu File uploadOnly if you serve at other times. Mark any dishes that appear on both so they are not listed twice.
- Drinks list File uploadWine, beer, cocktails and non-alcoholic drinks. Include the glass and bottle prices if you want them on the site.
- Dietary labelling you use Multiple choice, requiredTick every label you already put on the printed menu. The site uses the same ones so guests are not told two things.VegetarianVeganGluten freeDairy freeNut freeHalalKosher
- Allergen statement Long text, requiredThe sentence your staff say when asked about allergies. Local rules often require it to appear in writing, so confirm the wording with whoever handles compliance.
- Do prices go on the website Yes or no, requiredIf yes, the designer will need a process for keeping them current. If no, say how guests should ask.
About
Guests read this page to decide whether the place feels like them, so it needs the people and the reason the restaurant exists.
- Story of the restaurant Long text, requiredTwo or three paragraphs: when it opened, who started it and what they wanted it to be. Facts beat adjectives, and a date is worth more than the word 'passionate'.
- Chef or owner photo Image upload, requiredA portrait taken in the restaurant, not a headshot against a wall. Landscape or portrait both work, but at least 1500 pixels on the short side.
- Chef or owner name and title Short text, requiredName and role as you want them printed, for example 'Maria Costa, chef and owner'.
- Sourcing or suppliers worth naming Long textFarms, fishmongers or bakers you buy from by name. Only list those who agree to be named.
Visit and contact
This page answers the question people ask most, which is whether the restaurant is open right now and how to get there.
- Street address Long text, requiredThe address exactly as the post office writes it, with postcode. It must match your Google Business Profile or the map pin will look wrong.
- Opening hours Long text, requiredList every day, with kitchen close times if they differ from closing time. Mention holiday closures you already know about.
- Phone number for bookings Short text, requiredThe number staff answer during service, not a mobile that rings in the back office.
- Email for enquiries Short text, requiredAn address someone reads daily. The contact form on the site sends to it.
- Parking and transport notes Long textNearest station, bus line and where guests park. Two or three lines is enough.
- Step-free access details Long textWhether there is a ramp, a step at the door, an accessible toilet. Guests with mobility needs call ahead if the site says nothing.
Private dining and events
Group bookings are often the most profitable enquiries, so this page needs numbers and rules a planner can act on without calling.
- Rooms or areas available for hire Long textName each space, its seated and standing capacity, and whether it can be booked exclusively.
- Photo of the private room Image uploadSet up for a group, with tables laid, not empty. One landscape image is enough to start.
- Minimum spend or set menus File uploadThe PDF you send to event enquiries today. The designer will turn it into page text so the numbers are searchable.
- Who handles event enquiries Short textA name and email so enquiries go to a person, not a general inbox.
Gallery
Photos sell a restaurant faster than any paragraph, and clients tend to send either too few or too many.
- Food photos Image upload, requiredSix to twelve of your best dishes, shot in daylight if possible. Send originals from the camera, not images saved from Instagram.
- Interior photos Image upload, requiredThe bar, the dining room and any outdoor seating, taken when it is set for service. Avoid pictures with guests whose faces are clear unless they agreed.
- Photographer credit Short textIf a photographer owns the images, give the name and how they want to be credited.
- Permission to use photos online Yes or no, requiredConfirm you own these photos or have written permission from whoever does.
Brand and legal
Without logo files and legal text the build stalls in the last week, so ask for them at the start.
- Logo files File upload, requiredVector files (SVG, EPS or PDF) in colour and in a single-colour version. A logo saved from a social profile will print blurry.
- Brand colours ColourThe main colour from your menu or sign, as a hex code if you have one. If you do not, say which printed item to match.
- Brand fonts FontThe typeface on your menu or sign. If a designer made the menu, ask them for the name and the licence.
- Registered company name and number Short text, requiredNeeded in the footer in many countries. Check it against your bank or tax paperwork.
- Privacy and cookie policy approved Yes or no, requiredSay whether someone has a policy ready, or whether the designer should use a standard template for you to review.
What clients get stuck on
The menu as a photo or a scan
Ask for the file the printer was sent, or the document the kitchen edits. A photographed menu cannot be searched, resized or kept current, and retyping it is the longest job on the site.
Opening hours that disagree
Check the hours against Google, the door and the booking platform before you start. If the three differ, ask the owner to decide once and put the answer in writing.
Photos that belong to someone else
Restaurants often use pictures a freelance photographer took years ago. Ask who owns them in the first week so you are not replacing the gallery the day before launch.
No one owns the menu update
Ask who will change a price at 3 pm on a Saturday. If the answer is nobody, plan a very simple editing method, or the menu will be wrong within a month.
Allergen wording
Staff know what to say, but nobody has written it down. Ask the manager to send the sentence staff use, then have the owner approve it, because this text can carry legal weight.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# Restaurant website content checklist
## Home
- [ ] Restaurant name as it should appear (Short text, required)
- [ ] One-line description of the restaurant (Short text, required)
- [ ] Hero photo (Image upload, required)
- [ ] Primary action (Single choice, required)
- [ ] Booking or ordering link (Link)
## Menu
- [ ] Current dinner menu (File upload, required)
- [ ] Lunch or brunch menu (File upload)
- [ ] Drinks list (File upload)
- [ ] Dietary labelling you use (Multiple choice, required)
- [ ] Allergen statement (Long text, required)
- [ ] Do prices go on the website (Yes or no, required)
## About
- [ ] Story of the restaurant (Long text, required)
- [ ] Chef or owner photo (Image upload, required)
- [ ] Chef or owner name and title (Short text, required)
- [ ] Sourcing or suppliers worth naming (Long text)
## Visit and contact
- [ ] Street address (Long text, required)
- [ ] Opening hours (Long text, required)
- [ ] Phone number for bookings (Short text, required)
- [ ] Email for enquiries (Short text, required)
- [ ] Parking and transport notes (Long text)
- [ ] Step-free access details (Long text)
## Private dining and events
- [ ] Rooms or areas available for hire (Long text)
- [ ] Photo of the private room (Image upload)
- [ ] Minimum spend or set menus (File upload)
- [ ] Who handles event enquiries (Short text)
## Gallery
- [ ] Food photos (Image upload, required)
- [ ] Interior photos (Image upload, required)
- [ ] Photographer credit (Short text)
- [ ] Permission to use photos online (Yes or no, required)
## Brand and legal
- [ ] Logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Registered company name and number (Short text, required)
- [ ] Privacy and cookie policy approved (Yes or no, required)
Questions about this checklist
Should a restaurant put the menu on the page as text or as a PDF?
Put it on the page as text, and offer the PDF as a download. Text can be read by search engines and screen readers, and it loads on a phone in a restaurant with poor signal. The PDF still helps people who want to print it.
How many photos does a restaurant website need to launch?
Twelve is enough: six of food, four of the room and two of the people. More can be added later. Asking for forty at the start delays the launch while the owner chooses.
Related checklists
Cafe
A cafe site needs the menu, the hours and a few photos that look like the place on a normal Tuesday. Most delays come from menu files, allergen wording and an owner too busy to send pictures.
Bakery
A bakery site has to show what is in the cabinet, how to pre-order and when to turn up before the sourdough sells out. The slow parts are product photos, custom cake pricing and holiday order cut-offs.
Catering company
A catering site has to show what the kitchen can serve, for how many guests and at roughly what price per head, then make an enquiry easy. The slow parts are sample menus, event photos with permission and an honest delivery area.