Protocol InstituteBusiness

Feed · thread · version 2 · updated 18 November 2026

Agent readiness: what assistants read, trust and act on

Session of 16 November 2026. 12 participants, 54 minutes. Guest: Navid Nouhi of Credoble.

Buyers now reach businesses through AI assistants, and many will soon send software agents to compare, book and buy for them. A business in that position needs answers to three questions: what an assistant reads, what it trusts, and what an agent can do on the site. The guest, a growth practitioner with twenty years in paid search, SEO and growth, set out the current answers. The scheduled reading carries over to the next session.

The shift in discovery

  • Zero-click search. More than two thirds of Google searches end on Google, with the answer on the results page.
  • Assistant use at scale. 1.2 billion weekly ChatGPT users (September 2026 figures), before Claude and Perplexity. Between a quarter and a half of consumers use AI to find local businesses, depending on the survey.
  • Prompts replace keywords. An average of 23 words per prompt, with a recommendation as the expected output.
  • Conversion. Adobe: AI referral visits to US retail sites up 138% in a year, with a conversion rate 54% above other traffic. AI referrals remain a small share of total traffic.
  • Non-human traffic. Cloudflare: over half of internet traffic this year from bots and agents, and 1,700% growth in daily agents over one year.

Note: figures as cited by the guest, not checked against the original reports.

A three-layer stack

  1. SEO: crawling, understanding and ranking of pages by a search engine.
  2. AEO or GEO (answer or generative engine optimization): a named, trusted place in an assistant's answer.
  3. Agent readiness: facts and actions (price, booking, purchase) open to software acting for a person. No official standard exists yet. The guest's focus: Google WebMCP, a way for a site to declare the actions on offer to an agent.

Three differences from classic SEO:

  • Rank no longer earns a citation. 38% of cited pages sit outside the top ten results, and 62% of citations come from pages ranked 10 to 100 and beyond.
  • Query fan-out. An assistant splits one question into several background searches, in effect sub-agents, and narrows the answer from the results.
  • Mentions over links. Ahrefs, across 75 brands: brand mentions on the web correlate with AI visibility about three times more strongly than backlinks. Correlation, not proof.

Operating requirements

  • Bot access by purpose. Each vendor runs separate crawlers. OpenAI: GPTBot for training, OAI-SearchBot for its search index, ChatGPT-User for live user requests. A block on training and a block on live retrieval carry different consequences.
  • Text first. Assistants read plain HTML, not content rendered by JavaScript.
  • Technical floor. Sitemaps, clean links, indexable pages, page speed. Current agents browse through virtual machines, so load time still matters to them.
  • Open trust pages. In one audit, a company had blocked its terms and privacy pages from crawlers by mistake. After the fix, traffic rose: these pages signal a real company.
  • One set of facts. Address, phone and prices must match across the site and third-party profiles such as Google Business Profile. A mismatch carries a trust penalty. The guest found inconsistent prices on two pages of his own site.
  • Proof over claims. Assistants favour what generic content cannot fake: first-hand experience, proprietary data, a named expert. Google's E-E-A-T guidance applies, with trust as the top criterion. A new company with no third-party mentions gets no recommendation.
  • Content from customer questions. Meeting notes and FAQs mirror the prompts customers type into assistants. For long-form work such as an open book, quality and verifiable data outweigh format. The guest has no test results for the book route yet.

Discussion

  • Gaming gets harder. One participant: agents do more cognitive work per query and follow each user's own tuning, so a one-size ranking loses ground and gaming loses its payoff. The guest agreed and named a casualty: B2B pricing hidden behind "book a meeting" now works against the seller.
  • Creators as a channel. On creator-driven demand, the guest classed it as paid acquisition, separate from organic work. YouTube transcripts are indexable, though, and rank among the more cited sources in his audits. No measure of impact yet.
  • Legibility versus capture. The sharpest objection: "your incentive is to be fully transparent, but at the end of the day, it's just cash that wins. So what's the move in that game?" A transparent site hands its knowledge to well-funded rivals and to the labs, and an agents.txt claim offers no defence against a competitor's ad budget. With assistants as black boxes, a business has no means to confirm the absence of ad-driven steering. The guest's answer: publish the recipe and keep the method private. The questioner's reply: an assistant can reverse-engineer the ratios from the recipe. On the balance of paid and organic answers in ChatGPT ads, the guest had no answer: "time will tell. Because, ultimately, you gotta pay for those GPUs."
  • Capital has limits. Another participant: even a well-funded player has finite capital and a choice of markets. Product architecture and positioning trade-offs leave niches, and organic reach costs less than ads over the medium term.
  • Monetization unsettled. The guest's read: subscriptions and agent fees ahead of ads in the near term, with Google best placed through decades of Gmail and search data, its own cloud and its own chips.
  • Who the buyer is. The session lead asked whether to sell to people or to agents. The guest: "Ultimately, it's a people business," with agents as the filter on the options people see. Hence "build for clankers."

What this means for protocol watching

An interpretation from this write-up, not stated in the session. Each layer of the stack runs on a protocol with a different owner:

  • crawler rules: robots.txt and per-purpose bots, set by each vendor;
  • trust signals: consistency checks across sources, set by each assistant's ranking;
  • action interfaces: WebMCP and similar proposals, still in draft.

A business controls its own side of each protocol and holds no seat in the rule-setting. The objection on capture is a question about that asymmetry: who sets the protocol, and who pays for exceptions to it.

Open questions

  1. Does transparency to agents pay, or does it transfer value to the best-funded party?
  2. Which monetization model wins for assistants: ads, subscriptions or a hybrid?
  3. Which agent-readiness standard becomes the default?
  4. How can a business audit an assistant's recommendations for paid influence?

Next

  • The deferred reading, Anthropic's Patterns and problems in multiagent systems, carries over to the next session.
  • Guest suggestions. The litmus test: a person who runs an AI-native business. Suggestions go to the channel or through offer a talk.
  • Protocol watch continues: one paragraph per member in the channel every two weeks. Starting questions: the protocol watching guide.
  • Free audit. The guest offers members a free site audit through Credoble.
  • Next session, 30 November: Will Binns on Mru, an operating system for a thousand years of autonomous operation.

References

Anthropic. "Patterns and problems in multiagent systems." 2026. https://www.anthropic.com/research/multiagent-systems.

Google. "Creating helpful, reliable, people-first content." Google Search Central. https://developers.google.com/search/docs/fundamentals/creating-helpful-content.

Source: recording notes from OpenRecapper, the recording bot on the Protocol Institute Discord, and the session transcript, both in the group's repository. Quotes come from the transcript, minus repeated words. The session has a recording.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 0vj1pw7wsjr259g77gd0mw6r76

    Quote line ![[0vj1pw7wsjr259g77gd0mw6r76]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "0vj1pw7wsjr259g77gd0mw6r76", "version": 2}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 2 versions