Why this matters
Docs search queries are user intent in plain text. Zero-result searches tell you what users expected to find and could not.
What you get
- Top zero-result queries
- Pages where searches happen
- Users or accounts affected
- Follow-up impact: activation failure, support tickets, or API inactivity
Walk through it
You
What are people searching for in docs and not finding?
Agent
I’ll rank docs searches with result_count = 0.
Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
query: "SELECT properties.query AS query, properties.path AS path, count() AS searches, count(DISTINCT distinct_id) AS users FROM events WHERE event = 'docs_search' AND toInt(properties.result_count) = 0 AND timestamp > now() - INTERVAL 30 DAY GROUP BY query, path ORDER BY searches DESC LIMIT 50"The output
The agent returns search gaps and suggested docs pages to create or improve.
Setting it up
Emit docs_search from your docs site search component. Include result count and current path.
Variations
- “Only show searches from logged-in accounts.”
- “Find zero-result searches before API inactivity.”
- “Draft the missing docs outline for the top query.”