BeCuriouzLearn something new every day
Mapping intent to SKUs: matching demand to what you actually sell
💡 Intent-to-SKU mapping matches each shopper intent to the product that best satisfies it, exposing coverage gaps, content gaps, and mismatches — turning 'improve SEO' into a prioritized intents × SKUs worklist.
Here's the core operational move of retail search: intent-to-SKU mapping. On one side is a universe of shopper intents (all the ways people search for what you offer). On the other is your catalog of SKUs. The work is drawing the right lines between them — for each meaningful intent, which of your products best satisfies it, and is that product's content built to win that search?
Done well, this exposes three kinds of gaps:
- Coverage gaps — a real, high-volume intent that no SKU of yours targets. Maybe a product-line opportunity, or a SKU you should be promoting but aren't. - Content gaps — you have the right SKU, but its title/attributes don't speak the intent's language, so it doesn't rank. This is the most common and most fixable. - Cannibalization / mismatch — several of your SKUs fight over one intent, or a SKU is mapped to an intent it satisfies poorly (hurting conversion and rank).
Intent: "sweat-resistant wireless earbuds for running"
→ best SKU: SoundSport Pro (has: wireless ✔, IPX4 ✔, wingtip ✔)
→ gap: title omits "running" & "sweat-resistant" → not ranking
→ action: rewrite title/bullets, fill attributesThis mapping is what turns vague "improve our SEO" into a concrete, prioritized worklist: a matrix of intents × SKUs, each cell flagged covered / content-gap / missing. It's also the connective tissue to everything else — the fixes it generates are content fixes (Series 2) powered by attribute data (Series 3).