Hotel booking inside AI Mode is headed toward a shared industry protocol rather than a Google-only pipe. A draft of the Universal Commerce Protocol’s Lodging Booking feature landed on GitHub on September 25, and Google’s own developer FAQ, updated September 24, states that “over the coming months, Google will adopt this standard to power its hotel booking feature on AI Mode.” That is a plan, not a rollout, and neither document sets a date.
The stakes sit with anyone who depends on hotel demand from Google. AI Mode already books rooms directly inside a chat answer for U.S. English users, a feature Google launched August 27 with 10 hotel chains and travel platforms. Moving that flow onto an open spec means the booking mechanics stop being proprietary to Google and start being something Booking.com, Expedia and individual hotel groups can build to once, then plug into multiple AI surfaces.
The dev.ucp.lodging.booking draft covers real-time pricing, availability checks, guest details, occupancy, check-in and check-out dates, and special requirements, managed through REST or MCP calls that create, update, complete or cancel a booking session. It links to payment extensions for deposits, deferred balances and split payments introduced in UCP’s August 25 release, plus a new cancellation-policy extension. According to Google’s FAQ, this first milestone covers one room per booking, with multiple rooms “potentially as a future extension.” Search Engine Journal reported that the Lodging Technical Council behind the spec includes Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com.
Two commercial questions get settled in the FAQ, and both matter more to search teams than the technical schema does. First: “Opting for our booking integration does not influence how we rank your properties or rates in listings,” Google states, keeping UCP adoption separate from listing rank at least as described. Second, the hotel keeps its status as merchant of record, so it does not hand over its customer list, its booking records, or the contract terms that govern the stay. Google adds that lifecycle events shared through the API let a business tell UCP-sourced traffic and payments apart from bookings made through its own site or app, and that it checks real-time price and availability with the partner before the final “Book” button appears.
That separation between ranking and booking integration is the detail worth testing rather than accepting. Google is the party defining both the ranking system and the booking protocol, and the FAQ offers no independent measurement of whether listings with direct-booking capability get more visibility, more clicks, or more trust from users inside an AI answer, even if the ranking formula itself is untouched. A hotel that can complete a reservation inside the chat, without a redirect, has a functional advantage the ranking algorithm does not need to grant it.
For OTAs, a shared lodging standard cuts the engineering cost of plugging into Google’s AI surfaces while the merchant-of-record rule keeps the resulting customer relationship with whichever partner actually closes the booking. For individual hotel brands, it raises the question of whether to integrate directly and control those terms, or let an OTA’s existing UCP connection carry their inventory into AI Mode instead. Businesses will not have to run the Google Pay API on their own site, per the FAQ, though their payment processor has to be capable of handling Google’s tokens. The FAQ also notes that AP2, Google’s protocol for agent-led payments, can sit inside UCP as one way to handle future automated transactions, but it stops short of making that mandatory.
Google has not published a firm switch-over date, an onboarding process, or a list of which current AI Mode booking partners will actually move onto the new standard. For now, businesses can only sign up for a waitlist through Google’s UCP for Lodging page. The one-room cap applies to this new UCP milestone itself, not to the AI Mode booking feature live since August 27, which Google has not said runs on UCP. Hotel and travel marketers should watch whether Google widens that cap before making the switch, since group and family trips often need more than one room.
Travel SEO and revenue teams should treat the ranking-versus-booking separation as a claim to monitor, not a settled fact, and start mapping which of their current AI Mode booking partners are positioned to move onto UCP first.
Search Engine Journal’s Matt Southern reported this September 28, 2026, drawing on Google’s Hotel UCP FAQ (last updated September 24, 2026).
