A post doing the rounds this week calls ChatGPT plugins the biggest free distribution channel of 2026. For a software startup, that may turn out to be true. For a coach, a course creator or a local business with only a website, the real question is simpler: does any of this apply to me?

Yes, potentially, but not because ChatGPT suddenly promotes ordinary websites as plugins. You don’t need an app to build one. You do need something useful ChatGPT can actually do, and OpenAI’s rules make plugins a poor fit for selling courses or subscriptions.

Key Takeaways

What actually changed at OpenAI DevDay?

Plugins got a bigger home inside ChatGPT and better discovery. OpenAI’s DevDay 2026 recap says plugin extensions give a plugin a home in the sidebar with interactive panels, and that improved ranking and recommendations help people find relevant plugins in the directory and in conversations.

The recommendation part is an upgrade, not a launch. When OpenAI introduced apps in ChatGPT in October 2025, it already said ChatGPT could suggest apps when they were relevant to the conversation. What changed is how well that ranking works and how much a plugin can do once it is open.

OpenAI’s own docs say how a plugin gets that treatment. The plugin guidelines state that plugins with strong real-world utility and high user satisfaction may be eligible for directory placement or proactive suggestions, and an August 21, 2026 entry in the ChatGPT release notes says rankings now prioritise plugins people keep using after installation.

OpenAI also said at DevDay that developers can now reach its collective 1.2 billion weekly users. That is enormous potential distribution, but it is not a plugin audience figure. OpenAI has not published how many of those users discover, install or use plugins.

Is this good for your business if you only have a website?

Yes, but not in the way the plugin hype makes it sound. You do not need an existing app to benefit from ChatGPT’s plugin ecosystem. A business with only a website can build a plugin, but the website itself does not simply become one.

The distinction matters. A website gives ChatGPT information it can discover and cite. A plugin gives ChatGPT functionality it can use.

You don’t need an app. But you do need a function.

A Pilates studio might have nothing more than a website today. If its booking system exposes live availability, a plugin could let someone ask ChatGPT for open classes.

A tax firm could connect a calculator or a client workflow, and a consultant could expose a proprietary assessment. None of those businesses needs to launch a conventional app first.

But if your website mainly explains who you are, what you offer and why someone should hire you, building a plugin just to appear inside ChatGPT probably makes little sense. Your first job is still making the website easy for ChatGPT to access, understand and cite.

OpenAI’s crawler documentation says OAI-SearchBot is used to surface websites in ChatGPT’s search features, and that sites opted out of it will not be shown in ChatGPT search answers. So allow OAI-SearchBot, make important content available in the HTML a crawler receives, clearly identify your business and services, and use appropriate structured data.

So there are really two opportunities:

You can do the first without the second. Only build the second when you have a genuine function worth exposing.

Even then, the plugin route usually runs back through a website. For plugins backed by an MCP server, OpenAI’s submission requirements ask for an HTTPS product website, support page, privacy policy and terms of service, all identifying the same publisher.

Local service businesses have one more path, and it is not one they build themselves. OpenAI has published a Get Quote spec, in beta with approved partners, where a Get Quote button can appear on a local business card in ChatGPT. The partner supplies the business data, including your website URL, and must have a configured partner plugin before ChatGPT shows the button.

When is a ChatGPT plugin worth building?

When you have a task, not a message. OpenAI’s guidelines say a plugin should do something the product cannot already do on its own and should help with common requests people make in conversation.

That filters out most ideas a coach or creator would reach for first. ChatGPT can already write a workout plan, draft a sales email or explain a concept. A plugin that does those things adds nothing.

The function needs to offer a useful capability, specialised workflow or access to information that ChatGPT cannot provide on its own, such as live data from your system, a proprietary method, or access to an existing customer service. That last one matters for creators, because OpenAI’s rules allow users to sign in to an existing paid account and use what their subscription includes.

The bar is also high. OpenAI says plugins must be stable, responsive and complete, rejects trial and demo plugins, and requires a verified individual or business identity for every public submission.

MCP-backed plugin submissions are subject to additional requirements, including five positive and three negative test cases, a demo recording, domain verification and automated checks. With ranking weighted toward continued use, a novelty plugin that people try once is unlikely to benefit from that ranking signal.

Who should own your business’s ChatGPT plugin?

The business should. If you build a plugin for your business, treat it as a business asset, the same way you treat your domain.

An employee, agency or developer can help build and manage it, but the business should retain control of the accounts, verified identity, domain and infrastructure the plugin depends on. Do not leave a core distribution channel owned solely through an outside developer’s personal account.

This matters because OpenAI’s submission process explicitly asks you to select the organization and project that will own the plugin. Publishing under a company name also requires business verification, and MCP-backed plugins require domain verification plus website, support, privacy and terms pages that identify the same publisher.

The platform already separates access from ownership. Organization owners can submit plugins, while other members can be granted Apps Management Write permission, so a developer can do the work inside an organization the business controls.

Ownership also means having the code. If a studio or developer builds your plugin, the handover should include the full source, meaning the plugin package and the code for any MCP server behind it, ideally in a GitHub repository your business owns.

A package file on its own is not enough. OpenAI requires the MCP server to run at a public HTTPS address and the package only points to it, so if that server sits on the developer’s hosting, they still control whether your plugin works.

Put it in writing. The development agreement should explicitly cover source-code ownership, intellectual property rights, hosting access and handover responsibilities, because access to a GitHub repository does not by itself establish legal ownership of what is in it.

That is our recommendation, not a platform rule. The practical version is simple: let people manage it. Don’t accidentally let them own it.

What can’t a plugin do for a creator business?

It cannot sell your course. OpenAI’s plugin guidelines say plugins may conduct commerce only for physical goods, and that digital products, subscriptions, digital content, tokens and credits are not allowed, including through freemium upsells.

A plugin also cannot display your plans, start a new subscription or promote an upgrade. It may explain that a feature needs a different plan and link to an informational page about plans. It may not link to a checkout page.

The lead-magnet idea runs into the same wall. Plugins must not serve ads or exist primarily as an advertising vehicle, and descriptions cannot advertise pricing, free trials or promotions.

None of this makes plugins pointless for creators. It makes them a retention tool for existing customers before they are an acquisition tool for new ones.

How does ChatGPT decide which plugin to suggest?

From your metadata. OpenAI’s Optimize Metadata guide says ChatGPT and Codex decide when to call a tool based on the metadata provided: names, descriptions and parameter docs.

The guide tells developers to start each tool description with “Use this when…” and to state the cases where the tool should not be used. Here is what that looks like for a booking tool:

{
  "name": "booking.check_availability",
  "description": "Use this when the user wants to see open session times with Harbour Pilates Studio in Lisbon. Do not use for pricing questions or general exercise advice.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "date": {
        "type": "string",
        "description": "Requested date in YYYY-MM-DD format, for example 2026-10-14."
      }
    },
    "required": ["date"]
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false,
    "openWorldHint": false
  }
}

The description tells the model exactly when to use the tool, when not to, and what input it needs. The annotations declare that the tool is read-only and does not modify data, and the open-world setting marks it as limited to the studio’s own booking system.

That last setting depends on the implementation. OpenAI says to use true when a tool reaches the public internet or open-ended external entities, and false for a bounded private account or workspace. Either way, the declarations must match what the code actually does, because metadata describes intended behaviour and does not enforce it.

OpenAI also recommends testing against a set of direct, indirect and negative prompts, and tracking precision and recall. The guidelines forbid metadata that tries to steer the model toward your plugin over others, so this is not a keyword game. It is a clarity game.

The discipline is similar to structured data on a website, even though the two feed different systems. In both cases you describe what something is and what it does in a format a machine expects, instead of making it infer.

Frequently Asked Questions

Q: If my business only has a website and no app, does the ChatGPT plugin change benefit me?
A: Potentially, if you have a function worth exposing, such as live booking availability, a calculator or account data. A business does not need an existing app to build a plugin. If your website mainly describes your services, the bigger win is making that website easy for ChatGPT search to find and cite.

Q: Should my developer or agency own my ChatGPT plugin?
A: The business should retain control of the core accounts, verified identity, domain and infrastructure behind its plugin, and should receive the full source code, including any MCP server, in a repository it owns. Developers, employees and agencies can help build and manage it, but avoid making an outside party’s personal account the sole point of control.

Q: Is an MCP connection the same thing as having a ChatGPT plugin?
A: No. An MCP server can provide tools and data to a plugin, but the two are not the same thing. OpenAI says a plugin can include MCP connections, skills or both. Connecting your business account to another company’s MCP server does not by itself give your business its own published plugin in ChatGPT.

Q: Can I sell my online course through a ChatGPT plugin?
A: No. OpenAI’s plugin guidelines allow commerce only for physical goods and do not allow selling digital products or subscriptions, directly or through upsells. Existing paying members can sign in and use what their plan already includes.

Q: Does ChatGPT recommend plugins on its own?
A: Yes, in some conversations. OpenAI says plugins with strong utility and high user satisfaction may be eligible for proactive suggestions, and its release notes say rankings favour plugins people keep using after installation. OpenAI has not published how often suggestions appear.

Q: What happens to the custom GPT I built for my business?
A: OpenAI’s September 11, 2026 release notes announced a planned retirement of custom GPTs, with a migration path to plugins. Check OpenAI’s release notes for the current timeline before you rebuild anything.

Q: Can a local business get a quote button inside ChatGPT?
A: Possibly, through a partner. OpenAI’s Get Quote spec is in beta with approved partners. The partner supplies the business data, including your website URL, and must have a configured partner plugin before ChatGPT can show the button.

Q: Is it too late to build a ChatGPT plugin?
A: Nobody outside OpenAI can answer that yet. OpenAI’s announcement and docs give no figures for how often plugins are suggested in conversation, so any claim about how crowded it is or is not is a guess.

A clear description will not guarantee your plugin gets recommended. But if ChatGPT cannot understand what your business does or when its tools are useful, you have a problem before distribution even begins.

For most businesses, getting that clarity right is the cheaper place to start.

AI Visibility Studio helps websites become easier for AI systems to find, read, and cite. aivisibilitystudio.com

Sources