Google Opens Connected Apps Platform Preview for Search and Gemini

Google Unveils Connected Apps Platform to Enhance Search Integration

On October 28, 2026, Google announced a developer preview of its Connected Apps Platform, offering a single registration and testing system for services that work with the Gemini app and eligible experiences in Google Search. Developers can apply to connect a remote Model Context Protocol (MCP) server or use an Android-specific integration based on AppFunctions. Access is being opened in phases, and an application or approval does not mean a service will immediately appear to every Search user.

What Google Announced on October 28

Google introduced the Connected Apps Platform as a way for more third-party developers to submit services for use in Search and the Gemini app. The company also introduced Google Connected Console, where developers can register, test, manage and submit their integrations for review.

Connected Apps are not entirely new. The October announcement concerns a broader developer onboarding system and another wave of partner integrations, not the first appearance of third-party actions in Google’s AI products.

Google said more than 50 Connected Apps had launched across Search and Gemini, covering activities such as productivity, event tickets, health and fitness. It specifically identified Adobe, Experian, Localiza and Peloton as live in Gemini. Google expected to bring these integrations to Search in the following weeks and announced a forthcoming Calm integration for both products. Those statements are rollout plans, not confirmation that every named app is already usable in Search.

The timing matters: October 28 is the platform announcement date. An individual app’s launch date, eligibility and product availability can be different.

Remote MCP and Android MCP Serve Different Use Cases

Google’s announcement names two integration routes, but the current Connected Console registration guide defines different destinations for each. The distinction is important for developers deciding what to build.

Integration Documented purpose Product reach
Remote MCP server Expose server-hosted tools and authorised account data over a public HTTPS endpoint. Can be configured for applicable Search and Gemini experiences on web, Android and iOS, subject to approval and availability.
Android MCP with AppFunctions Expose functions running inside an Android app, using its on-device state. Google documents this route for Gemini on Android, not as a general Search integration.

A remote integration is the relevant starting point for a service that needs to reach users through a cloud backend. Google recommends it for cross-platform capabilities. Android MCP is a separate option for Android developers who need Gemini to invoke functions inside an installed app. Google’s Android integration guide describes Play app linking, AppFunctions bundles, testing and production release requirements.

Google’s language about building once across products therefore should not be read as a promise that every technical path works in every Google interface. Available surfaces depend on the connection type and the product-specific rollout.

How Registration, Testing and Publication Work

Developers seeking access can apply for the preview. For a remote MCP integration, Google’s documented process includes a reachable HTTPS endpoint, domain verification, application details, authentication configuration where required, tool synchronisation and testing before review.

In Google Connected Console, a developer chooses a connected app category and a connection type. The registration documentation says these choices cannot simply be changed later for the same app. It also allows developers to configure countries, languages and supported Google products for an eligible release. Selecting Search, Gemini or both is not the same as receiving approval for every location or user account.

The console supports developer testing and version management. Google’s console overview also describes access to traffic, latency and error-rate information once an app is live, alongside controls for verified branding and authenticated accounts.

For a server-hosted app, completing setup leads to a review submission rather than automatic publication. Google reviews the integration, and an approved version must be published before it can roll out to users. Android MCP follows a different release process tied to the associated Google Play app. A preview application, a version available to testers and a published integration should not be described as the same status.

Search Availability Is More Limited Than the Announcement Might Suggest

Google’s Connected Apps in Search help page currently describes the feature in AI Mode as available in the United States in English. It also says individual app availability varies by location, language and device. This is narrower than general availability across Google Search worldwide.

Users must be signed into a Google Account. For actions requiring a third-party account, they may need to connect that account and grant the relevant permission. The help page describes connecting an app during an AI Mode request or selecting it from an available list, as well as managing linked apps in Google Account settings. It does not support the blanket claim that every user must first manually enable every approved app through one personalised Search setting.

The user journey also depends on the task. AI Mode can help prepare a grocery cart, playlist or design, while some follow-up actions take users to the connected service to finish. The feature should not be presented as evidence that every transaction will be completed entirely inside Google’s interface.

Google says it will open the developer platform to additional markets and products over time. As of November 4, 2026, that remains a phased expansion, with no verified universal launch date.

What the Platform Changes, and Does Not Change, for SEO

Connected Apps introduce a route for users to access a service’s functions through supported Google experiences. That is distinct from having a crawlable webpage considered for ordinary organic search results. A service might expose a booking or account action through MCP while continuing to maintain webpages for people who want descriptions, prices, eligibility information or other public content.

Google has not said that registering a Connected App improves traditional search rankings, increases AI citations or requires additional schema markup. The platform’s tool definitions and authentication setup have a different purpose from structured data on public webpages. They should not be treated as interchangeable SEO requirements.

The announcement also provides no measured evidence of more organic referral traffic or fewer website visits. Connected Console usage data can help a developer assess interactions with its own integration, but that is not the same as visits measured on a website. Similarly, Google Search Console does not provide a newly announced Connected Apps performance report in the material Google published on October 28.

For website-only publishers without a suitable app or service action, the announcement does not create an immediate engineering requirement. For developers already operating authenticated APIs, the practical change is the opportunity to request access to a new distribution channel, subject to Google’s review and rollout limits.

What Remains Open After the Preview Announcement

The announcement establishes the platform and its onboarding process, but it leaves several business questions unresolved. Google has not published a universal timetable for wider Search access, a guaranteed level of app discovery, or a predictable number of user interactions for approved developers.

The documents reviewed do not establish how Connected Apps are selected for every relevant Search request or whether participating apps receive any advantage in ordinary web rankings. They also do not provide a consistent basis for forecasting website traffic, app conversions or commercial return.

The next verifiable milestones are developer eligibility, product and regional availability, approval of individual integrations, and what each connected service can actually do for users. Those are more useful signals than treating the announcement itself as proof of a new SEO ranking system.

Scroll to Top