A lot of people choose where to eat on a phone, often standing in the street or sitting in a parked car. They search, look at the map, tap a name, and want three answers quickly: what is on the menu, is it open now, and can I get a table. If those answers take more than a few seconds to find, they tap the next name.
A restaurant website is where those three answers should live, in your words, kept up to date by you. This is what it needs to do, the problems that quietly cost restaurants and cafés their covers, and how to check your own.
Does a restaurant need a website?
Yes, and the reason is control rather than prestige. Every other place your restaurant appears online belongs to somebody else. The map listing is Google’s. The page on a delivery app is the app’s. The reviews sit on a review site. Each one shows your business in its own layout, next to whoever else it wants to show, under its own rules.
Your own site is the one place where the menu, the hours, the booking button and the story are yours. It is also what the other places point back to. Your Google profile links to it, review sites link to it, and AI assistants read it when someone asks where to eat tonight. That is why a website is important for any business, and more so for one whose customers decide in under a minute.
Does a café need a website, or is Instagram enough?
Instagram is good at showing what the food looks like. It is poor at the practical questions. Opening hours sit in a bio or in a story that disappeared yesterday. The menu is a photo of a chalkboard. Nothing on it is in a form Google can match to a search such as “brunch near me” or “dog friendly café”, and anyone without the app may hit a login screen before they see a thing.
Keep the Instagram. Give it somewhere to send people. A café website can be a handful of pages and still answer every question a customer has before they walk in.
What goes wrong for restaurants online?
The same problems come up again and again, and almost none of them look like problems from behind the counter.
The menu is a PDF or a photo
A PDF menu has to download, then be pinched and zoomed on a small screen. A photo of a menu cannot be read by a search engine at all. Either way, Google cannot see that you serve a Sunday roast or a proper vegan menu, so it cannot show you to the people searching for exactly that. A menu written as text on a page loads at once, reads well on a phone, and gives every dish a chance to be found.
The opening hours disagree
The website says one thing, the Google profile another, and the Facebook page still has last winter’s hours. Customers believe whichever one they see first, and the one who turns up to a locked door does not come back. AI assistants cross-check sources too, and when the sources disagree, they guess. Choose one place where hours are changed first, then copy them everywhere else the same day, bank holidays included.
Delivery and booking platforms own the customer
Delivery apps and booking marketplaces bring orders, and they charge for them, usually as a commission on each order or a fee per booking. The bigger cost is quieter. The customer’s details stay with the platform. You cannot tell them about a new menu, and the next time they open the app it shows them every other restaurant in town. Use the platforms for reach if they earn their fee, but make your own site the place regulars go to book or order direct.
No allergen information
For someone with an allergy, a menu with no allergen information is a reason to eat elsewhere. In the UK, food businesses must be able to tell customers about 14 allergens, and the Food Standards Agency’s best-practice guidance for food ordered online is that written allergen information should be no more than one click from the menu. Mark allergens on the menu page itself, and say how to ask about anything that is not listed.
Slow on a phone, outside the door
The person deciding whether to come in is on mobile data, sometimes on one bar of it. A site built around a video background and full-size photos can take long enough to load that they give up and walk on. Speed affects where you rank as well, which we cover in why fast pages win local search.
Instagram is the whole website
It deserves its own line, because it is the most common setup of all. An account can be locked, hacked or quietly shown to fewer people, and none of that is in your control. A website and a domain in your own name are.
What should a restaurant website include?
- The menu, as text. With prices, dietary labels and allergens, and easy for you to update when a dish changes.
- Opening hours and location where nobody has to hunt for them, with a map link and a line about parking or the nearest station.
- A way to book or order direct. A booking button near the top of the page, and a phone number that dials when tapped.
- Photos of the actual food and the actual room, compressed so they load quickly.
- Private dining and events, if you offer them. These are valuable enquiries, and they deserve their own page with their own form.
- Restaurant schema markup. A short block of code that tells search engines your cuisine, hours, address and menu in a format they read without guessing.
- Links to your Google profile, reviews and social accounts, so search engines and assistants can tell they all belong to one business.
What makes good restaurant website design?
Good restaurant website design starts with the phone and works outwards. The menu should be one tap from the top of the page, the hours visible without scrolling, and the booking button where a thumb can reach it.
The look should feel like the room. A neighbourhood café and a tasting menu restaurant should not share a template, because a customer reads the site as a preview of the evening. And it has to be something you can change yourself. A menu that changes every week cannot wait for a web designer to reply to an email.
Why audit your restaurant’s website?
Plenty of restaurant sites are built once and then left. Since launch, the menu has changed, a booking link has broken, and the photos have grown heavier. Nobody notices, because the owner only ever looks at the homepage, on fast office broadband, already knowing where everything is.
Our free website audit checks what a customer and a search engine actually meet: how fast the site loads on a phone, whether the page titles say what you are and where, broken links, schema markup, and whether search engines and AI assistants can read the site at all. It takes about a minute. While you are at it, make sure your Google Business Profile is set up properly, because for most restaurants it is the first thing a customer sees.
Where Onlineify fits
Onlineify is a website product with published prices. A restaurant or café build includes a custom design, a first draft of the copy written for you, Google Business Profile setup, schema markup, and Sanity, an editor where you change the menu, the hours and the photos yourself. The pages are static files on a global network, so they open quickly on a phone outside the door.
On Business and Plus, booking that syncs with your calendar is included, which suits private dining and events. Connecting the site to a table booking system or till you already run is priced as a named line before you pay for anything. There is one build fee, no Onlineify subscription, and every account is in your name. See Onlineify for local businesses, or read what a website costs first.