Analytics

Analytics shows how people and AI agents use your docs, and what to write, update, or fix next. Open Admin > Analytics. It needs a paid plan, the Open source plan, or the free trial. Viewers, editors, and admins can open it.

What ContextOwl counts

ContextOwl counts every read on the server, on every channel:

Channel What it covers
Docs pages People who read your docs site, and agents that fetch its pages
Markdown pages Agents that read the Markdown of a page
llms.txt Agents that load the index or the full text
Changelog feeds The RSS feed and the Markdown changelog
OpenAPI files Downloads of the public OpenAPI spec
MCP Agents that call the MCP endpoint, with or without a key
REST API Calls to the REST API, with or without an agent key

Who counts as what

Each request counts in one group:

Tools are integrations and scripts together. The question list and the Not found card show them as one group.

The analytics page

Pick 7, 30, or 90 days or 12 months, and one workspace or all of them.

Where interest is growing

This section shows what people and AI agents ask for more than before. Click People or AI agents to switch between them. Each side has 3 lists:

Pages compare the range with the same number of days before it. Searches and topics compare 30 days at most, because ContextOwl keeps search text for 90 days.

A row rises when all of these are true:

The clearest rise comes first, so a jump from 2 to 20 comes before a jump from 200 to 260. NEW means that nobody asked for it in the period before. Each card states its rule, and each row gives its readers or agents, the change, and its reads or searches. Click View to open a page, Draft to start a page for a search that found no answer, or Hide to remove a row in your own browser.

A list shows not enough data yet when it can't compare:

When Record search text is off, the search and topic lists say so. Integrations, scripts, and AI crawlers never count in these lists.

The AI agents section

The section counts AI agents only, on MCP, the REST API, and the docs site. A line under the tiles gives the calls of cowl, the GitHub Action, and scripts, which don't count as AI agents.

When no AI agent searched or read in the range, the section explains how to connect one.

The question list

See all questions opens Admin > Analytics > Questions. It lists every question of the range, 100 at a time.

Question text is kept 90 days, so the list covers 90 days at most.

Verified agents

Anyone can send the user agent of GPTBot or ChatGPT. ContextOwl checks the claim in 2 ways:

Agents and crawlers shows how many hits of each agent were verified, and the AI agent reads tile shows how many reads were verified. A hit that no check proves still counts, as claimed.

Next steps

Next steps turns the data into work in 3 lists:

Each row says why it's on the list. Hide removes a row in your own browser.

What search learned

Search learns from use. What search learned lists the searches that changed the order of search, with the page that people and AI agents opened after each one, and how many of them did. The card shows what search knows now, so it doesn't follow the range.

To turn learning off for a workspace, or to reset what it learned, open Admin > Settings > Publishing. Search learning needs search text, so it stops when Record search text is off.

Weekly report

Editors and admins get a weekly email with the reads of the week and of the week before, up to 3 rising topics or pages, and up to 3 lines each of Write, Update, and Fix. It covers Monday to Sunday in UTC. A week in which only AI crawlers visited sends no email. To stop it, turn off Weekly docs report in the email settings of your account.

Privacy

For agents

An agent key with the analytics.read permission reads the same data over MCP, the REST API, and cowl:

Task MCP tool cowl
Read the report get_analytics_report cowl analytics report
Read the next steps get_content_insights cowl analytics next
Read what agents asked agent_insights cowl insights
List every question REST only: listQuestions cowl analytics questions

The report includes growth, and the next steps include rising, for people and for AI agents apart.

Any agent that can search your docs can report a question that the docs didn't answer, with report_content_gap or cowl analytics gap. This also works without a key on the public MCP endpoint of your docs site. See Agent Access.