How to audit your restaurant marketing yourself
Guide menu and contents
In 90 minutes you can find a point where your restaurant loses potential guests. Test one real journey from search to seating on a phone and compare what you find with the reservation system and till. Leave with three fixes, a named owner for each and a way to retest.
Choose a service and a guest scenario
Pick one location, visit type and time slot. Two people might be looking for dinner nearby on Wednesday at 7.30 p.m., with a menu they can see before booking. Another scenario is a neighbour looking for a weekday lunch within walking distance. Record the language the guest will use for the search.
Ask someone who rarely visits your restaurant to try the task on their own phone. Have them say what they expect to happen next. Watch where they hesitate, which price and location they see and where they stop. Arrange any test booking with the front-of-house team in advance and cancel it in the system.
Walk through the guest journey
| Stage | Check | Flag it when |
|---|---|---|
| Find | Name, address, entrance, opening hours, phone and current photos. | The listing opens a different location, says it is closed when it is open or leaves guests unable to find the entrance. |
| Choose | How to reach the menu, ingredients, prices and language options. | Guests see an old menu, struggle to read it or have to ask for prices. |
| Book | Available date and time, party size, confirmation and changes. | The booking link fails, the details disappear when changing language or guests cannot understand the confirmation. |
| Visit | Directions, entrance, special conditions and what happens on arrival. | The terms shown online differ from what staff tell the guest. |
Repeat the task from the restaurant’s Google profile and one ad currently driving meaningful traffic. If you offer delivery and bookings, test a real task for each.
Reconcile the website, bookings and till
For four comparable weeks, collect enquiries, confirmed bookings, seated tables, covers and revenue for the chosen service. Keep the units distinct: a booking for six is one table and six guests. Track advance cancellations and no-shows separately. Use the date of the visit for reporting.
Example: of 60 confirmed dinner bookings, 9 cancelled in advance, 6 did not show and 45 arrived. Among the bookings still active at service, the no-show rate was 6 ÷ (60 − 9), or about 11.8%. Record the denominator so the team measures the same thing before and after the changes.
Prioritise the fixes and run the test again
For each problem, record how often it happens, what it costs the guest and how hard it is to fix. If the website has the right price and Google links to an old PDF, correct the link first. If the booking system needs longer work, provide a working alternative with an expected response time and test it on a phone.
Example handover: New guest comes from Google and finds a closed form. Link to the location’s working booking calendar. Owner: restaurant manager. Acceptance: a test booking from Android and iPhone reaches the reservations log and receives confirmation.
Repeat the original journey after every critical fix and measure again in two weeks.
Want a team to help market your restaurant?
Use this guide to make the changes yourself. If you want help finding where you’re losing diners and turning the plan into action, OliveMKTG can connect your website, menu, Google profile, content and ads to measurable table bookings.
Talk to us about restaurant marketing