Agent distribution is developing across search, tool catalogs, browser interactions, and commerce. There is no single switch that makes a business available to every agent. This briefing records what we checked on September 13, 2026. It is an editorial snapshot, not a live news feed or a claim that we tested every platform.
Google has more specific AI controls and reporting
Google's newer Search Console help documents say its Search generative AI control and Search generative AI performance report rolled out worldwide on August 31, 2026. The control covers inclusion in specified generative Search experiences; the report shows impressions for AI Overviews and AI Mode, with eligibility and data-volume qualifications. Consult the control documentation and report documentation.
Practical implication: inspect the actual property settings and report available to your account. Do not repeat the older blanket claim that AI participation has no separate control or that no AI-specific reporting exists. Impressions still do not establish qualified traffic or sales. Google's general search fundamentals remain relevant; a newer feature-specific document can change an older summary.
MCP compatibility now needs an explicit version check
The current MCP versioning documentation identifies revision 2026-07-28, using per-call protocol versions. This differs from the initialization model in older revisions. A published specification does not establish support in a particular host or SDK. Record both sides of the connection before advertising compatibility. See the versioning documentation and our compatibility checklist.
Practical implication: old snippets can remain useful when explicitly pinned to the older version. Mixing an older connection lifecycle with newer request fields is a poor integration plan. A successful documentation review is not a successful live connection.
WebMCP is a browser integration experiment
Chrome documents a WebMCP origin trial from Chrome 149, alongside a local development flag. This is more specific than the early-preview announcement, and less than universal browser support. Chrome documentation.
Practical implication: evaluate it for an existing website workflow with a named compatible browser and agent. Preserve ordinary forms and accessible navigation. A page exposing tools still needs a way for a user or agent to reach that page.
Discovery specifications are changing too
Agentic Resource Discovery was announced in June 2026. The ARD main-branch specification reviewed here describes revision v0.91 and a current /.well-known/ard.json publishing path; older material refers to ai-catalog.json. Main-branch documents can change. ARD specification.
Practical implication: compare the implementation you intend to reach with a pinned revision. A valid manifest, a registry ingestion event, and an independent agent finding your business are three different observations. Our ARD assessment recipe explains how to test the actual route.
Commerce discovery and checkout remain separate
OpenAI's product file-upload documentation describes catalog data for purchasable variants. Feeding product information does not itself enable checkout; merchant participation and transaction integration have separate requirements. Product specification.
Practical implication: establish item identity, price, availability, and landing-page agreement before investing in a transactional interface. Do not announce support for purchases in a particular assistant until the actual merchant account, region, integration, and confirmation path have been verified.
What to prioritize this week
| Situation | First useful investment | Evidence to collect |
|---|---|---|
| Important pages cannot be retrieved | Fix the specific access or rendering failure | A successful permitted fetch with useful content |
| Agents confuse the offering | Reconcile facts and publish task-specific documentation | Correct answers with supporting sources |
| A known tool is difficult to use | Repair authentication, inputs, and result retrieval | An authorized task completed correctly |
| The basics work but exposure is weak | Test a relevant search, catalog, or ecosystem route | An observed introduction without naming the provider |
| A new protocol looks promising | Run a bounded compatibility experiment | A named consumer actually reading or using it |
These priorities are our judgment, not platform ranking rules. We have not published a customer outcome study establishing their relative lift. Use the evaluation guide to produce evidence for your own business and update the decision when the evidence changes.
Primary sources
Put the next step to work.
Find your starting point