Translate shopper problems into searchable product attributes
Support symptom and use-case searches by mapping shopper language to defensible product attributes and visible result logic.
Skip this if Stores that intentionally provide no storefront search
Support symptom and use-case queries only through product attributes the business can defend. Map the shopper's language to those attributes, then show how the result was interpreted.
A use-case query describes where, when, or why a product will be used, such as “wedding gift” or “cold weather sleeping bag.” A symptom query starts from a problem rather than a product name. Baymard identifies both as common ecommerce query types and notes that useful support often depends on structured product data, not simple keyword presence.[1]
The rest of this lesson is available once the Atlas is unlocked.