The Search Queries report tells you exactly what readers expect to find in your docs. It's often more useful than page-view analytics — page views tell you what's there, search tells you what's missing.
Pro plan or higherScreenshot needed
screenshot of the Search Queries view: tabbed switcher for "All queries" / "No results", a table with query, count, click-through rate, last seen
Two tabs#
All queries#
Every search executed in the date range, sorted by frequency. Columns:
- Query — what the reader typed
- Count — how many times searched
- CTR (click-through rate) — % of searches where the reader clicked a result
- Last seen — most recent search
A query with high count and low CTR means readers are searching for something but not finding the right page. Either the query is genuinely missing content, or you have a page about it but the title/description doesn't match the intent.
No results#
Queries that returned zero results. These are the highest-signal source of "what should I write next."
Common patterns:
- Misspellings of existing concepts — your search index might be too strict. Add common misspellings to the page's title or description.
- Related concepts you don't cover — readers expect coverage and you don't have it. Write the page.
- Outdated terminology — readers searching for an old name. Add a redirect or mention the old term in the new page.
Date ranges and filters#
Same controls as Top Pages. Default is 30 days; you can filter by section (only show searches that happened on pages under a specific parent — useful for diagnosing missing API docs vs missing concept docs).
Privacy#
Search queries are stored verbatim. They could contain sensitive info if a reader pastes a token or PII into the search box (rare but possible).
If you're concerned, you can disable query logging in Project Settings → Privacy → Disable search logging. The search itself still works; only the analytics trail goes away.
How to act on this#
A weekly 15-minute ritual that compounds:
Open Search Queries → No results, last 7 days
Sort by count descending.
Look at the top 10
For each one, ask:
- Is there a page that should match this query?
- If yes, why didn't the search find it? (Probably a title/description mismatch — fix it.)
- If no, should I write a new page? Add it to your queue.
Spot-check the all-queries tab
Look for queries with high count but low CTR. Read the page that should match and ask whether the title and first paragraph make it clear.
Ship the fixes
Most fixes are 5-minute edits. Batch them.
This single ritual is the highest-leverage docs work I know.
Export#
Click Export for a CSV of the queries with all columns. Useful for keyword research, prioritization meetings, or piping into your team's planning tool.