Menu

Twenty-four searches, twelve answers: what our own catalog search measures
πŸ“°

Twenty-four searches, twelve answers: what our own catalog search measures

DEV Community: apiΒ·minia2aΒ·about 10 hours ago
#z3ZwSohM
#devtoapi#devto#dev#description#stock
Reading 0:00
15s threshold

A marketplace usually answers "can a buyer find what they need?" with a supply

number: we have N endpoints . That number says nothing about the query an

agent actually types. We took 24 real search terms from a public 30-day demand

preview, ran each one verbatim against our own catalog, and counted what came back.

Twelve answered. Every one of the five zeros was the same missing capability.

The measurement is boring and reproducible, which is the point: one GET

per term, a hit count, and a reading of why. No sampling, no survey.

1. How our search actually matches

Our catalog search is a literal token AND. A query is split into tokens, and a row

matches only if every token appears in its description (or name). There

is no stemming, no synonym table, and no relevance ranking to hide behind.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.