# What is agent analytics?

> Agent analytics is the record of the AI agents that fetch a website: who came, what they tried, and where they stopped. A browser pixel does not see them.

## What is agent analytics?

Agent analytics is the record of AI agents that fetch a website: which agent, which page, and where it stopped. ChatGPT, Claude, Perplexity and coding agents request the URL directly and do not run the JavaScript a pixel needs, so Google Analytics and PostHog do not show the visit. Wake reads the request on the server or at the edge.

The longer account of why a pixel misses them is [Why Google Analytics cannot see AI agents](/wake/docs/analytics).

## What is Wake?

Wake is agent analytics for websites. It shows which AI agents visit, what they try, where they stop, and what to change so the next one gets through. Watching is free for good. The fixes, the problems and the weekly brief are $100 a month after a 7-day trial, with no card to start.

## How do I see if ChatGPT or Claude visited my website?

Install one file where the site is served: a Cloudflare Worker, Express middleware, or Next.js middleware. Wake names the agent family from the request, then drops the user-agent string. The desk, the API and an MCP connection all read the same rows.

The scan needs no account and no collector. It is at [/wake/start](/wake/start). The install steps are in [Install](/wake/docs/install).

## Why can't Google Analytics see AI agents?

Agents fetch the page the way curl does. A pixel runs only after a browser executes JavaScript. The request is real, and the person who sent the agent may become a customer, and the analytics dashboard stays at zero.

## What is AXO?

AXO, agent experience optimization, is the measurement half of Wake: which agent fetched the site, what it tried, where it stopped, and which fix matches that stop. A conversion is a successful write on checkout, not a page view. Search crawlers are shown and are not counted as agents.

The funnel and the friction labels are in [What AXO measures](/wake/docs/axo).

## What is AEO?

AEO, agent engine optimization, is whether an agent can fetch the site and finish the task: robots.txt, llms.txt, the sitemap, the agent card, and a page whose words are in the HTML. Arrivals are judged by identified agents. A crawler that follows a redirect is counted separately.

## What is GEO?

GEO, generative engine optimization, is how a page gets quoted when a person asks an assistant instead of opening a list of links. Answer engines fetch the page, often without JavaScript, and quote a passage that already answers the question. The files overlap with AEO. The score does not: GEO is the citation, AEO is the visit.

The name and the practical list are in [AEO and GEO](/wake/docs/aeo).

## What is llms.txt?

llms.txt is a Markdown file at the root of a site: one heading, one sentence on what the site is, then links with a reason for each. llms-full.txt is the same index with the page text included. Agents that do not run JavaScript read these instead of an empty page.

How the four files fit together is in [Discovery files](/wake/docs/discovery).

## What does Wake cost?

Watching the agents is free, for good, with no limit on visits: overview, who came, and which pages they read. The changes and the insight, where agents stop, what to fix, and the weekly brief, are $100 a month. Every account starts with 7 days of the whole desk and no card. The scan needs no account.

The full split is on [Pricing](/wake/docs/pricing).

## What does Wake store?

Timestamp, method, page, status, provider family, country, an opaque daily nickname and behaviour signals. Never the IP address, the user-agent string, the path, the query string, the body, the prompt, a cookie or the referrer.

The same list is in [Privacy](/wake/docs/privacy).
