Google Lets Apps Work Inside the Answer. Ranking Was Only Step One.

For a year I have measured whether AI answers cite my clients. On October 28, 2026, Google changed what the answer can do.

Google launched the Connected Apps Platform in preview, a single place for developers to build and manage apps for Search and the Gemini app. Chips Mistry, Group Product Manager for Search, and Mai Lowe, Group Product Manager for the Gemini app, announced it on Google's blog. A developer connects through a cloud-hosted MCP server or Android MCP using the AppFunctions APIs, then registers, tests, and submits the app in a new Google Connected Console, picking before review whether it goes live in Search, the Gemini app, or both. Once live, the console tracks traffic, latency, and error rates, and the developer keeps control of brand identity, including verified logos and authenticated accounts.

Google says more than 50 Connected Apps have launched between Search and Gemini, largely in Gemini so far, with Search expansion coming. Adobe, Experian, Localiza, and Peloton are live in Gemini and reach Search in the coming weeks. Calm is slated to launch across both. Access opens in phases, with more developers, markets, and Google products coming over the coming months, and developers sign up for the preview at developers.google.com/connected-apps.

A citation and a callable service are two different gates

A citation puts your page in the answer. A connected app puts your service inside the answer, able to advance the task the user asked about inside it: ordering groceries and making playlists are Google's own examples, with final steps sometimes handing off to the app itself.

Winning the first gate does not win the second. A citation is earned by content, structure, and authority. I read a callable service as three gates, and ranking clears none of them. First, someone builds the integration, an MCP server or an Android AppFunctions integration. Second, it passes Google's review in the Connected Console (full review criteria not stated in the announcement). Third, the user connects the app. Barry Schwartz flagged this in Search Engine Roundtable's October 28 coverage: building an app does not mean it appears for searchers. The user must have access and connect it through their personalized Google Search settings. That last gate belongs to the user.

So the new surface runs on permission, not page rank. Google has not described any ranking between competing connected apps, so do not assume page rank carries over. A small service with a working integration and willing users can sit inside the answer next to a brand ten times its size, and the best content on the web earns nothing here until it builds the integration and earns the connection.

What Google did not say

The announcement is short. Google says nothing about how Search or Gemini picks between two competing apps that could handle the same request, nothing about fees or revenue share, and no countries or date for general availability beyond phased access over the coming months. Coverage after the announcement reported the preview is limited to developers in the United States first, citing TechCrunch and Android Authority, but Google's own post names no country, so treat the US-first read as reported, not confirmed.

Anyone selling "Connected Apps SEO" as a ranking tactic is selling something Google has not described. The platform changes how a service reaches a user inside an AI surface. It does not change how pages rank, and nothing in the announcement makes an integration a ranking signal. Keep the two surfaces separate, because conflating them is how budgets get spent on the wrong gate.

I wrote about Google's Universal Cart moving checkout into Search, which put checkout inside Search at participating stores. Connected Apps put the service itself inside the result. Checkout covered one task; Connected Apps extends the same pattern to any task with a built, reviewed, connected integration, one at a time.

What I am adding to my Monday measurement

My measurement habit is a fixed prompt panel I run every Monday: the same money questions, across ChatGPT, Gemini, Perplexity, and Claude, logged in and logged out, three samples each, for clients and for dalindegraff.com. It is how I caught citation shifts early in the GEO campaign at First Rank that lifted LLM search traffic 98% in 30 days. Connected Apps adds one column to that panel. It records whether the answer ended in a citation, a link, or a task advanced or completed inside the answer.

That column changes what I report to a client. A citation with no action is a mention. A task completed inside the answer may never register as a website session, even though it is a conversion. If you only track sessions, the most valuable outcome this platform produces is invisible to you. Log the task outcome by hand until a tool does it.

A Winnipeg therapy clinic I work with grew calls 300% through local SEO, and many of those calls start as a booking question. Today that question ends in a call or a click to a booking page. A connected booking action would advance that booking inside the answer itself. The clinic has no such integration yet. The patient wants booking done, not reading about booking, and the business that makes that task completable inside Search removes a step its competitors still charge the user.

What to do this week

Four steps, in order, and none of them require waiting for general availability.

First, list the tasks your customers ask an assistant to do, not the pages they visit: booking, checking availability, designing, tracking, ordering. If your list is "read our blog," you have no task to connect.

Second, check whether those tasks already exist as something a machine can call. A booking system with an API, a structured product feed, a service catalog with real availability data. If the task only exists as prose on a page, an integration has nothing to call. This is the same entity-and-identity discipline behind winning Google's official-site box in AI answers, applied one step further.

Third, sign up for the preview and read the documentation at developers.google.com/connected-apps, even if you are not a developer. The preview is reportedly US developers on a waitlist first, so a Canadian sign-up may only queue you for a later phase. The sign-up tells you whether your market is in an early phase, and the docs tell you what an integration requires before anyone quotes you a build.

Fourth, add the task-outcome column to whatever you already use to track AI visibility. Log citation, link, or task outcome per question, per engine, per week. When connected apps reach your category, that column is the record that shows whether the surface is sending you work or just mentions.