Google reservations for restaurants: enable the ‘Reserve a table’ button (and fix it if it’s missing)

January is a tougher month for many restaurants: fewer tourists, fewer spontaneous terrace visits, and guests who search but decide just a bit later. That’s exactly where Reserve with Google shines: someone searches “restaurant + city” and can book immediately via the blue ‘Reserve a table’ button. No calling, no clicking around your site first.

In this guide I’ll walk you through it provider-agnostically: what it is, what you need, how to activate the button, and what to do if it doesn’t show up. In 80% of cases it’s not a big mystery, but a mismatch in name/address/hours, an old connection, or simply waiting time.

What is ‘Reserve with Google’ and where do guests see it?

Reserve with Google is a way for guests to book a table directly from Google (Search or Maps) at your restaurant. You connect your Google Business Profile to a reservation partner (or you use a reservation link), and Google then shows a clear call-to-action.

In quiet winter weeks, this is one of the fastest improvements with minimal hassle: you catch people at the moment they already have intent. They’re not searching for fun. They want to eat, and they want a place now.

Google Search vs Google Maps: where does the button appear?

You’ll usually see the button in two places:

Google Search (desktop/mobile): in the business result (knowledge panel) next to call/directions/website.
Google Maps: in your place profile, often prominently above your photos or under your basic info.

In practice: on mobile this really matters. Especially for searches like “tapas near me” or “Italian restaurant city center”, the venue with a direct booking button wins more often than the venue that only offers “Website”.

What you gain: more direct bookings at the moment of ‘restaurant + city’

This channel is strong mainly because it removes friction:

Guests don’t have to browse your website or menu first.
They don’t have to call during peak times.
They decide faster because Google keeps the booking path tight.

In January that’s extra valuable: hesitant guests click “yes” faster when it’s literally 2 taps.

Check this first: requirements before you can activate the button

If you’re thinking, “I’ve set everything up, but I don’t see a button,” start here. In practice, it’s often not the provider—it’s basic conditions in your Google profile.

Google Business Profile (GBP) verified + correct category (Restaurant etc.)

Make sure your Google Business Profile is verified and your primary category is correct (for example Restaurant, Brasserie, Tapas Restaurant, Sushi Restaurant).

Have you ever changed categories (for example Café to Restaurant)? Then double-check whether Google treats your profile as “bookable”. Category and attributes help determine which buttons Google does or doesn’t show.

NAP consistency (name/address/phone) + opening hours match (mismatch = button won’t appear)

The most common reason the button doesn’t show is a mismatch:

Name in your reservation system differs from Google (for example “Bistro De Markt” vs “De Markt Bistro”).
Address details differ (additions, unit numbers, postal code format).
Phone number differs (with/without country code).
The pin on the map is slightly off (happens more often than you’d think).

Your opening hours also need to be correct. If Google sees “Special hours” that conflict (holidays, adjusted times), it can delay or block your connection.

Choose your route: official ‘Reserve with Google’ provider or just a reservation link

You have two main routes:

Full integration via a Reserve with Google partner (usually the blue button with availability and booking flow).
Only a reservation link (less deep, but sometimes faster and fine as an intermediate step).

Which is better depends on your team (how busy the phone is) and how important availability sync is.

Step-by-step: activate the ‘Reserve a table’ button (provider-agnostic)

The steps below are intentionally provider-agnostic. Whether you use Zenchef, Formitable, DISH, Guestplan, Tableo, Resengo/Tablebooker (or another system that supports Google): the logic is almost always the same.

Step 1: choose (or already have) a reservation provider that supports Google

First check whether your reservation system truly supports Reserve with Google (not just “add a link”). Many restaurants think they have Google bookings, but in reality they only have a website button.

If you mainly have last-minute tables, you’ll often get the most out of a direct Google flow. That’s exactly the type of guest who’s still browsing around in January.

Step 2: connect your provider to your Google Business Profile (select the listing)

This is where it often goes wrong on a detail: you have to select the correct location/listing if you have multiple venues or have moved in the past.

Checklist while connecting:

Is the exact business name correct?
Does the address match letter for letter?
Is this truly the profile with the most reviews and visibility (not an old duplicate)?
Are your opening hours correct, including “special hours”?

If you do this cleanly, you prevent most of the “why don’t I see anything?” frustration.

Step 3: publishing/activation—what’s a normal waiting time?

Don’t expect “instantly live”. In practice, you’ll often see:

24 to 48 hours for the first visibility, or
a few business days before Google shows the button consistently.

Important: if you keep changing things during that period (name, category, opening hours), it can retrigger or delay the process.

Step 4: test like a guest (how to verify everything works)

Don’t test only from your own account.

Test on mobile (where most local traffic is).
Test in incognito or via a colleague.
Test in Maps and in Search.
Click through a full booking and check:
- Is the date and time correct?
- Does the booking arrive in your system?
- Is the language/region correct (useful in tourist areas)?

If the button doesn’t show: troubleshooting checklist (most common causes)

This is where most restaurants end up after a frustrating week. Good news: usually it’s not “broken”, but a concrete mismatch or an old connection.

Listing mismatch: name/address/pin/phone doesn’t match exactly

Pull up your Google Business Profile and your reservation system, and compare:

Name (including “Restaurant”, accents, and characters like &)
Address (street name exact, unit number, postal code)
Phone (same format, preferably consistent with +31 or +34)
Pin location (especially in city centers where Google sometimes places it wrong)

Small differences can be enough for Google not to trust the connection.

Opening hours and exceptions (holidays/special hours) trigger rejection

Check:

Standard opening hours
Special hours (holidays, vacations)
Temporarily closed status

If Google gets signals you’re “possibly closed”, it’s logical that the Reserve button appears less quickly.

You previously connected a different provider (remove/overwrite the old connection)

This often happens after switching (for example from a widget to a full system). Google may still “think” your old provider is active.

Actions:

Check your provider dashboard for old Google connections.
See whether you ever added multiple booking links in Google.
Temporarily stick to 1 clear route: either integration or link. Not both mixed together.

Provider works, but Google still shows nothing: waiting time and re-check moments

If everything is correct, give it time. A practical routine:

Check after 48 hours
Check after 5 business days
Only then escalate (provider support or a deeper audit of your Google profile)

Don’t tweak “something” every hour. Consistency wins here.

Limitations almost nobody talks about (but that impact your planning)

A lot of help docs act like it’s always perfect. In practice, there are limitations you’d rather know upfront—so you don’t end up with angry guests or double reservations.

Book 30 days ahead (often a Google limit)

With many setups, guests can reserve via Google only up to roughly 30 days ahead. Great for weekdays and spontaneous diners, less useful for:

group dinners planned 2 to 3 months ahead,
holiday menus,
tourists who book early.

Solution: make sure your website also has a clear reservation route for “far ahead”.

Not all features work via Google (deposits/no-show flows depend on the provider)

Not every provider feature carries over 1:1 into the Google flow. Think:

deposits,
detailed no-show terms,
extra questions (allergies, table preferences).

If you want to reduce no-shows specifically in quieter months, you want to know which flow is active where—and where it’s better to use your own channel.

Capacity/availability sync can lag (not always real-time)

Some systems don’t sync with Google second-by-second. That can mean:

a table is just gone, but Google still shows it briefly,
or the other way around: capacity exists, but Google is behind.

Especially on Friday and Saturday, it’s smart to keep an eye on this and give your team a simple playbook for the rare case of a double booking.

Conversion boost: get more out of Google reservations than just the button

The button is the start. The win is in measuring, optimizing, and having a fallback route that also converts.

Tracking per channel (Google vs website vs socials): what you at least want to measure

At minimum, you want to see:

How many reservations come in via Google?
How many via your website?
How many via Instagram (or other socials)?

Why this matters: if you run January promos (weekday deal, early bird), you’ll want to know which channel actually fills seats. Without tracking, you’re steering by gut feeling.

Website UX: don’t make Google your only path

Google is strong, but you don’t want to depend on 1 platform. On your site you can:

show your menu clearly,
explain allergens and set menus,
handle group inquiries more easily,
share practical info (parking, high chair, dog policy).

If you notice Google limitations (like 30 days) are holding you back, a restaurant website that increases bookings is a logical second step: keep Google as the entry point, but route guests to a flow you control.

WhatsApp follow-up and no-show reduction: confirmations, reminders, questions

WhatsApp is often the fastest way to remove uncertainty:

“Can we come inside with a stroller?”
“Is 7:30 OK if we’re 10 minutes late?”
“Can this work with an allergy?”

A short confirmation or reminder can reduce no-shows—especially in quiet months when every table counts.

Book a free WhatsApp consult: “I’ll check your Google profile + reservation button and give you a setup/fix plan for more bookings.”

Which reservation software fits ‘Reserve with Google’? (quick selection help, no vendor pitch)

The market is crowded and changes quickly. You also see more consolidation, which can shift features and integrations. Base your choice on your situation, not on one pretty feature page.

When ‘direct via Google’ is ideal (walk-ins/last-minute/locals/tourists)

Direct via Google works well if you:

get many spontaneous guests,
are in a high-search area (city center, station area, tourist district),
want to fill last-minute gaps (January, off-peak hours),
have a team that can’t constantly answer the phone.

When you’re better off using a (live) reservation link instead of full integration

A reservation link is often better if you:

have complex set menus,
get lots of group requests,
use strict no-show rules with deposits,
or if your integration is unstable for any reason.

In that case, it’s often smarter to work from 1 central flow: an online reservation system for your restaurant that aligns your website, Google, and internal planning.

Consolidation: why vendors or switching can affect your Google button

Because reservation software is increasingly consolidating (companies acquiring each other or integrating platforms), this can impact:

what your Google integration is called,
where your settings live,
whether an old connection keeps lingering somewhere.

Practically: if you switch, do it in a fixed order. First align NAP, then remove the old connection, then activate the new connection. Only after that do you fine-tune.

Mini-FAQ

How long does activation really take?

Often you’ll see the button within 24 to 48 hours, but it can also take a few business days. If your profile details change in between (name/address/opening hours), it can take longer.

Can I connect multiple locations?

Yes, but you need to select the correct listing per location and ensure NAP and opening hours are exact per branch. Especially with chains or two venues in the same city, this goes wrong due to duplicates.

What if I have Wix/website reservations?

You can still use Reserve with Google. First decide whether you:

only want a reservation link (simple), or
need full integration via a provider (useful for availability sync).

If Wix is your primary channel, make sure your reservation path is fast and mobile-friendly so Google doesn’t become your only booking route.