Guides
Analytics
What shoppers search, what finds nothing, where they click, what search sells, and who searched. In the dashboard, a Monday email, the API, and for AI agents.
The dashboard's Analytics page covers every index in a workspace, or one of them. It has three tabs: Searches, Traffic, and Events. Choose the last 24 hours, 7, 30 or 90 days, one index or all of them, and browser or server traffic, or both. Clicking a country narrows the page to browser searches from it. Each number is compared with the period before.
Search analytics are kept for three months. Products and revenue from search are counted from events, which are kept for 13 months.
Searches
The Searches tab starts with searches, the share that found nothing, the median response time, and how many different queries were searched. Below them:
- Top queries, with the share of each that was clicked, the place usually clicked, and the share that found nothing.
- Searches with no results and Searches without clicks: queries that found nothing, and queries that found results nobody clicked.
- Query suggestions picked: whether shoppers typed their search or picked a popular or a recent one. See query suggestions.
- Filters used and Sorts chosen, each as a share of searches.
- Countries, Top cities, Devices, Browser languages and Sites, with a map of where browser searches come from. A browser language your index doesn't handle yet suggests turning it on in languages.
- Recent searches: the last 24 hours, as they happen.
Searches that found nothing
Each query that found nothing opens to show what it was searched with: the filter fields, the values chosen, and the sorts. Try opens the index's playground with the same query, filters and sort, so you can see what's missing and fix it with a synonym, a rule, or related results. Filter values are recorded for browser searches.
Why, and fixes
With one index chosen, each query that found nothing without filters at least 3 times in the last 7 or 30 days, more often than it found something, says why, and how to fix it when settings can. Searches that found nothing only because of their filters, such as an empty category, are for their filter details above.
| Why | What you see | The fix |
|---|---|---|
| A typo | The word it's a typo for, and how many results the query finds with it | Add synonym: a one-way synonym from the typo to that word, so only searches for the typo change. |
| Another word | The word your records use, and how many results the query finds with it | Add synonym, from the query to that word. |
| Not sold here | That you don't seem to sell it | None. It's demand, worth knowing about. |
| Not a real search | Tests and keyboard mashing, hidden until you show them | None. |
| No fix found | Nothing sure enough | Look into it yourself, with Try. |
An AI model chooses among words your index already has: did you mean's correction, its category and brand values, and searches that found results. It's shown what each choice finds, a fix is offered only when it's very likely right, and every fix is checked by searching the query with it added. Nothing changes until you add it. Add all adds every fix at once. Fixes are ordinary settings, which the settings page lists under one-way synonyms, with the date they were added.
Each query is checked once, and again after a week or when the index's records change by a tenth. The first check of an index can take a minute; the table fills in as answers arrive.
Where clicks land
Once your pages send clicks, Where clicks land shows which places in the results get them: place 1, places 2 and 3, and further down, or page 2 and later for searches with more pages. Clicked further down lists searches whose shoppers usually click below the top three, with the result they pick most, a sign it should rank higher.
Revenue from search
With visitor IDs on, search clicks, and purchases sent as events with prices, one index's analytics show what search sold: the value of orders with a product the shopper clicked in search results in the 24 hours before, beside all orders, per query and per product. See revenue from search.
Traffic
The Traffic tab shows every search request: those counted toward your plan, those answered from the cache, and those from verified crawlers, which are free (see limits). Who searched splits them into visitors, verified crawlers, other crawlers, scripts and automation, and your servers.
Refused, and why lists requests that were turned away, by reason. Each opens to show the sites they came from and what the client was told. Owners can add a site that should be allowed to the index's allowed origins from there, with Allow. Limits and bot rules are in security.
Crawlers
Crawlers' searches are left out of search analytics, so top queries and searches that found nothing are the shoppers' own. They're counted on the Traffic tab instead.
Events
The Events tab shows product views, clicks, add-to-carts and orders, a table of each product's numbers, products that are viewed often but rarely bought, and recent events. See events for sending them, and products for what the table counts.
Weekly report
Every Monday, each member of a workspace gets an email about the week before: searches, searches that found nothing, the median response time, top searches, revenue from search, clicks, the most viewed products, who searched, and plan usage. A workspace with no searches that week or the week before gets none.
Turn it off under Settings, Email, or with the unsubscribe link in each email. The setting can also send you last week's report again.
From the API and agents
The analytics API gives the same reports to your own dashboards, with a key that has the analytics scope. AI agents read them with the MCP server's get_search_analytics, get_event_analytics, get_product_analytics and get_search_revenue, and why searches found nothing with get_no_result_fixes, whose fixes owners' agents add with apply_no_result_fixes.