The sale you never saw: measuring lost demand from thin data
The demand you never converted rarely shows up in a dashboard. Here's how to find and size it using zero-result searches, exits, and returns data.
Your analytics tell you what happened after someone found your product. They say almost nothing about the buyer who searched, got nothing usable, and left. That gap — demand that existed but never converted because the product wasn't findable or answerable — is the most expensive line item most retailers never see. It doesn't show up as a bounce or a refund. It shows up as a customer who bought the same thing from a competitor an hour later.
Why this cost is invisible by default
Standard reporting is built to measure what converted, not what almost did. Google Analytics tells you sessions, conversion rate, and revenue per visitor for the traffic that landed on a PDP. It has no native concept of "a shopper typed a query your site couldn't answer" or "an AI assistant summarized your competitor's spec sheet instead of yours because yours was thin." Those events happen upstream of the funnel you're already measuring, in places most teams don't instrument: on-site search logs, impression data in Search Console, and exit behavior on pages that technically "worked."
The result is a systematic undercount. Every dashboard looks calmer than the business actually is, because the demand that never converted never got logged as a loss.
Four proxies that make lost demand visible
You can't measure invisible demand directly, but you can triangulate it from four proxies that already exist in tools most teams have.
| Proxy | What it shows | Where to measure it |
|---|---|---|
| Zero-result / low-result site searches | Buyers who described what they wanted in words your catalog couldn't match | On-site search analytics (Algolia, Klevu, Bloomreach, or your search vendor's query log) |
| Impressions without clicks | Demand that found you in search results but didn't click through | Google Search Console — Performance report, filter by page, sort by impressions with low CTR |
| High-exit PDPs with adequate traffic | Buyers who reached the product and left without adding to cart or asking a question | GA4 — engagement rate and exit rate by page, cross-referenced with content completeness |
| Win/loss and support signals | Deals or purchases lost to a competitor, or repeat questions that indicate the page didn't answer them | CRM win/loss notes, live chat transcripts, support ticket tags, on-site "ask a question" logs |
None of these is proof on its own. Together, they triangulate the size of the demand you're losing before it ever reaches a conversion funnel.
Zero-result and low-result searches
Site search users are disproportionately valuable — they convert at meaningfully higher rates than browsers and spend more per session, because a typed query is a stated intent. That's exactly why a failed search is expensive: it's not a casual visitor drifting off, it's a buyer telling you precisely what they want and getting nothing back. Industry benchmarks put zero-result rates well into double digits for stores that haven't actively tuned search, and shoppers who hit a bad search result are far more likely to abandon the session entirely rather than try again (Algolia).
The fix starts with the query log, not the search box. Pull the top zero-result and low-result queries by volume, and check whether the product actually exists in your catalog. Often it does — the query just doesn't match because the attribute that would have surfaced it (a synonym, a use-case term, a spec value) was never captured in structured data. That's a data completeness problem wearing a search-relevance costume.
Impressions without clicks
Search Console's Performance report is the closest thing you have to a receipt for demand that found you and passed. A page with rising impressions but flat or declining clicks is a page that's ranking for the right query but losing the click — usually because the title, snippet, or the underlying content doesn't answer the query as specifically as a competitor's does. Segment by page type: category pages behave differently from PDPs, and a PDP with high impressions and low CTR against a specific spec query (a size, a material, a compatibility term) is telling you the page doesn't contain that spec in a crawlable, matchable form.
This same gap shows up beyond organic search — in marketplace search, in on-site search, and increasingly in how AI answer engines choose which product to cite. Treat it as one signal among several discovery channels, not the whole story.
High-exit PDPs that "worked"
A PDP that gets traffic and doesn't convert is not neutral — it's actively losing demand that already found the right product. Nearly half of shoppers report abandoning a purchase because they couldn't find sufficient information, and a large share bounce before they even finish scrolling the page (Retail Dive). Cross-reference your highest-traffic, lowest-converting PDPs against a simple completeness check: does the page have full specs, real dimensions, compatibility or fit guidance, and enough imagery to answer the question a buyer would otherwise ask support? Pages that fail that check are your highest-leverage fix, because the traffic is already paid for.
Win/loss and downstream signals
The last proxy is the one sales and support teams already have and rarely share with the content team: deals lost to a named competitor, support tickets asking questions the PDP should have answered, and returns tagged "not as described." Returns tied to inaccurate or missing product information are a documented and sizeable share of total returns, and buyers who receive wrong information are far less likely to purchase from that retailer again (360 Magazine). A support ticket about sizing or compatibility is a zero-result search that happened after checkout risk was already taken — it's the same underlying gap, just discovered later and at higher cost.
Sizing the opportunity
To put a number on it: take your top 50-100 zero-result or low-CTR queries, estimate their monthly search volume, and multiply by your site's average search-to-purchase conversion rate and AOV. Do the same for high-traffic, high-exit PDPs using your category's average conversion rate as the benchmark they're falling short of. Add the fully-loaded cost of returns and support tickets tied to "wrong or missing information" tags. The sum won't be precise, but it will be directionally large enough to justify fixing the underlying data — and specific enough to tell you which SKUs and categories to fix first.
That's the practical case for treating product data as a demand-capture problem, not a back-office chore. Anglera plugs into whatever PIM you already run (or none) and continuously scores, gap-fills, and enriches product data from your own supplier and source documents — not invented values — so the specs, compatibility details, and answers buyers are already searching for actually exist on the page. Most catalogs can be live in weeks, not a multi-year rebuild, which means you can start closing the zero-result and high-exit gaps on the SKUs where they're costing you the most, this quarter.