Key takeaways
- Put a "Book a table" button in the header of every page, and keep it visible on phones as guests scroll.
- Aim for a booking in five taps or fewer from the home page: party size, date, time, details, confirm.
- Put a tap-to-call number beside the button for guests who would rather talk.
- Test the flow on real phones every month and after every website change.
The button most restaurant sites get wrong
Guests visit restaurant websites for a handful of reasons: the menu, the hours, the address and a table. Yet booking is often buried. In a Cornell study, only 9% of restaurants that took online reservations offered reservation access on their home page[1]. Websites have improved since, but the same problems still show up: a booking link hidden in a menu, a widget that loads below the fold, or a button that opens a page asking guests to download an app.
- Restaurants taking online reservations that offered booking on the home page 9%
Source: Cornell University Center for Hospitality Research (Kimes and Kies), 2012[1]
Show the data
| Item | Value |
|---|---|
| Restaurants taking online reservations that offered booking on the home page | 9% |
The payoff for getting it right is real. In early Cornell research, 59% of restaurants that used online reservations saw sales increase as a result[2]. Operators are investing in the same direction: promoting the restaurant online to attract and keep customers was an investment focus for 64% of full-service operators in 2024[3]. A clear booking button is the cheapest part of that investment.
Where the button goes
| Location | Recommendation | Why |
|---|---|---|
| Site header, every page | Always | Guests land on menu, events or private dining pages from search, not just the home page |
| Sticky bar on phones | Always | Keeps "Book" and "Call" one tap away while guests scroll the menu |
| Home page, first screen | Always | The first thing many visitors want to do |
| Menu page, top and bottom | Recommended | Guests decide to book while reading the menu |
| Private dining and events pages | Use an inquiry form, not the table widget | Groups need a conversation, not a time slot |
| Footer | Optional | Useful, but never the only place |
Use one label everywhere. "Book a table" or "Reserve" are both clear; pick one and use it in the header, the sticky bar and your social profiles. Avoid vague labels like "Visit us" or "Get started".
Make the button look like a button: a solid block in your accent color, large enough to tap with a thumb, with space around it so guests do not hit the menu link by mistake. If you take walk-ins only on some nights, add a short line under the button such as "Bar and patio are walk-in", so guests who find no table online still come by.
How many taps to allow
Every extra screen loses guests. Count the taps from your home page to a confirmed booking on a phone. A good flow looks like this:
- Tap "Book a table".
- Choose party size.
- Choose date, with available times shown at once.
- Choose a time.
- Enter name and phone, then confirm. Email optional unless you need it for a card hold.
That is five taps plus typing. If your flow needs an account login, an app download, a separate page for each step or a CAPTCHA before showing times, it is costing you bookings. Ask your reservation provider whether the widget can open directly on your site, preloaded with the most common party size.
Show availability, not a dead end. If the chosen time is full, the widget should offer the nearest open times and a waitlist or notify option, not just "no availability".
Embed or link out?
Booking widgets come in two forms: embedded on your page, or a link that opens the provider's page. Embedded widgets keep guests on your site and in your design. Linked pages are often faster to set up and more reliable on old website builders. Choose by testing both on a phone; whichever reaches a confirmed booking in fewer taps and loads faster on a weak signal wins.
- If you embed, make sure the widget loads quickly and does not shift the page as it appears.
- If you link out, open the booking page in the same tab on phones; new tabs confuse many users.
- Either way, make sure the booking page shows your restaurant's name and photo, so guests know they are in the right place.
- Check which channel the booking is counted as. Bookings from your own site often carry lower fees than bookings from a platform's consumer app; see reservation platform fees explained.
Keep the phone number next to the button
Not every guest wants to book online, and that is fine. In Cornell research, about two-thirds of diners who had not made an online reservation said they wanted to talk to someone to make a booking[1]. Put a tap-to-call link beside the booking button on phones, and make sure calls are answered in the hours when guests are browsing, which are often evenings and lunch breaks. If the line rings out during service, Ava can answer and take reservation requests so a guest who chose to call is not lost.
Things that block the button
Many restaurant sites have a good button that guests never get to tap, because something else is in the way. Check for these on a phone:
- Newsletter or offer pop-ups that appear before the guest can see the page. If you use one, delay it and never show it on the booking page.
- Cookie banners that cover the sticky booking bar at the bottom of the screen.
- Auto-playing video on the home page that pushes the button below the first screen and slows loading.
- Menus published only as PDF files, which open outside your site and leave the guest without a booking button.
- Chat widgets that sit on top of the confirm button inside the booking flow.
- Several booking links pointing to different systems, such as an old provider on one page and a new one on another.
Fixing these rarely needs a redesign. Most are settings in your website builder or plugins that can be moved or switched off in minutes.
A monthly phone test
Most booking flows break quietly: a website update moves the button, a widget script stops loading, or a pop-up covers the confirm button on small screens. A ten-minute monthly test catches these.
Use two phones
One recent smartphone and one older, smaller one. About 16% of US adults rely on a smartphone for internet access with no home broadband[4], so phones are where your guests book.
Turn off Wi-Fi
Test on a mobile connection, ideally a weak one, to see real load times.
Start from search
Search your restaurant's name, tap your website, and try to book from whatever page appears.
Count taps and seconds
Write down taps from landing to confirmation and how long it took.
Check the confirmation
Did the text and email arrive? Do they show your name, the correct details and a change link?
Cancel the test booking
Use the change link, which tests that too.
Then repeat from your menu page, your private dining page and your maps listing. Note anything that took more than five taps or failed.
Accessibility basics
Restaurants are public accommodations under ADA Title III[5], and guests with disabilities book tables like everyone else. A few basics make the button and widget usable for more people:
- The button is real text, not an image of text, so screen readers can read it.
- Color contrast between the button and background is strong.
- The widget can be completed with a keyboard alone.
- Form fields have visible labels, not just placeholder text.
- There is a way to note accessibility needs, such as step-free seating, in the booking.
Track what the button brings in
Add tracking so you know which placements work. Most reservation systems can record the source of a booking if the link carries a tag. Use a different tagged link for the header button, the sticky phone bar, the menu page and your social profiles, then check covers by source each month. If social profiles bring in bookings, our guide to reservation buttons on Instagram and Facebook goes further. If you are changing providers, replace every button using the checklist in how to switch reservation systems, and make sure direct bookings land in a guest list you control, as explained in who owns your restaurant's guest list.
Example audit result: a restaurant finds its header button works on every page except private dining, where an old widget from a previous provider is still live. The sticky phone bar covers the confirm button on the smallest phone tested. Both are fixed in an afternoon, and direct bookings from the website rise the following month.
Frequently asked questions
Where should the reservation button go on a restaurant website?
In the header of every page, in a sticky bar on phones and on the first screen of the home page. Add it to the menu page too, because guests often decide to book while reading the menu.
How many steps should online booking take?
Aim for five taps or fewer from the home page: open booking, party size, date, time, then name and phone to confirm.
Should I embed the booking widget or link to it?
Test both on a phone and choose the one that confirms a booking in fewer taps and loads faster on a weak connection.
Do I still need a phone number if I have online booking?
Yes. Many guests prefer to call, so put a tap-to-call link beside the booking button and make sure the phone is answered.
References
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑
National Restaurant Association (2024). Where operators plan to invest in tech (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
US Department of Justice (ADA.gov) (2026). ADA Title III Regulations primer (opens in a new tab) ↑