Key takeaways
- Put one Book a table button in the header of every page, and make it work in two taps on a phone.
- Avoid pop-ups and embedded frames that break on mobile or get blocked; a dedicated booking page is safer.
- Guests use your website for practical checks: 44% of consumers aware of the hygiene scheme had seen a rating on a business’s own website[1].
- Tag website bookings by source so you can see which pages and posts bring guests.
What a good booking widget does
A booking widget has one job: turn a guest who wants a table into a confirmed booking, on whatever device they are holding, in as few steps as possible. Most venues have a widget. Many have one that is hidden on a contact page, opens a pop-up that will not close on an iPhone, or still points at a booking platform they left two years ago. The fix is usually an afternoon’s work.
Guests tend to book in the evening and on phones. Restaurants, cafés and bars took 42% of time-stamped consumer spending between 6pm and 6am in an ONS sample week[2], and plenty of the decisions behind that spending are made on a sofa or a train with a phone in hand. Design for that guest first.
Where to put it
- A Book a table button in the site header, visible on every page without scrolling, on mobile and desktop.
- A second button high on the homepage, next to the opening hours.
- On the menu page, near the top and again at the bottom. Menus are where guests decide.
- On every event and offer page, linked to the right date or booking type.
- In your Google Business Profile and Instagram bio, linked to the same booking page.
- In email footers, confirmations and on printed materials as a short link or QR code.
Use the same words everywhere. “Book a table” is clearer than “Reserve”, “Book now” or “Enquire”. Keep a separate, clearly labelled route for private dining and large groups.
Mobile layout that does not lose bookings
| Element | Good | Causes drop-off |
|---|---|---|
| Button | Large, high contrast, always visible | Small text link in the footer |
| Date picker | Calendar that fits the screen | Tiny dropdowns or a picker that scrolls off screen |
| Time slots | Available times shown as tappable buttons | A free-text time field |
| Party size | Simple plus and minus or a short list | A long dropdown with a large group cap hidden |
| Guest details | Name, mobile, email; autofill works | Account creation before booking |
| Policy | One line near the button with a link | A wall of terms the guest must scroll |
| Confirmation | On screen and by email or text at once | A “we will be in touch” message |
Ask for the minimum. Every extra field loses some guests. Name, mobile number, email, party size, date and time are enough for most bookings, with optional fields for allergies, access and occasions.
More than one kind of booking
Most venues sell more than a standard table, and the widget should make each type easy to find without cluttering the main journey. Set up separate booking types in the system and link to them from the right pages.
- Standard tables: the default on every Book a table button.
- Set menus and special dates, such as Christmas or Mother’s Day, with their own terms and deposits.
- Counter or bar seats, if bookable, with a note on what the experience is like.
- Outdoor tables, with the weather policy shown before the guest books.
- Large groups above your online limit, sent to an enquiry form rather than a dead end.
- Private dining and events, with a separate enquiry route and a named contact.
When a guest chooses a party size above your online limit, the widget should say what happens next and offer the enquiry form or a phone number. A message that simply says “no availability” loses the most valuable bookings you could have taken.
Faults worth checking every quarter
- The button on one page still links to an old platform or a dead page.
- The widget shows times when the venue is closed, such as bank holidays.
- The time zone is wrong, so overseas visitors see shifted times.
- The confirmation email lands in spam because the sending domain is not set up.
- Pages load slowly on mobile data because the widget script is heavy.
- The cookie banner covers the Book button on small screens.
None of these show up in a dashboard. They show up as guests who meant to book and did not, which is why a hands-on test by a real person, on a real phone, matters more than any report.
Avoiding broken journeys
The most common failures come from how the widget is attached to the website rather than the widget itself. Pop-ups and embedded frames are the usual culprits.
- Pop-ups: they can be blocked by browsers, hard to close on small screens and break the back button. If you use one, test it on several phones.
- Embedded frames: they can be cut off on mobile, scroll inside the page and lose cookie consent. A full-width embed or a dedicated booking page works better.
- Dedicated booking page: a page on your own domain with the widget filling the width. It is easy to link to, easy to track and works with the back button.
- Third-party pages: if the widget opens on the provider’s site, make sure it shows your name and logo and a way back to your website.
- Old links: search your site, social profiles and Google for old booking links and replace them all.
What else guests check on the page
Guests use your website for practical checks before they commit, and they notice when information is missing. In the Food Standards Agency’s 2025 survey, of consumers who knew the hygiene rating scheme, 44% had seen a rating on a business’s own website[1], and 93% agreed hygiene ratings should be shown on a restaurant’s or café’s own website[1]. Yet only 29% found it easy to find hygiene ratings when ordering food online, against 56% when eating out in person[1].
Source: Food Standards Agency, 2025[1]
Show the data
| Item | Value |
|---|---|
| Eating out in person | 56% |
| Ordering food online | 29% |
Put the basics near the booking button: opening hours, address and map, your hygiene rating, a line on access, allergy information and the phone number. A guest who can answer their own questions on the page books; a guest who cannot often rings, or goes elsewhere.
Tracking website bookings
Tag the source
Make sure bookings from the website are tagged as such in the booking system, separate from Google and platforms.
Add campaign tags to links
Use campaign tags on links from newsletters, social posts and QR codes, so you can see which ones bring bookings.
Track the completed booking
Set up your analytics to record a completed booking as a conversion, not just a click on the button.
Respect consent
If tracking uses cookies, follow your cookie banner settings. Bookings still count in your system even when analytics cannot see them.
Review monthly
Compare website bookings, covers and no-shows with other channels each month.
The booking system’s own source report is the most reliable number. Analytics tools miss guests who refuse cookies, so use them to compare pages and campaigns, not to count total bookings.
Accessibility and security
The widget should work for every guest. Check that it can be used with a keyboard alone, that buttons and text have enough contrast, that form fields have labels a screen reader can read, and that error messages say what to fix. Test it at a large text size on a phone.
The booking system holds guests’ names, numbers and visit history, so protect the accounts behind it. In the 2025 cyber survey, 30% of food or hospitality businesses identified a breach or attack in the previous year[3]. Use individual logins, two-step sign-in and a supplier that keeps the booking pages on secure connections. When choosing a provider, ease of integration and use is what hospitality businesses most often say shapes their technology choices[4]; check that the widget fits your site before committing.
Example: a ten-minute test
Example. The owner of a fictional café-restaurant runs this test on her phone every quarter. She searches for the venue on Google and taps the booking button, then does the same from Instagram and from the website’s menu page. She books a table for two for next Friday, timing how long it takes, then amends and cancels it from the confirmation. She repeats the test on a desktop with only the keyboard. On her first run, the Instagram link went to an old platform and the website pop-up would not close. Both took less than an hour to fix.
Frequently asked questions
Where should the booking button go on a restaurant website?
In the header of every page, high on the homepage and on the menu page, with the same wording everywhere. Link Google and Instagram to the same booking page.
Is a pop-up booking widget a bad idea?
Pop-ups can be blocked or break on phones. A dedicated booking page on your own domain is easier to link to, track and use.
What should a booking form ask for?
Date, time, party size, name, mobile and email, with optional fields for allergies, access and occasions. Do not make guests create an account.
Should our hygiene rating be on our website?
It helps. 93% of surveyed consumers agreed ratings should be shown on a restaurant’s or café’s own website[1].
References
Food Standards Agency (2025). Food Hygiene Rating Scheme (FHRS) Food and You 2 report: wave 11 (opens in a new tab) ↑
Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑