We Tracked Every AI Agent That Visited Our Site. 5 Different Agents Found Us This Month.
Three weeks ago, I noticed something strange in our referrer logs.
A user from chatgpt.com had landed on our validator page, browsed our documentation, and — crucially — triggered tool events. Not a human clicking around. An AI agent. ChatGPT had crawled our site, loaded our tool, and used it.
That was one agent. One week. A curiosity.
This week: five.
What showed up (and what they did)
The full lineup of AI agents that visited ucptools.dev in the last month:
ChatGPT (chatgpt.com) — 4 visits this week alone. Most active of the bunch. Browsed documentation pages and the free UCP validator. Triggered actual tool events — someone asked ChatGPT about UCP validation, and it came to us to answer.
Gemini (gemini.google.com) — 1 visit this week. First time we've seen Gemini in our logs. Shorter session than ChatGPT, but it hit the same pages: validator, compare page, docs.
Perplexity (perplexity.ai) — First spotted in May. Here's the wild part: every Perplexity-referred session in May resulted in a tool user. 100% conversion rate. Someone asked Perplexity "how do I validate my UCP profile?" and Perplexity sent them straight to our tool, already knowing what to do.
Claude (claude.ai) — Returned June 14 after a multi-week gap. Browsed our UCP protocol documentation and the agent simulator page. Not using tools yet — but it's building a map.
NotebookLM (notebooklm.google.com) — Newcomer. Discovered us June 7. Google's research assistant found our site and ingested content. We don't know what question triggered it, but something in our content matched a user's research query.
Trend line: 1 → 1 → 5. Not a spike. A ramp.
This isn't about SEO as you know it
If you work in developer tools or e-commerce infrastructure, you've probably spent the last 6 months hearing about UCP, ACP, AI shopping agents, and "agentic commerce readiness." The conversation has been about protocols — can an AI agent parse your UCP manifest? Can it call your payment handlers? Can it add items to a cart?
That's the protocol layer. And it matters.
But here's what the referral data shows: AI agents are indexing your entire web presence, not just your UCP endpoint.
When ChatGPT crawled our validator tool, it wasn't reading a .well-known/ucp manifest. It was reading our documentation, our compare page, our blog posts. It was building a knowledge graph of "what tool exists for checking UCP profiles" that it can retrieve when a user asks.
When Perplexity sent us a user with a 100% tool completion rate, it had already decided — before the human ever saw our site — that UCPtools was the right answer to their question.
This is a new kind of discoverability. Not search ranking. Knowledge base ranking. The question isn't "do I rank #1 for 'UCP validator'?" — it's "when an AI agent needs to answer a UCP question, does it know I exist?"
What this means for developer tools and e-commerce platforms
Five different agents found us without us doing anything to attract them. No agent-specific SEO. No structured data markup for AI crawlers. Just a website with clear, specific content about a niche protocol.
The implication: AI agents are actively hunting for authoritative sources in specialized domains. If you build something in the UCP/ACP/agentic commerce space, the agents will find you — but only if your content is in their corpus.
Three patterns we can already see:
Agents prefer documentation over marketing. Every agent that visited us hit our docs and tools. None touched our pricing page. None visited our blog homepage. They went straight for substance.
Tool usage is the strongest signal. Perplexity's 100% tool-user rate tells us the agent pre-qualified the user — it already knew our tool was the answer. The human didn't browse; they executed.
Multi-agent coverage compounds. One agent finding you is luck. Five agents finding you means your content is propagating across knowledge bases. ChatGPT, Gemini, Perplexity, Claude, and NotebookLM use different indexes and different retrieval strategies. If you're in all five, you're discoverable regardless of which agent a user chooses.
The protocol layer matters too — here's how they connect
We built UCPtools to validate UCP profiles. The core insight was: an AI shopping agent needs a valid UCP manifest to buy from your store. But the protocol layer and the knowledge layer are connected in ways that aren't obvious yet.
Consider this sequence:
- A developer asks ChatGPT: "How do I set up UCP for my Shopify store?"
- ChatGPT searches its knowledge base, finds our documentation (because we're in its corpus), and recommends our validator.
- The developer uses the free validator, finds 3 broken endpoints, and fixes them.
- Now their store is both UCP-valid (protocol layer) AND indexed by the agents that will send them customers (knowledge layer).
Without step 2, the developer might never find the validator. Without step 3, their UCP profile stays broken and AI shopping agents can't transact.
You need both. A valid UCP profile that no AI agent knows about is useless. And an AI agent that knows about your store but can't transact because your payment handlers are broken is equally useless.
How to check if AI agents can find you (and transact with you)
There's no all-in-one dashboard for this yet. But here's what you can do right now:
Check your referrer logs for these domains:
-
chatgpt.com/chat.openai.com gemini.google.comperplexity.aiclaude.ainotebooklm.google.com
If you see any of them, AI agents are already building knowledge about your site.
Check your UCP profile — because being discoverable is pointless if agents can't transact. Our free validator runs 4 levels of checks: structural, rules, network, and an AI agent simulator that actually tests whether an agent can complete a purchase flow.
Check your robots.txt. Most AI crawlers respect robots.txt. If you're blocking GPTBot, ClaudeBot, or Google-Extended, you're opting out of AI discoverability. That might be intentional — but it's worth knowing what you're blocking.
One thing I'm still figuring out
The data is real but the sample is small. Five agents, a handful of visits, one site. This isn't a research paper — it's an observation from our referrer logs that I think matters for anyone building in this space.
What I don't know yet:
- How frequently agents re-crawl and refresh their knowledge
- Whether agent referral traffic converts differently than organic search
- Whether NotebookLM ingestion leads to downstream discoverability in other Google products
If you're seeing AI agents in your own referrer logs, I'd love to compare notes. Drop a comment — especially if you're seeing patterns I haven't mentioned.
The one thing I'm confident about: the agents are here, they're indexing, and they're already making decisions about which tools and services to recommend. The question isn't whether to care about AI discoverability. It's whether you're already invisible.
