A restaurant owner spends money on photography, a new website and social media. Bookings are steady, but they have no idea which parts of the website help. Is the menu page doing its job? Does anyone read the private dining page? Why do so many people still call to ask about parking?
Measuring which pages lead to bookings and enquiries helps restaurants spend effort where it matters.
Why this matters
Restaurant websites often grow page by page: a menu here, an events page there, a gallery nobody updates. Some pages bring in bookings. Others confuse guests or send them to call. Without measurement, it is all guesswork. Common missteps are covered in restaurant mistakes with online enquiries.
The checklist
1. Know your key pages. For most restaurants: menu, booking, opening hours and location, private dining, events and gift vouchers.
2. Track where bookings start. Your booking system may show where bookings came from. Your website analytics tool can show which pages visitors viewed before booking. Together, they show which pages lead to action.
3. Track where enquiries start. Enquiries about private dining, catering and events are valuable. Note which page each one came from. SpideyChat for restaurants keeps each conversation and captured lead, so you can see which pages prompted them.
4. Look at the questions on each page. If guests on your menu page ask about gluten-free options, your menu needs clearer labels. If they ask about parking on the booking page, add parking information there. These questions are free research.
5. Watch for pages that send people away. High exit rates on the menu page may mean it is hard to read on a phone. A PDF menu is a common culprit.
6. Measure catering and private dining separately. These enquiries are worth more than a standard booking. If they are rare, check whether the pages exist, are easy to find and answer the obvious questions. Catering enquiries are covered in catering and takeaway enquiries from your website.
7. Review every quarter. Look at what changed, especially after menu updates or seasonal events.
Acting on the results
Pages that bring bookings deserve care: keep them current, fast and clear. Pages with lots of questions need more information. Pages nobody visits may need better links from the homepage, or may not be needed at all.
Agencies use the same approach to judge their pages, as described in measuring which agency pages produce real enquiries. The businesses are different, but the method is the same.
Where to put the assistant
Not every page needs an assistant. The menu, booking and private dining pages usually benefit most because that is where guests have questions. The broader question of placement is covered in which pages need an AI assistant.
A monthly habit
Set aside half an hour each month to read through the questions guests asked. Pick the three most common and fix the pages they came from. Over a year, that small habit makes the website far more useful.
Seasonal checks
Measurement is most useful around changes. After a new menu launches, check whether menu questions rise. Before Christmas, check how many party enquiries arrive and which page they come from. If the festive page brings few enquiries, it may be hard to find or missing key details like deposits and set menu prices.
Setting it up
Install the assistant on your key pages and train it on your menu and policies. The guides to installing the widget and training your bot explain how.
Knowing which pages work lets you stop guessing and focus on the changes that bring in more bookings.