What a restaurant website does that a listing cannot

For your trade 6 min read

Your Google listing already has the menu and the hours. Here are the jobs only your own restaurant website can do, and the ones it cannot.

Your listing has the menu, the photographs, the hours, the map and the reviews, and it does all of that without an invoice. So the fair question is what a website is still for, and "presence" is not an answer.

There are things a listing does better than any website will, and a short list of things it structurally cannot do at all. The second list is the whole argument.

What the listing does well, and where it stops

The listing answers where you are, roughly when you are open, how far away you are and what other people thought. For somebody standing on the street at half past seven deciding between two places, that is most of the decision, and you should keep it accurate before you spend money anywhere else.

Where it stops is anything that changes, anything long, and anything in your own words. A listing has no room for a set menu for twelve, no place for the sentence about the kitchen closing an hour before the bar, and no way to take a booking that is not a standard table for two.

If your listing is right, your tables are full and you are turning people away on a Friday, you do not need to pay anybody this month. Come back when the quiet season starts.

Menus move. Prices move, suppliers change, the pasta dish that ran all summer comes off in October. What sits on the internet is usually the version somebody uploaded once.

The common failure is a menu saved as a PDF, which opens sideways on a phone, pinches to a size nobody can read, and takes a call to your designer to change. The other one is a photograph of a printed menu, which looks fine and cannot be read aloud by a phone's screen reader, cannot be searched, and cannot be understood by anything that only reads text.

A menu as plain text on your own page is editable in the time it takes to make a coffee. That single change is often the whole reason a restaurant wants a site.

Whether you are open tonight is a different question from your hours

Your hours are a pattern. Tonight is a fact, and the two often disagree. A private party has taken the room. The chef is ill. The kitchen closes at nine even though the bar runs to eleven. You are shut on a holiday that half your customers assume you work.

One line at the top of your own page, changed by you in under a minute, answers that. It also stops the specific bad outcome where somebody drives across town, finds the door shut, and writes about it.

Keep the listing's hours right as well. Your own page is for the thing the listing has no field for.

Taking a booking without paying for it

Every booking that arrives through a platform costs you something, and you are paying it on a customer who already knew your name and was looking for you specifically.

A booking link on your own page, or a phone number, or a short form that goes to the address you actually read, costs nothing per head. Put it where it is visible on a phone without scrolling, and put the phone number next to it, because a table for six at eight on Saturday is faster explained than typed.

You will not get every booking that way, and you do not need to.

The questions the phone rings for during service

Every restaurant gets the same handful of calls at the worst possible moment. Are you doing gluten free tonight. Have you got a high chair. Can we bring the dog. Where do we park. Is there a step at the door. Do you take cards only. Is there corkage.

Every one of those is a paragraph on a page, and every one of them is a call that does not interrupt a Saturday service. Answer them in plain sentences rather than in a chart.

Allergies are the exception worth writing carefully. Say what you can accommodate, then say clearly that anyone with a serious allergy should call and speak to the kitchen before booking. Never let a web page make a promise the kitchen has to keep on a busy Saturday.

Large tables, private hire and the seasonal inquiry

This is the money the listing cannot handle.

A table for fourteen, a room for a wake, a set menu for an office in December, a christening lunch, a supper club. Those inquiries are worth several ordinary covers each, and there is nowhere in a listing to put a set menu, a minimum spend, a deposit policy or the two photographs of the back room.

A single page with the room capacity, the sample menus, what a deposit is and who to email answers it while you are on service. Without that page, every one of these inquiries arrives as a phone call at seven on a Friday, and some of them do not arrive at all.

Who chose the photograph at the top

On a listing, some of the pictures are yours and some belong to strangers. A blurred photograph of a dish from two chefs ago can sit at the top of your listing for months, and anyone can suggest an edit to your opening hours.

Nobody can suggest an edit to your website. You choose the first photograph, the order, the words, and what the room actually looks like when the lights are down. It is the one place where the impression is under your control.

A short checklist

Menu as text on your own page, not a PDF and not a photograph
One editable line at the top for tonight, holidays and private events
Kitchen hours written separately from opening hours
A booking route you own, with the phone number beside it
Parking, step at the door, high chairs, dogs, cards, corkage, all answered
Allergies answered honestly, with a line asking them to call the kitchen
A private hire page with capacity, sample menus and a deposit policy
The listing kept accurate as well, because that is still the first thing seen

Questions people ask

Do I need a website if my Google listing has everything

If your menu changes, if you take large bookings, or if you ever need to say something tonight that is not on the pattern, yes. If none of those apply and you are full every night, keep the listing right and spend nothing.

Should the menu be a PDF

No. A PDF cannot be read comfortably on a phone, cannot be searched, and cannot be changed by you in a hurry. Plain text on the page can be all three.

Do I need online booking or is a phone number enough

A phone number is enough for a small room. Online booking helps when calls land during service, but only use it if somebody is actually watching the inbox.

Should I put prices on the menu page

Yes, and keep them current. A menu without prices reads as a menu with something to hide, and an out of date price is an argument at the table.

How often does a restaurant site need updating

Whenever the menu or the hours change, and once at the start of each season. That is minutes of work, provided the site was built so you can do it without calling anybody.

My food photographs are taken on a phone, is that a problem

No, provided they are yours and recent. A real plate photographed in your own light beats a stock image of food you have never served.