Websites and marketing for restaurants
Menus that work on a phone, booking that converts, and a listing people can find at the moment they are deciding where to eat.
What usually costs you covers.
- Your menu is a PDF
- It downloads instead of opening, needs pinch-zooming, and is largely invisible to search. Dish names are search terms — someone looking for a specific dish nearby is about as ready to book as a customer gets.
- Your Google listing is doing the work alone
- For "near me" searches the map pack sits above everything. Category, hours, photos and reviews decide whether you appear — and most restaurants set them once and never return.
- Booking takes too many taps
- Every step between "I want to eat there" and a confirmed table loses people. A buried booking button and a phone number that is not a real link both cost covers.
What we do about it.
The site
Menu in HTML, not a PDF. Booking visible without scrolling. A phone number that dials when tapped, and an address that opens maps. Fast on a phone on mobile data, because that is where your customers are.
Local search
Google Business Profile set up properly — primary category, hours including holidays, photos that get refreshed. Consistent name, address and phone everywhere. Restaurant structured data that matches what is on the page.
The pages nobody builds
Private hire and events, dietary requirements, seasonal and set menus. Often the highest-value enquiries a restaurant gets, and usually they have no page at all.
Social that looks like the room
A consistent cadence with real photography of your own food. Stock imagery is obvious and it undercuts a premium room.
We wrote the long version of this as a checklist:local SEO for UK restaurants, including the order we would work through it.
Want more covers.
Thirty minutes, no deck, no pressure. You will leave knowing roughly what it costs and how long it takes — even if you build it elsewhere.
