Website checklist
Restaurant website checklist: what guests need before they choose you
A useful restaurant website answers the small practical questions fast: What is on the menu? Is it open? Where is it? Can I book, order, call, or share the link without fighting the page?
Most restaurant website checklists drift into generic web design advice. That is not what an owner needs on a Tuesday afternoon before printing QR cards, updating Google Business Profile, or sending a menu link to a hotel concierge.
Use this checklist as a practical pass through the site. If a guest can find the menu, trust the details, read it on a phone, and act without confusion, the website is already doing more than many restaurant sites.
First screen: prove the guest is in the right place
The first screen should make the restaurant name, type of food, neighborhood or city, and main action obvious. A guest should not have to inspect the footer to know whether this is the bistro downtown, the takeaway branch, or an old event page.
Keep the useful actions close to the top: view menu, reserve, order, call, get directions, or choose a language. The exact mix depends on the restaurant, but hiding the menu behind a carousel or a vague “discover more” button makes the site feel slow even when it loads quickly.
- Restaurant name and location are visible without scrolling.
- The menu link is one tap away on mobile.
- Hours, address, phone, booking, or ordering paths match the restaurant operation.
- The page still makes sense when a guest lands from Google, Instagram, a QR code, or a hotel recommendation.
Menu: make the live menu easier than a PDF
The menu is usually the reason the guest opened the site. It should be readable HTML, not only a PDF download, screenshot, or image that has to be pinched around on a phone. PDFs can still be useful for print, but they should not be the only public menu experience.
A strong menu page has clear sections, current prices, concise descriptions, dietary notes where the restaurant can support them, and stable URLs that can be used from QR codes, social profiles, and search results.
- Guests can scan sections and prices without downloading a file.
- Dish names, descriptions, prices, and availability are up to date.
- Photos support the menu instead of burying the text.
- Old PDF links are removed, redirected, or clearly secondary.
Mobile: test the actual guest moments
Restaurant traffic is full of awkward moments: one hand on a phone outside the door, bad reception at a table, a guest translating the menu, a parent checking allergen notes, or someone trying to send the link to a friend. Mobile quality is not just a layout question.
Open the site on a real phone and move through the common paths. If the menu takes more than a few seconds to reach, the contact buttons jump around, or the text becomes a wall, fix that before polishing decorative sections.
- Tap targets are large enough for directions, phone, menu, language, and booking links.
- Important text does not sit inside images that translation tools cannot read.
- The menu remains usable on slower connections.
- QR scans land on the right menu or homepage without extra decisions.
Trust details: remove the reasons guests hesitate
Guests look for practical signs that the restaurant is current: accurate opening hours, a real address, recent reviews or social posts, fresh menu details, working booking links, clear payment or ordering expectations, and a site that looks actively maintained.
The site should also handle edge cases. Seasonal closures, special menus, private events, sold-out items, and holiday hours do not need elaborate design, but they do need a place to live so staff are not answering the same questions all day.
- Opening hours are current and match public profiles.
- Address, map link, phone, and social links are correct.
- Reservation, ordering, delivery, or inquiry links go to the right destination.
- Temporary notices can be updated without rebuilding the whole site.
Search basics: help Google understand the restaurant
Restaurant SEO starts with accurate, crawlable information. The site should say what the restaurant is, where it is, what it serves, and which pages matter. A pretty one-page image site gives Google, map results, and accessibility tools very little to work with.
Keep titles, descriptions, headings, menu text, location details, language alternates, sitemap entries, and internal guide links tidy. This is less glamorous than a redesign, but it is often what makes the site more findable.
- Each important page has a plain-language title and description.
- Menu content is text-based and crawlable.
- Location, cuisine, and restaurant identity are clear.
- Language versions use intentional localized pages instead of mixed-language fragments.
Launch checklist before you print or share links
The most expensive website mistakes often happen after the site is “done”: QR cards point at the wrong URL, old PDFs keep ranking, the Instagram link still opens a draft page, or staff discover that prices changed after everything was printed.
Before a public rollout, test the site from the places guests will actually enter. Scan the table QR, tap the Instagram bio, search the restaurant name, open the menu in another language, and ask someone outside the team to find the address and today’s menu.
- Scan every printed QR code before service.
- Check Google Business Profile, Instagram, Facebook, delivery apps, and email signatures.
- Verify redirects from old domains, old PDFs, and previous menu links.
- Keep one owner for menu changes so print, QR, website, and translations do not drift.
Turn the checklist into a restaurant site your team can keep current.
Build a live menu, homepage, QR destination, translated pages, and printable menu from one structured source instead of chasing links across separate tools.