You may have read that ChatGPT now finds your site's tools. OpenAI's documentation says that, with limits: only for accounts and models that support it, and only inside the built-in browser of the ChatGPT desktop app. It does not happen in Chrome, and nothing in the documentation connects it to ChatGPT search.
OpenAI's help article on site tools says that when site tools are available to your account, ChatGPT "automatically discovers the tools a supported webpage provides." A conference talk on Nov. 6 put that in front of SEOs as "on by default."
My read is that WebMCP changes what an agent can do once it lands on your page. Nothing published says it changes whether an agent sends anyone there.
The claim came out of TechSEO Connect. SEO consultant Lily Ray posted a line from a talk by Darwin Santos on Nov. 6: "WebMCP discovery is turned on by default for free users - ChatGPT comes to a page and uses WebMCP to understand what tools exist for agents."
OpenAI's page backs the discovery part. It says no separate connection is required, and that users can switch the feature off under Browser settings, then Permissions, then Enable site tools.

It does not name the plans that get site tools. The Free-account detail rests on Santos.
What the default covers
Site tools work only in the desktop app's built-in browser, "not in Chrome," according to OpenAI. They work only on the page that provides them, and only while that page is open. Tools that come only from embedded content are not supported.
Search Engine Journal's August 27 report added model and workspace limits. Reporting on OpenAI's documentation at the time, SEJ's Matt Southern wrote that the feature needs GPT-5.6 Sol or Terra, that Luna has WebMCP turned off, and that site tools are not available in Enterprise or Edu workspaces.
WebMCP is a proposed standard. A site registers tools, and an agent calls them instead of clicking and typing. The tasks OpenAI lists are searching documentation, editing a document, exploring a dashboard, building an itinerary and updating a shopping cart.
What it does not cover
Nothing on the help page describes ChatGPT search results, citations or recommendations. SEJ made the same point: the documentation "doesn't explain how it might affect rankings, citations, or discoverability."
The pitch around WebMCP often blends two jobs. One is being found and named in an answer. The other is letting an agent finish a task once a person has already sent it to your page. Site tools, as OpenAI describes them, belong to the second job.
Chris Long of Nectiv posted on Nov. 5: "AEO Tip: You can actually see whether your competitors are starting to leverage WebMCP." His method is to open DevTools, go to Applications, then WebMCP, then Available Tools.
The practical friction is still open. Agents that fill in forms have to get past the spam checks those forms use, such as Turnstile, and nothing I found says how site tools handle that. OpenAI's own warning points the other way: site tools "may expose functionality not otherwise present on the webpage," which it says carries risks including data exfiltration and prompt injection. OpenAI says it will ask the user to confirm purchases, deletions and messages sent on their behalf.
My take
I think the default-on headline will get read as a visibility story, and so far nothing shows it is one. The recommendation is the outcome that matters in AI search, and no source I found shows that registering a tool earns one.
Where WebMCP could matter is after the recommendation. If a person asks ChatGPT's desktop browser to reorder something or fill in a form, a site with clean tools may finish the job where one without them stalls. Whether that beats a plain backend integration is a question I cannot answer yet. I would keep it in a separate column from citations.
Free newsletter
The Sherpa Brief
One email a week on what changed in AI search, what it means, and what to do about it. Written for marketers, SEOs, and publishers.
Free. Unsubscribe in one click.



