When a customer searches for your restaurant on Google, the search result shows a "Reserve" button tied to your reservation system. This button vanishes when the API connection fails. Most restaurants lose bookings without realizing the integration stopped syncing. The problem is rarely the reservation software. It's usually a credential rotation, endpoint change, or missing webhook that you don't notice for weeks.
Why Google stops showing your availability
Google uses your reservation API to check real-time table inventory. If the API returns an error or doesn't respond within the timeout window, Google removes the reserve button from your listing. The restaurant sees no notification. Customers clicking your listing on mobile either see no option to book or land on an error page.
The API breaks most often after password resets, timezone changes in your restaurant's profile, or when your hosting provider issues new IP whitelisting requirements. Some third-party reservation platforms rotate their endpoints quarterly without alerting clients.
Set up monitoring before the integration fails
- Check your API key expiration date in your reservation system's developer settings and set a calendar reminder 30 days before renewal
- Test the endpoint manually once a week by visiting your API status page or asking your reservation provider for a health check URL
- Log in to Google Business Profile monthly and verify the "Reserve" button still appears on your listing
- Enable API response alerts if your reservation software offers them, typically in integrations or developer tools
- Document the exact credentials, endpoint URL, and authentication method in a shared file outside the reservation system itself
A broken API connection costs bookings without appearing as an error. Monitoring catches the failure before your customers do.
When the integration needs to reconnect
If you haven't seen the reserve button on your listing in the past month, the integration has likely failed. Log into Google Business Profile, go to Reservations or Booking, and click the option to re-authenticate with your reservation provider. Most systems prompt you to re-enter your API key or approve access again through OAuth.
After re-connecting, allow 24 to 48 hours for Google to validate the new connection and re-enable the reserve button on search results and maps. Test by searching your restaurant name on Google and checking both desktop and mobile.
Track which bookings came through search
Your reservation system should log the source or referrer for each booking. If it doesn't, you can't measure whether the reserve button actually drives traffic. Ask your reservation provider if they track Google as a source or if you can add a custom parameter to the reservation link.
Compare the number of reservations made through the reserve button (shown in Google Business Profile analytics, if available) to total reservations that week. A large gap suggests customers are searching but clicking a different link instead, or encountering friction in the booking flow.
See who Google and AI recommend instead of you
Enter your website and get a free check of what Google and AI actually read about your business — and who they point people to instead. No call, no account: the report renders right on the page.
Run my free check →Share this article
Comments
Leave a comment