ChatGPT can now use tools on your page. Getting cited did not buy you that.

OpenAI's own Learn page on site tools now says "site tools" are ChatGPT's implementation of the proposed WebMCP standard. In the ChatGPT desktop app's built-in browser, ChatGPT Work and Codex can discover actions a webpage registers — search, edit, compare, update a cart — while you and the agent share the same live page and signed-in session. The Help Center, updated within this window (stamp read ~9:25 AM MT on 27 August 2026 as "Updated: 15 hours ago," so roughly the evening of 26 August MT), is explicit: no extra connection, not in Chrome, not Enterprise or Edu, GPT-5.6 Sol or Terra (Luna has WebMCP disabled), and the tools die when you leave the page.

Chrome's own WebMCP docs, last updated 7 August 2026, still call it a proposed standard and an origin trial from Chrome 149. A form becomes a tool with toolname and tooldescription (declarative API). By default a person still has to click Submit. Moz's 26 August explainer draws the line New Reward actually sells: this is not "showing up in AI-generated answers." Discovery is still citation GEO. WebMCP starts after the agent is already on your page. Search Engine Journal, opening the same story on 27 August 2026, is honest about the gap: OpenAI's documentation does not explain how this might affect rankings, citations, or discoverability.

Two jobs. Do not mash them.

Citation work is already on the Field Guide. Reddit didn't vanish. ChatGPT stopped treating threads like source material. is the volume story. Become the brand AI knows to cite is discovery. Your website now lives inside chat is the older direction: the site has to be readable inside an answer surface.

Today is a different job. When ChatGPT is on the page, does a declared tool exist? Google AI Mode calling your business is also not this post — different vendor, different surface. We already wrote Google AI Mode can call your business.

What OpenAI actually shipped

The Help Center FAQ is the sentence to keep: "No separate connection is required. Site tools are currently available only in the ChatGPT desktop app's built-in browser, not in Chrome." Chrome login does not carry over. Embedded-content tools are not supported. A tool from one page does not travel to the next. The address-bar arrow is gray when tools are available and blue while ChatGPT is using them. Example jobs OpenAI named: search or compare docs, edit a document / whiteboard / notebook, explore a dashboard, build a travel itinerary, update a shopping cart. Each website decides which tools to provide.

Tools belong to the page. Close it or navigate away and they can disappear. If no suitable tool exists, OpenAI says the agent may still use its regular browser capabilities. That is clicking around. It is not a citation, and it is not a "WebMCP ranking" miss.

Website-provided tool definitions and results are untrusted content. Each invocation gets a safety review. OpenAI's wording: those checks reduce risk; they do not make a website or its output trustworthy. Named risks: data exfiltration and prompt injection. Off switch: Settings > Browser > Permissions → Enable site tools.

The spec is a draft from the W3C Web Machine Learning Community Group, not on the Standards Track (SEJ). Chrome still requires clients to visit the site to know if tools exist. Default Permissions Policy is tools=self. OpenAI's community post on 25 August 2026 announced a WebMCP Challenge — $35,000 in cash prizes, due 3 September 2026 at 8:00 PM, winners 23 September. That is a hackathon, not a ranking program.

Audit the actions a buyer already takes

Do not invent a new "agent page." Start with three to five actions a buyer already takes: quote, book, contact, hours or service request. Moz's local example is the same shape: request a quote or book an appointment.

Chrome's declarative path is attributes on the existing form: toolname plus tooldescription. Default: the user still clicks Submit. OpenAI's JavaScript path, from the Learn page opened 27 August 2026: check typeof document.modelContext?.registerTool === "function", then document.modelContext.registerTool with name, description, a narrow inputSchema, annotations: { readOnlyHint: true } on read-only tools, and execute. Preserve the normal interface for people and browsers that do not support WebMCP. If the human form is broken, a tool registration will not save it.

Why good brands disappear from AI search is usually a fetch or entity miss. This week's add: even after the agent is on the page, the quote or book action may still be undeclared.

Do not auto-submit money, bookings, or account changes

Chrome's default is manual Submit. toolautosubmit is opt-in. Moz's 26 August advice: leave it off for anything critical. OpenAI's Help Center names the confirmations: sharing personal information, making purchases, deleting data, changing account permissions, sending messages. Enter passwords on the website, never in the ChatGPT conversation.

That is not a ranking rule. It is the condition under which you ship this.

A check you can run this week

1. Confirm the quote / book / contact / hours form exists, is crawlable, and matches the entity facts you already claim.
2. If you want the ChatGPT desktop path: register a narrow tool on that same form. Keep the human UI.
3. ChatGPT desktop, GPT-5.6 Sol or Terra, built-in browser — not Chrome. Address-bar Site tools arrow: gray = available, blue = in use.
4. Chrome testing flag on the opened docs: chrome://flags/#enable-webmcp-testing. A visit is required; tools are not advertised off-site.
5. Leave toolautosubmit off on money, bookings, and account changes.
6. If no tool matches, the agent may still click around. Do not log that as a citation win or a WebMCP ranking miss.

GEO has a measurement layer now is still the Google half. "Were we cited?" and "could an agent complete the job on our page?" are different jobs.

Allowing SearchBot is not a site tool

OpenAI's crawler docs, re-opened 27 August 2026, have not grown a new bot. OAI-SearchBot is Search. GPTBot is training. ChatGPT-User is a user-triggered fetch — robots.txt rules may not apply, and OpenAI says this user-agent is not used to decide whether content may appear in Search.

Allowing OAI-SearchBot does not register a site tool. Registering a site tool does not put you in ChatGPT Search. AI crawlers are becoming a real SEO signal is the older reporting note. The jobs are still separate.

This is a program

SEO and GEO move together when the same first-party page is crawlable, canonical, and actually does the job. Site tools are an action layer on that page. They are not a citation KPI.

Monitoring is not execution. New Reward — two words — is a visibility partnership, not a one-week attribute blast, and not a promise that ChatGPT Search will start citing you.

If you want the news surface instead of this field guide, that lives on Pulse.

Want this working for your brand? Book the AI-visibility demo, or get your AI-visibility score.