Skip to content
GPLWP Guides

How to sync WordPress bookings with Google Calendar

Booking & Events Time About 30–60 minutes 6 steps Updated 20 Oct 2026

BOOKING & EVENTS
The short answer

WordPress has no universal booking-to-calendar sync, so your booking plugin must provide a Google integration, an iCal feed, or an API connection. Use two-way sync when Google events must block booking slots; one-way iCal is fine for simple visibility but can lag and will not reliably prevent clashes.

The route
  1. 01Check what your plugin supports
  2. 02Set the calendar and timezone
  3. 03Use the manual route first
  4. 04Connect Google with OAuth
  5. 05Test the complete booking cycle
  6. 06Choose a dedicated sync addon

What you need

  • A WordPress booking plugin that supports Google Calendar, iCal, or an API
  • Admin access to WordPress and the booking system
  • A Google account with access to the calendar
  • The correct WordPress site timezone

Check what your plugin supports

Open your booking plugin’s documentation or settings and look for Google Calendar, calendar sync, iCal, ICS, or external calendar options. There is no single WordPress-wide setting that syncs every booking system with Google Calendar.

Choose two-way sync if events added to Google Calendar must make times unavailable on your booking form. Choose one-way sync if you only need website bookings to appear in Google Calendar.

Set the calendar and timezone

Set the WordPress timezone to the location where the bookings take place, then check the booking plugin’s own timezone setting. Some booking plugins use their sync timezone instead of the general WordPress setting, which can shift appointments by an hour or more.

Choose a dedicated Google Calendar when possible. Confirm that the connected Google account can write to it if the integration will create or update events; Google requires suitable calendar permissions for event creation.

Use the manual route first

If your plugin offers a built-in Google connection, use that rather than building a separate workflow. The usual process is to open the plugin’s calendar settings, connect the Google account through OAuth, select a calendar, and choose one-way or two-way synchronisation.

If it only provides an iCal or ICS feed, copy the booking calendar’s export URL into Google Calendar or copy Google’s iCal URL into the booking plugin. This route is useful for date-based rentals and basic availability, but feeds may refresh on a schedule rather than immediately, and many iCal setups do not support full event editing or dependable conflict prevention.

Connect Google with OAuth

For a native integration, follow the plugin’s connection screen and approve the requested Google Calendar permissions. Some integrations require an HTTPS site, non-Plain permalinks, and a Google Cloud OAuth client before the connection button will work. These requirements are integration-specific, so use the instructions supplied by your booking plugin rather than guessing the Google Cloud settings.

After authorisation, select the exact Google Calendar to use and save the settings. In two-way mode, confirm that the plugin is importing busy events as unavailable booking time rather than merely displaying them.

Test the complete booking cycle

Create a short test booking on the website and check that it appears in Google Calendar with the correct title, date, time, duration, and timezone. Then edit the booking, move it, cancel it, and confirm that each change reaches Google.

Create a separate busy event in Google Calendar and try to book the same time on the website. A proper two-way connection should block that slot. If the integration creates duplicate events, check that the booking plugin is not also connected through an automation service or a second calendar feed. Duplicate events are a recurring sync failure.

Choose a dedicated sync addon

If your booking system is LatePoint and preventing Google Calendar conflicts is essential, the LatePoint Addon – Google Calendar is a suitable route. It is designed for two-way, real-time synchronisation between LatePoint bookings and Google Calendar, with support for multiple calendars and appointment notifications.

Install and activate the addon, connect the Google account from its settings, select the calendar, and repeat the booking, edit, cancellation, and conflict tests above. Keep the manual iCal route when you only need a simple calendar view; use the addon when Google events must reliably affect LatePoint availability.

The fast route

Let LatePoint Addon do it

Two-way, real-time calendar sync for LatePoint bookings; choose it when Google Calendar conflict prevention is essential.

Get LatePoint Addon

Sources

  1. wordpress.org /support/topic/timezone-and-recurring-events-issues/?utm_sou…
  2. developers.google.com /workspace/calendar/api/guides/create-events?utm_source=open…
  3. docs.bookingwp.com /appointments/setup/google-calendar?utm_source=openai
  4. wordpress.org /support/topic/rescheduled-booking-not-syncing-to-google-cal…

Questions

Can WordPress sync bookings with Google Calendar without a plugin?
Not as a general WordPress feature. You need a booking plugin that already supports Google Calendar or iCal, an automation service that can pass booking data between systems, or custom code using Google’s Calendar API and OAuth. Custom API work must store the Google event ID so later booking edits update the original event instead of creating duplicates.
What is the difference between one-way and two-way calendar sync?
One-way sync sends website bookings to Google Calendar but does not normally let Google events block website availability. Two-way sync sends bookings to Google and imports busy Google events so customers cannot book those periods. Check the plugin’s wording carefully because some iCal feeds display events without providing real-time blocking or edit support.
Why are WordPress booking times wrong in Google Calendar?
The usual cause is a timezone mismatch between WordPress, the booking plugin, the server, and Google Calendar. Set the same named timezone in WordPress and the plugin’s sync settings, then test a booking across a daylight-saving change if relevant. Imported ICS events can also contain timezone or recurring-event data that the receiving plugin interprets differently.
Will deleting a Google Calendar event reopen the booking slot?
Only a supported two-way integration can normally use Google edits or deletions to change website availability, and the exact behaviour depends on the booking plugin. An iCal subscription may update later and may only import busy periods, while some integrations require a manual re-sync before changes appear. Test deletion and rebooking before relying on it for conflict prevention.
How do I stop duplicate Google Calendar bookings?
Use one sync route for each booking calendar. Duplicates often happen when a native integration runs at the same time as an iCal feed, automation, or second plugin connection. Also check whether the booking system preserves a Google event ID when a booking is edited; without a stable ID, an update can be mistaken for a new event.