Skip to content
self.md

■ SIGNALS // RADAR SIGNAL

the missing visitor got a ledger

Cloudflare's AEO Visibility Dashboard separates citation, mention, prominence, and operator referral data so site owners can see when AI systems read or recommend their work without sending a visitor back.

Published Updated Read 2 min
■ [!] ON THIS PAGE ▼

self.md radar — 2026-08-07

Cloudflare has put a dashboard around a new kind of absence: an agent reads your site, answers a buyer’s question, and sends nobody back. The useful part is not another score. It is the attempt to separate being named, being cited, and being used without a receipt.

1. the missing visitor got a ledger

sources:

what happened: Cloudflare released its AEO Visibility Dashboard in early access on August 6. It scores Citation Rate, Mention Rate, Prominence, and Share of Voice for answers from Anthropic’s Claude and OpenAI’s GPT, while a separate activity view reports crawl and referral traffic by operator. The implementation uses a category-level prompt panel, reruns models to account for variance, and compares citations and answer text rather than asking a model to grade itself. Cloudflare says the system can expose the awkward pattern of an operator crawling thousands of pages while referring nobody back.

the collision: A public site has always needed proof that it exists somewhere beyond its own CMS. Now it also needs to know whether an intermediary can read it, repeat it, and quietly keep the customer. That does not make Cloudflare’s dashboard neutral, or its metrics gospel. It does make the old comfort of pageviews look thin: the work may be doing its job inside somebody else’s answer while the author sees neither the use nor the handoff.

question left open: when an answer engine becomes the room where a recommendation happens, what evidence should a publisher demand before calling that relationship discovery rather than extraction?

left on the table

  • Meta’s Muse Code beta arrives with multi-agent and auditability claims, but a new terminal agent is still a weak second act after a week of harnesses, review gates, and production permissions.
  • Datasette 1.0a38 fixes a real SQL-injection path involving mixed public and private tables; important maintenance, but too narrow to carry today’s fieldnote.
  • Emacs’ AGENTS.md discussion is a good small institutional instinct: tell assistants to search and analyse instead of generating code where contributions are not welcome. It is a thread, not yet a change.
  • Personal AI OS tools — the control-plane map for personal agents, receipts, memory, and tools
  • Best Claude Code plugins — choose the Claude-specific extensions worth installing, and the ones to skip
  • Browser agents — where browser automation helps, where it lies, and how to keep it observable
agent-discovery public-proof web-publishing signals