Map the search task to the right page type
Send the named-item search to the exact product, the product-range search to a collection and the compatibility question to a fit guide. These assignments are planning hypotheses until relevant results and customer evidence are inspected. One destination should earn its role by completing the underlying task.
Worked example — illustrative data.
| Search | Candidate destination | Reason |
|---|---|---|
| Arc lamp brass | Specific Arc product page | An identified item and finish |
| Clamp desk lamps | Clamp collection | A set of options to compare |
| How thick can a desk be for a clamp lamp? | Clamp-fit guide | A compatibility question before choosing |
Start with a small product family and write the shopper’s next action beside each search. Inspect relevant live results when available and note if the result mix contradicts the assumed task. Group close variations only when one page can answer them naturally. Record the selected URL, primary task, supporting pages and the evidence still needed. Avoid assigning every query to the homepage simply because it is the strongest existing page.
A product-name search may be a support request
A query can support several tasks. Someone searching for a lamp name may need a manual rather than a purchase page. If existing demand shows that split, add a clear support route instead of forcing all visitors toward checkout.
Use this three-row map as a planning hypothesis. Revise it after actual result inspection and site evidence; do not label it a measured keyword opportunity list.
Continue with Guides for stores, software teams and local businesses, eCommerce SEO services and Design category pages that help shoppers choose.