# Pulse ยท September 28, 2026 > Google confirms UCP for AI Mode hotel booking, rewrites Merchant Center account-penalty policy, and quietly pulls a Search API documentation page. Canonical: https://brandonlazovic.dev/pulse/2026-09-28/ Author: Brandon Lazovic Published: 2026-09-28 ## Google Confirms It Will Adopt the UCP Draft Spec for AI Mode Hotel Booking Status: Confirmed | Topics: agentic-commerce, ai-overviews-ai-mode Google's own UCP for Lodging FAQ, updated September 24, confirms it will adopt the Universal Commerce Protocol's lodging-booking draft spec, published by the UCP consortium on GitHub the next day, to power hotel booking inside AI Mode over the coming months. The current release covers one-room bookings only, with multiple rooms noted as a possible future extension. Google states the integration does not affect property ranking, and hotels keep merchant-of-record status and their own customer data. In plain terms: UCP is a shared technical standard so different booking systems can talk to Google's AI the same way, instead of Google building a one-off connection to every hotel chain. Why it matters: For hotel and travel brands this is a distribution decision separate from ranking: opting into UCP determines whether AI Mode can complete a booking on your inventory at all, while Google states plainly it does not change how properties rank. Our take: I already flagged UCP's release cadence in the piece on its fourth schema break: four backward-incompatible releases in eight months is a maintenance commitment, not a finished integration. A hotel chain wiring into AI Mode booking today inherits that same cadence, whatever the FAQ's stable tone suggests. - [Google Developers: UCP for Lodging FAQ](https://developers.google.com/hotels/ucp/faq) - [Universal Commerce Protocol: Lodging Booking draft announcement](https://github.com/Universal-Commerce-Protocol/ucp/discussions/864) ## Google Rewrites Merchant Center Policy Pages Around Account-Level Penalties Status: Confirmed | Topics: product-feeds-shopping Google rewrote its Merchant Center policy help pages, and the misrepresentation page confirms two of the changes directly: enforcement text now warns that a whole account can be suspended rather than only the offending listing, and a new alert states that a bulk appeal on a large offer set risks immediate failure if any violation remains. Search Engine Roundtable's review of the broader rewrite, covering at least seven policy pages, also reports matching navigation across pages and new guidance for merchants who manage appeals through platforms like Shopify. In plain terms: Google used to mostly penalize the one product listing that broke a rule; these pages now say a bad listing can pull down visibility for the whole store account. Why it matters: A bulk appeal is now a single bet on the whole batch instead of a per-product fix, so an unaudited resubmission can cost account-wide visibility rather than one listing. Our take: Account-level enforcement changes the math on a bulk appeal. Once one confirmed violation can fail the whole batch, resubmitting everything at once is riskier than holding back the flagged offers and appealing only what is actually clean. - [Google Merchant Center Help: Misrepresentation policy](https://support.google.com/merchants/answer/6150127?hl=en) - [Search Engine Roundtable: Several Google Merchant Center Policy Documents Updated](https://www.seroundtable.com/google-merchant-center-policy-docs-updates-42167.html) ## Google Quietly Removes Its Web Search Service API Documentation Status: Observed | Topics: organic-search-core, ai-data-stack Google published documentation for a Web Search Service API, letting partners retrieve and display Google Search results as JSON over REST or gRPC, around August 22, then pulled the page by September 20 with no deprecation notice or redirect. The URL still returns a 404 as of this writing, confirmed directly. Google has made no public statement; the removal surfaced through a Wayback Machine capture and community reports, including a LinkedIn post calling it a hard 404 with no redirect and no note. In plain terms: Google briefly had a public instruction page for a tool that let other companies pull search results programmatically, then deleted it without saying why or where to go instead. Why it matters: A documented, unannounced API for pulling raw Google Search results existed publicly for roughly a month, and anyone who built against it in that window now has nothing to migrate to and no notice it was coming. Our take: A documentation page pulled with no deprecation notice usually means it was never meant to be public, not that a product was retired. It is worth watching whether the removal lines up with tighter enforcement against tools that were quietly relying on it. - [Search Engine Roundtable: Google Web Search Service API Documentation Has Been Removed](https://www.seroundtable.com/google-web-search-service-api-documentation-removed-42168.html) - [Google Developers: Web Search Service API overview (now returns 404)](https://developers.google.com/web-search-service/overview)