By industry
Restaurant booking button: link out or embed?
Should your restaurant website link to your booking system or embed its widget? How each option works on a phone, speed, Google, and a test.
A restaurant booking button can do one of two things. It can link out: a tap takes the guest to your booking system's own page, where they pick a time and confirm. Or it can embed: the booking system's widget sits inside your website, in a box or a pop-up, and the guest books without leaving. Both work. For most small restaurants and cafés, a clear button that links out is the simpler, faster and safer default, and an embed is worth it only when you have a reason and you have tested it on a phone.
This guide assumes you already use a booking system such as OpenTable, SevenRooms or ResDiary. You do not need to replace it: the question is only how your website hands guests over to it.
Linking out versus embedding, side by side
| Link out | Embed the widget | |
|---|---|---|
| What the guest sees | Your site, then the booking system's page in the same or a new tab | A booking box or pop-up on your own page |
| Setup | Copy one URL into a button | Paste code from the booking system, then style and test it |
| Effect on page speed | Almost none until the tap | The widget's scripts load with your page unless you delay them |
| When the booking system changes | The link usually keeps working | The code may need updating |
| Looks like your brand | Only up to the tap | Partly, within what the widget allows |
For a busy owner, the link-out column has fewer trade-offs.
Option 1: a button that links out
Guests tap Book a table, land on your page in the booking system, choose a time and get a confirmation from that system.
Why it is a good default:
- It is fast. Nothing heavy loads on your site until the guest asks for it.
- It is robust. Booking providers keep their own pages working on every phone and browser. You do not have to re-test after each of their updates.
- It is one URL. The same link goes on your website, your Instagram bio and your Google Business Profile, so every route ends in the same place.
What to get right:
- Link to your restaurant's booking page, not the provider's home page. Guests should land on your name with times showing, not on a search box.
- Say where they are going. A small line such as "Bookings through OpenTable" stops people wondering whether they have left the right site.
Option 2: embedding the widget
Most booking systems offer embed code: a few lines you paste into your site that show availability right on your page.
When an embed earns its place:
- You have a dedicated booking page and want guests to stay inside your design while they book.
- You take events or set menus and want the booking box next to the details.
- You have checked that the widget fits a phone screen without sideways scrolling or a tiny box.
The cost is weight. Google's web.dev guidance on third-party embeds notes that many popular embeds include over 100 KB of JavaScript and some go much higher, that they keep the browser busy while they run, and that they can make the page jump as they load. On a café website that should show the hours and the menu in a second, that matters.
If you embed, do it carefully:
- Put it on one booking page, not on every page. Every other page gets a plain button that links to that page.
- Reserve the space. Give the box a fixed height so the menu text does not jump down when the widget arrives.
- Delay what is not on screen. If the widget sits lower down the page, let it load only when the guest scrolls near it, which web.dev describes as lazy loading.
- Keep a plain link underneath. "Booking box not loading? Book here" with a link to the provider's page. If a script is blocked or slow, the guest still has a way in.
- Give it a title for screen readers. If the widget is an iframe, it should have a descriptive title, such as "Table bookings", so assistive technology can announce it.
Where the button goes
Whichever option you choose, the placement rules are the same:
- In the first screen on a phone, near your opening hours, not three scrolls down.
- One main button. "Book a table" in your strongest colour. Order online, gift vouchers and catering can be quieter links.
- On every page, including the menu page, because that is where people decide to book.
- With a fallback. A phone number that dials when tapped, for large groups and people who would rather call.
If you take walk-ins only, say so in the place where a button would be: "No bookings, walk-ins welcome". A missing button with no explanation makes people guess. For the rest of the page, see what a café website must have.
How it connects with Google
Many bookings never start on your website. They start on your Google Business Profile in Search or Maps. Google's help pages say a profile can hold links for bookings and reservations, alongside a menu link and links for food orders. On Search you choose the Booking option; on Maps you choose Edit profile and then the type of link, add the URL and save. Some links appear automatically when a booking provider has a partnership with Google, and the options you see depend on your business category.
Use the same booking URL on Google as on your website, so both routes land on the same page with the same times.
Keeping your name, address and phone number identical everywhere helps here too; we explain why in name, address, phone consistency.
A five-minute test you can run tonight
Pick up your phone, switch off Wi-Fi so you are on mobile data, and:
- Search for your restaurant and open your website.
- Time how long it takes to see the booking button without scrolling.
- Tap it and book a table for two for next week, all the way to the confirmation screen.
- Go back and do the same from your Google Business Profile.
- Cancel both bookings.
If any step was slow, confusing or broken, fix that first. It usually matters more than the choice between linking and embedding.
What it costs
Linking to your existing booking system is part of building the site. A one-page website suits a café or restaurant whose guests mostly need the menu, the hours and the button; a business website adds pages such as a booking page for events. These are Realtiq's published prices, in Australian dollars:
Prices in Australian dollars. Every proposal is confirmed in writing before we start.
Your domain, hosting and booking accounts stay in your name. If you are weighing up how many pages you need, read what pages does a small business website need, or see our page on websites for restaurants and cafés.
Common questions
Will embedding the booking widget help my Google ranking?
Nobody can promise that, and the booking box itself is usually loaded from the provider's domain, so it is not really your content. What helps people find and choose you is a fast page with real menu text, accurate hours and a profile on Google that matches your website.
Should the booking button open in a new tab?
Either works. On a phone, opening in the same tab is simpler and avoids people losing track of tabs. If you use a new tab, keep it consistent across the site.
Can I have both a link and an embed?
Yes, and it is a sensible set-up: a plain button on every page that links to one booking page, where the widget is embedded, with a direct link to the provider's page underneath as a fallback.
What if I do not take bookings?
Say so clearly where a button would normally be, for example "Walk-ins only, no bookings". Add your busiest times if you know them and a phone number for large groups.
Talk it through, 15 minutes
Book a 15 minute call to talk through a website for your café or restaurant.