Google moves AI Mode hotel booking to a shared protocol

The hotel booking infrastructure behind Google's AI-powered search feature, AI Mode, is moving toward a shared industry standard. According to Search Engine Journal, the Universal Commerce Protocol (UCP) project added a draft of its lodging booking feature to the protocol's GitHub repository on 25 September; according to Google's developer documentation, the company plans to adopt this standard for its AI Mode hotel booking feature in the coming months.

What does the draft cover?

The technical specification, called dev.ucp.lodging.booking, describes how a platform manages a booking session over REST or MCP: creation, updates, completion and cancellation. The announcement lists features such as real-time pricing, availability checks, guest details, occupancy, check-in/check-out dates and special requirements. The draft ties into payment extensions covering deposits, deferred balances and split payments, plus a new cancellation-policy extension. The announcement also credits the Lodging Technical Council, made up of Amadeus, Booking.com, Expedia, Google, Hilton, Marriott and Trip.com.

How will Google use it in AI Mode?

Google began rolling out hotel booking in AI Mode for U.S. English users on 27 August, working with 10 hotel chains and travel platforms. The company's FAQ, updated on 24 September, says it will adopt this standard to power the AI Mode hotel booking feature in the coming months. The first milestone covers a single room; support for multiple rooms is noted as a possible future extension.

What happens to ranking and the customer relationship?

Google's FAQ explicitly states that choosing the booking integration does not influence how a business's properties or rates are ranked; however, listings with UCP integration do gain a direct-booking option. The business remains the merchant of record, keeping its own customer information and booking details, with its own terms and conditions governing the reservation. PCI DSS compliance isn't required for card payments; bookings must be finalized by a person through a trusted interface, except when using UCP's AP2 Mandates extension for agent-led payments.

Impact and recommendations: what should Turkish hotel and travel businesses do?

Although the standard is currently limited to U.S. English and a small set of partners, Google tying its booking infrastructure to a shared protocol rather than a closed system is an early but concrete example of how AI-powered search is being wired into commerce. For hotel chains, health-tourism operators' accommodation partners, and travel-technology teams in Turkey, the first lesson is to keep booking engines flexible enough to speak to open protocols like UCP over REST or MCP; businesses locked into a closed, proprietary booking API today may face a heavier integration burden when adapting to such standards later.

The second point is that, despite Google's statement that ranking is unaffected, the direct-booking option is granted only to integrated listings: marketing and growth teams should treat this not as a ranking signal but as an opportunity to convert AI Mode traffic directly into bookings. The third point concerns data ownership; since the business keeps customer information in its own system, the integration decision should involve customer-relationship teams, not just the technology team. For the basics: SEO, AEO, GEO, AIO, GEM: how do the five disciplines differ?