Ecommerce Search Analytics: What Should You Measure?
Which ecommerce search metrics matter: usage, zero results, refinements, exits, result clicks, search conversion and query-level analysis, with a review routine.
Quick answer
Measure ecommerce search at two levels. At store level, track search usage, zero-result rate, result click-through, refinement rate, search exits, and add-to-cart and conversion after search, segmented by device. At query level, review the top queries by volume and revenue, queries with zero results, low clicks or high exits, and what shoppers type next when they refine. Review weekly, fix synonyms, data and ranking for the worst queries, and use search terms as demand data for merchandising.
Why Search Analytics Deserves Its Own Practice
On-site search is one of the few places shoppers tell you exactly what they want, in their own words. Search logs show demand, vocabulary and gaps that navigation data can't reveal. When search works, shoppers find products quickly; when it fails, they leave or assume you don't stock what they wanted.
Most stores track search conversion and stop there. That number is influenced by intent as much as by search quality, so it rarely tells you what to fix. Useful search analytics looks at what happens after each query: did results appear, did shoppers click, did they refine, did they leave. For search strategy and setup, see ecommerce site search; for interface design, see ecommerce search UX.
Store-Level Search Metrics
| Metric | Definition | What it tells you |
|---|---|---|
| Search usage rate | Sessions with a search ÷ all sessions | How much shoppers rely on search |
| Zero-result rate | Searches returning no results ÷ all searches | Catalog, synonym and data gaps |
| Result click-through rate | Searches followed by a result click ÷ searches with results | Whether results look relevant |
| Refinement rate | Searches followed by another search ÷ searches | Mismatched intent or vocabulary |
| Search exit rate | Searches followed by leaving the site ÷ searches | Serious failures |
| Filter use after search | Searches with a filter applied ÷ searches with results | Result sets too broad, or filters helpful |
| Add to cart after search | Searches followed by add to cart ÷ searches | Search usefulness closer to purchase |
| Search conversion | Search sessions with purchase ÷ search sessions | Outcome, influenced by intent |
Query-Level Analysis
Store-level metrics tell you whether search is improving; query-level analysis tells you what to fix. Build a table of queries with volume, zero-result flag, click-through, refinement rate, exits, add-to-cart and revenue. Normalize queries first (lowercase, trimmed, obvious typos grouped) so variations are counted together.
Sort the table in several ways. By volume shows the head queries that deserve manual checks. By revenue shows the queries that matter commercially. By exits or refinement rate among queries with meaningful volume shows the biggest failures. Zero-result queries sorted by volume give you a direct to-do list; see zero-result searches.
| View | Sort by | Action |
|---|---|---|
| Head queries | Volume | Check results manually each week |
| Revenue queries | Revenue after search | Protect ranking and availability |
| Failing queries | Exit or refinement rate (min volume) | Fix synonyms, ranking or data |
| Zero-result queries | Volume | Add synonyms, fix data, consider range |
| Rising queries | Change vs previous period | Spot trends and new demand |
Refinement Paths
When a shopper searches, then searches again, the second query often shows what the first should have returned. "Trainers" followed by "sneakers" suggests a missing synonym. "Black dress" followed by "black midi dress" might mean results were too broad, or that length should be a filter. Pairing each query with the next query in the same session reveals these patterns quickly.
Also look at filters applied after search. If most shoppers searching "running shoes" immediately filter by gender and size, consider showing those filters first for that query, or using autocomplete to offer the refined queries directly. See search autocomplete.
Segmenting Search Data
Segment search metrics by device, new vs returning visitors, traffic source and market. Mobile shoppers may search more because navigation is harder on small screens, or less if the search box is hidden behind an icon. Returning customers often search for specific products they bought before. International visitors may use different words or languages. Each pattern suggests different fixes.
Setting Up Tracking
Search analytics needs events for the search itself, the results shown and what happens next. In GA4, enhanced measurement records a view_search_results event when the search term appears in a URL query parameter. On Shopify, the search_submitted customer event fires when a search is performed. Many search apps and services record queries, clicks and zero results in their own dashboards.
Add what the defaults miss: the number of results returned, result clicks with position, filters used within search results and autocomplete selections. Without results count, zero-result searches can't be identified; without click position, ranking can't be judged. See ecommerce event tracking.
- Search event with normalized query and results count
- Result click event with product ID and position
- Autocomplete shown and selected events
- Filters and sort changes on search results pages
- Add to cart attributed to search where it followed a search
- Device, market and language on each event
Not sure what your search data is telling you?
ZSpace Labs audits search tracking and query data to find the fixes that matter most for your store.
Search Conversion: Use With Care
Search conversion rate is commonly reported, and searchers often convert at higher rates than non-searchers. That doesn't prove search causes the difference: shoppers who search often have stronger intent. Use search conversion to track trends in your own store and to compare queries, not to claim search's contribution to revenue.
A better indicator of search quality is what happens immediately after a query: clicks, refinements and exits. These are closer to the search experience itself.
Search Data as Demand Data
Search logs are a continuous survey of what shoppers want. Share them beyond the search team. Merchandisers can see demand for products and attributes you don't carry. Content teams can see questions ("how to clean suede") that deserve guides. Product teams can see the names customers use, which should appear in titles and descriptions. Seasonal and trend shifts often appear in search before they appear in sales.
A Weekly Search Review
| Step | Time | Output |
|---|---|---|
| Top 20 queries: check results manually | 15 min | Ranking or pinning fixes |
| Top zero-result queries | 10 min | Synonyms, redirects, data fixes |
| Highest exit and refinement queries | 10 min | Ranking and synonym changes |
| Rising queries | 5 min | Merchandising and content notes |
| Log changes made | 5 min | Change log to judge impact |
Judging the Impact of Search Changes
Measure changes at the level they're made. A new synonym should be judged on the affected queries' zero-result rate, clicks and exits before and after. A ranking change should be judged on click position and add to cart for the affected queries. Larger changes (a new search engine or relevance model) can be A/B tested where the search platform supports it. Keep a change log so improvements and regressions can be traced. See search ranking.
Worked Example
An illustrative scenario, not a client case: a homeware store's search conversion looks healthy, but query-level analysis shows "duvet" with high exits and refinements to "quilt" and "comforter". The catalog uses "quilt" in titles. The team adds synonyms in both directions, adds tog rating as a filter because many searches were refined with tog values, and checks the affected queries the following week.
Building a Search Scorecard
A scorecard keeps search health visible without drowning teams in metrics. Choose a handful of store-level indicators, show their trend over recent weeks, and list the queries behind any movement. The scorecard should lead to actions in the weekly review, not replace it.
| Indicator | Direction you want | If it moves the wrong way |
|---|---|---|
| Zero-result rate | Down | Check indexing, new products, top zero-result queries |
| Result click-through rate | Up | Review ranking for head queries |
| Refinement rate | Down (for head queries) | Look at refinement pairs for synonyms and filters |
| Search exit rate | Down | Inspect the queries with most exits |
| Add to cart after search | Up | Check availability and product suggestions |
| Autocomplete selection rate | Up | Review suggestion lists and ranking |
Qualitative Checks Alongside the Numbers
Numbers show where search fails; watching people search shows why. Short usability sessions in which participants look for specific products, session recordings filtered to search pages, and support tickets that mention "couldn't find" all add context. A query with a high exit rate might turn out to be fine in results but let down by slow loading on mobile, or by a result grid that hides prices. See ecommerce conversion research.
Privacy in Search Logs
Search logs can contain personal information: shoppers sometimes type names, email addresses, order numbers or health-related terms into search boxes. Keep search analytics aggregated where possible, avoid sending raw queries to tools that don't need them, filter obvious personal data patterns, and set retention periods for raw logs. See ecommerce privacy and customer data.
Common Mistakes
- Reporting only search conversion rate
- Not recording the results count, so zero results are invisible
- No normalization of queries before analysis
- Ignoring refinement and exit paths
- Reviewing search data only during redesigns
- Keeping search insights within one team
Ready to measure search properly?
Talk to ZSpace Labs about search and conversion audits, search tracking and implementation and search UX design.
Conclusion
Search analytics works when it looks past search conversion to what happens after each query. Track results counts, clicks, refinements and exits, analyse queries, review weekly and share search demand across teams. Related: Shopify search optimization and search vs navigation.
Common questions.
The measurement of how shoppers use on-site search: what they search for, whether results appear, whether they click, refine, leave or buy, and how this varies by query, device and segment.
Search usage rate, zero-result rate, result click-through rate, refinement rate, search exit rate, add-to-cart and conversion after search, and query-level versions of each for top and problem queries.
Searchers frequently arrive with clearer intent. That makes blended search conversion a poor measure of search quality; compare queries and segments rather than searchers against non-searchers.
GA4's enhanced measurement can record a view_search_results event when the search term appears in a URL query parameter. Stores often add custom events for result clicks, filters used in search and zero-result searches.
Shopify's customer events include search_submitted, which pixels and analytics apps can subscribe to. Search apps usually provide their own analytics on queries, clicks and zero results.
There's no universal benchmark. Track your own rate over time, and focus on the volume and value of the specific queries returning nothing.
Shoppers are rewriting queries, often because results didn't match intent. Look at which queries are refined and what they're changed to; the change often tells you the synonym or ranking fix needed.
Top and zero-result queries weekly, broader metrics monthly, and specific queries after catalog changes, launches or seasonal shifts.
Yes. Mobile search behaviour and interfaces differ, and problems like hidden search boxes or poor autocomplete often show up only on mobile.
Yes. Search terms reveal demand in shoppers' own words, including products you don't stock, missing attributes and names customers use for your products.