Manage your search
Read your search analytics
Last updated April 11, 2026 · by the AdminDex team
The analytics dashboard shows what your users are actually searching for — top queries, latency, zero-results rate, and a daily volume timeline. It helps you spot content gaps, slow queries, and search behaviour you weren't expecting.
Before you start
- You need a connected instance. See connect your first Meilisearch instance.
- Analytics requires a paid plan. Retention varies: Starter keeps 7 days, Pro keeps 30, Agency keeps 90.
- Important — closed-loop scope: in v1, the analytics page captures only test searches you run from AdminDex's own browse-page preview. Real production traffic isn't captured yet — that's a separate, larger feature on the roadmap. The page is honest about this scope so you don't expect business-intelligence-grade insights.
Steps
- Open the instance from your dashboard.
- Click the Analytics tab at the top.
- Use the Time window filter strip to switch between Last hour, Last 24 hours, Last 7 days, Last 30 days, or All time.
- The four headline cards show Total searches, Unique queries, Avg latency, and No-results rate. The no-results rate turns amber if it's above 20% — that's a signal that users are searching for things your index doesn't cover.
- Below the cards: Searches over time (a daily bar chart), Top queries (a leaderboard with relative-frequency bars), and Recent searches (the last 20 individual queries with their hit counts).
What happens next
To populate the dashboard with data, run a few searches in the browse page first — see browse documents and run search previews. Each search you run there is logged into analytics.
Tips
- If the no-results rate is high, the Top queries panel often shows you exactly which queries are failing — the leaderboard pulls from all searches, not just successful ones.
- Slow average latency usually means your ranking rules or searchable attribute list is too broad. Try narrowing them in the settings editor.
Related
All help articles
Still stuck? Email the AdminDex team →