AI queries and crawler activity
The AI queries tab shows how readers and AI systems use your published documentation: what readers ask the on-site AI, how often those questions return nothing, and which AI crawlers fetch your content.
Before you begin
You need at least one published site with AI reader features enabled (the AI search or chat widget). See Embed widget.
Open the tab
Go to Analytics in the sidebar.
Open the AI queries tab.
Choose 7 days, 30 days, or All time at the top to change the range.
Read the summary cards
Two cards summarize reader AI activity for the selected range:
Total queries: how many questions readers asked, added up across the queries listed in Top AI queries.
Zero-result rate: the share of those questions that returned no answer, under the sub-label
Searches with no answer. The card turns amber above 30%. Choose it to open the Triage content gaps tab, where you act on what is missing.
Top AI queries
The Top AI queries table lists up to 20 of the most frequent questions, each with:
Column | What it shows |
|---|---|
Query | the question text, lowercased and grouped with identical questions |
Count | how many times it was asked in the range |
Asked on | the page the reader was on when they asked. Choose it to open that page in a new tab. Questions asked through site-wide AI search show Site search instead. |
Last asked | how recently the question was last asked |
Use Asked on to jump to the page a question relates to and improve it directly. A question asked repeatedly on one page usually means that page fails to answer it.
If nothing has been asked yet, the section reads Questions readers ask the AI on your published docs appear here.
AI crawler activity
The AI crawler activity table shows the AI agents that fetched your published site, grouped by crawler:
Column | What it shows |
|---|---|
Crawler | the identified AI agent or service |
Requests | how many requests it made in the range |
Endpoints | which endpoints it hit, as short labels |
Last seen | its most recent request |
The endpoint labels
Label | What was fetched | Public URL |
|---|---|---|
| the page index for AI crawlers |
|
| the whole site as Markdown |
|
| the Markdown sitemap for path discovery |
|
| one page as Markdown |
|
| one page as HTML |
|
page-html is recorded only when the request comes from a recognized AI crawler, so human readers never appear in this table. Adding ?ask=<question> to a .md URL is logged as a reader question rather than a fetch, so it counts toward Top AI queries, not crawler activity.
See AI-ready published sites for what each endpoint returns.
See also
Triage content gaps: turn zero-result queries into new topics
Improve AI search readiness (GEO): make pages easier for AI engines to parse and answer from
Monitor search analytics: keyword search query analytics
AI-ready published sites: llms.txt, per-page Markdown, and the ask endpoint