Google’s Open Hotel Booking Standard: Transforming AI Mode for Seamless Reservations

| Editorial Team On 30 Sep, 2026

Google to Adopt Open Hotel Booking Standard for AI Mode Over Coming Months

Google has confirmed plans to adopt the Universal Commerce Protocol's newly published Lodging Booking draft specification to power hotel reservations directly inside AI Mode — a move that could reshape how travelers book accommodations online.

The announcement follows UCP's September 25 release of its Lodging Booking draft on GitHub, giving hotels and travel platforms their first public look at the technical standard underpinning Google's AI-driven booking ambitions. For hotel marketers and travel platforms already watching Google's growing footprint in commerce, this development signals a significant shift in how reservations may be initiated and completed through AI-powered search. As real-world examples of artificial intelligence in business continue to multiply, Google's move into transactional AI represents one of the most commercially consequential deployments yet seen in consumer-facing search.

What the UCP Lodging Specification Actually Does

The dev.ucp.lodging.booking specification outlines how a platform manages booking sessions through REST or MCP protocols. It covers the full lifecycle of a reservation — creation, updates, completion and cancellation.

Core capabilities defined in the draft

Key features described in the draft include:

Real-time pricing and availability checks
Guest details and occupancy data
Check-in and check-out date handling
Special requirements and preferences

The spec also connects to payment extensions released on August 25, covering deposits, deferred balances and split payments — alongside a new extension specifically for cancellation policies.

The draft incorporates shared UCP components such as identity linking and payment handlers. Notably, the spec states that PCI DSS compliance is not required for card payments processed through this framework — a detail that will matter to payment and compliance teams evaluating the integration.

Human oversight and data stability

One important guardrail is built into the spec: bookings must be finalized by a human through a trusted interface unless the UCP AP2 Mandates extension is used for agent-led payments. This reflects a broader industry caution around fully autonomous AI transactions, particularly in high-value categories like travel.

The draft carries a warning that data models and bindings may evolve with breaking changes still possible — a reminder that this remains an early-stage document open for public feedback.

The Lodging Technical Council credited in the announcement includes some of the most prominent names in travel: Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com.

How Google Intends to Integrate the Standard

Google's FAQ, updated September 24, describes the first milestone as a single-room booking. The company confirmed: "Over the coming months, Google will adopt this standard to power its hotel booking feature on AI Mode." Multiple-room bookings are referenced only as a potential future extension.

Google first launched hotel booking inside AI Mode for U.S. English users on August 27, working with 10 hotel chains and online travel platforms. The September 25 draft is the standard Google intends to formalize for that feature going forward.

Commercial terms businesses need to understand

For hotels and travel businesses evaluating the integration, several commercial questions have now been answered in Google's documentation.

Joining the UCP integration does not influence how properties or rates are ranked in listings. Only entries with UCP integration receive the direct booking option within AI Mode — making adoption a functional prerequisite for appearing in that placement, rather than a ranking signal.

The business retains its position as merchant of record. Customer information, booking details and terms and conditions remain under its control. Google highlights that lifecycle events shared through the API allow businesses to distinguish which traffic and payments originated from Google's AI surfaces versus their own website or app — a meaningful distinction for attribution and analytics teams. For organisations investing in AI-powered business intelligence tools and platforms, this level of source-level attribution data represents a significant opportunity to sharpen performance reporting across channels.

Technical and payment requirements

Before the final booking button appears, Google verifies real-time price and availability through the partner's API. Businesses do not need the Google Pay API on their own site, but their payment provider must support processing Google's tokens.

For now, Google's UCP for Lodging page directs interested businesses to join a waitlist, with detailed onboarding instructions described as "coming soon." Given the pace of development in this space, early registration is advisable for any business that wants to influence its own readiness timeline.

The Timeline That Led Here

From protocol to product

The Lodging Technical Council was formally established on August 11. UCP's August 25 release introduced the structural foundation needed to expand the protocol beyond retail commerce. As of August 31, the lodging specifications were still in active development with no public release timeline confirmed.

Google connected hotel booking to UCP as early as May at Google Marketing Live. However, the August 27 launch post did not specify whether all integrated partners were already operating on the protocol — a gap this draft now begins to address publicly.

The draft is currently open for community feedback on GitHub. Neither Google's FAQ nor its lodging page provides a confirmed date for when AI Mode will fully transition to the standard, or which existing AI Mode booking partners will migrate first.

Understanding how tools like these fit into a broader digital strategy is increasingly relevant — teams already familiar with Google's most effective tools for business growth will be better positioned to evaluate how AI Mode integrations fit within their existing channel mix.

Three developments worth monitoring

Watchers of this space should track the following milestones:

A stable lodging specification release from UCP
Google formally opening onboarding beyond the current waitlist
Additions to the booking spec, beginning with the multi-room extension

Each of these will mark a meaningful step toward AI Mode becoming a mainstream booking channel — rather than an early-access feature available to a limited set of partners.

How you can use this information:

Hotel and travel marketers should join Google's UCP for Lodging waitlist now to position their properties for direct booking placement inside AI Mode before the standard is broadly adopted.
SEO and attribution teams can leverage the UCP lifecycle event data through the API to cleanly separate Google AI Mode bookings from organic and direct traffic — closing a significant measurement gap.
Travel technology developers should review the UCP Lodging Booking draft specification on GitHub and submit feedback during this public comment period to influence how the final standard handles edge cases relevant to their platforms.