For two decades, getting found on Google meant pages, keywords and links. On October 28, Google added a new way in. Its Connected Apps Platform, now in preview, lets developers bring their app's features straight into Google Search and the Gemini app, and the way in is an MCP server. (Google)

How it works

According to Google's announcement and developer page:

Is your SaaS agent-ready? Get your score
  • You build one integration. Developers connect through a cloud-hosted MCP server, or on Android through the AppFunctions APIs. (Google for Developers)
  • Users sign in once. Authorization uses OAuth 2.1, so Gemini can act in your service for a signed-in user, with their real account data.
  • You register and submit in Google Connected Console. Before review, you choose whether your app goes live in Search, the Gemini app, or both.
  • You get numbers back. Once you're live, you can track traffic, latency and error rates, and keep control of your brand with verified logos and authenticated accounts.

Google says it has already launched more than 50 Connected Apps across Search and Gemini, with partners like Adobe, Experian, Localiza and Peloton live in Gemini and a Calm integration coming. Access is opening in phases, so developers have to apply for the preview.

That's what makes this an SEO story. Google is building a listing in its own products, with traffic reporting, and MCP is what you need to get in.

GitHub did the same thing for developers on the same day

Also on October 28, GitHub started rolling out GitHub-verified MCP servers, which it calls connectors, in public preview for Copilot. A user picks a service, signs in once, and its tools work across the Copilot app, Copilot CLI, VS Code, Copilot in the cloud and GitHub Mobile. There's nothing to install and no credentials to manage. (GitHub)

At launch, 26 services were available, including Slack, Figma, Notion, Sentry, Linear, Atlassian Rovo, Cloudflare, Vercel and Work IQ. Copilot uses a connected service's tools whenever they're relevant, "even if you do not mention the service by name." (GitHub Docs)

That last part matters. Being in the list means the agent reaches for your product without being told to.

What it takes to get picked

Neither company has published a list of requirements for being chosen. GitHub doesn't describe how a service becomes verified, and Google is reviewing apps as they apply. Even so, what Google documents and what the launch partners have in common point the same way:

  1. A remote MCP server. Both platforms connect through one. Without it, there's nothing to list.
  2. Sign-in with OAuth. Google's path uses OAuth 2.1, and GitHub's connectors handle sign-in for the user. A setup that relies on copying API keys around won't fit.
  3. Tools that do real work. Google's examples include ordering groceries and making playlists. Agents favour actions over read-only lookups.
  4. A site agents can read. Before anyone lists you, agents and their users have to understand what your product does. That means an llms.txt file, robots.txt rules that let AI crawlers in, public API docs and structured data.

The cost of not being listed

When Search, Gemini and Copilot can act inside a competitor's product and not inside yours, the user doesn't file a complaint. They just let the assistant use whichever tool it can reach. Your usage slips a little each month, and the renewal conversation gets harder. That's ghost churn, and today Google and GitHub both made it easier to fall into.

See where your product stands

Our free Agent Readiness Check scans your site for the signals AI agents look for and gives you a score in about a minute.

Is your SaaS agent-ready? Get your score

Is your SaaS agent-ready? Get your score

Run a free Pryno readiness check on your MCP server