Zero-result searches: the dashboard most sites don't have
A customer who searches and finds nothing is telling you, in their own words, what they wanted to buy. Most sites simply have no way to know it.
What most search engines never tell you
An online store typically measures its traffic, page views, overall conversion rate. Far more rarely: what visitors type into the search bar and never find. Yet it's one of the most direct signals there is — a customer typing a search tells you exactly, in their own words, what they wanted to buy.
Why this figure is rarely tracked
Most native platform engines (Shopify, PrestaShop, WooCommerce) don't easily expose a history of zero-result searches — the information exists somewhere in the logs, but nothing is built to make it usable without digging through them by hand. The result: the data exists, but no one ever looks at it, and catalog decisions (what to list, what to reword) get made without it.
What changes when you have the list, not an estimate
The Heurix console logs every search and automatically flags the ones that returned no results — with a count of how many times each query was typed. Concretely: if "waterproof women's jacket" comes up twelve times with no result even though you sell water-repellent jackets, it's either a vocabulary problem (add a synonym) or a genuine catalog gap (a product to source). Both cases are actionable — but only if you know they exist.
A zero-result search isn't a technical glitch to fix once. It's a continuous stream of information about what your customers want and what your catalog doesn't cover yet.
A concrete example
On a hardware catalog, a recurring zero-result query might be "torx screw m8" while the catalog only lists hex-head screws. Without search history, that signal exists nowhere. With it, it's a row in a table, sorted by frequency, ready to hand to the purchasing or catalog team.
How to read it usefully
Two categories to treat differently: queries that fail because of vocabulary (the product exists, the word to find it is different — fixable in minutes with a synonym) and ones that fail because the product genuinely isn't in the catalog (a business decision, not a technical one). Sorting the two takes a few minutes a week once it's a habit, and it's the dashboard itself that surfaces them, with no manual log extraction.