Ecommerce search intent: product page, collection or guide?
Search intent is the task someone wants to complete when they search. A product page helps them inspect or buy a specific item; a collection helps them choose among items; a guide explains a question that needs more context. Match the task before deciding to publish another page.

In this article
Overview
Search intent is the task someone wants to complete when they search. A product page helps them inspect or buy a specific item; a collection helps them choose among items; a guide explains a question that needs more context. Match the task before deciding to publish another page.
Name the decision before the keyword
A keyword is useful because it expresses a need. Ask whether the shopper wants a known item, a set of options or an explanation. That first distinction keeps a content plan connected to the store rather than treating every phrase as a blog assignment.
Search results can mix several types of pages and change over time. Check the US results for your query, record the date and distinguish ads from organic listings. The examples below show how to make that judgment; they are not findings from a live study of those exact searches.
A collection page is the category page in many ecommerce stores, including Shopify stores. It should help shoppers compare a meaningful set of products. With only two closely related items, a comparison on an existing page may be more useful than several thin collections for slightly different phrases.
Follow the customer's task
A known item
Start by considering the exact product page.
A set of options
Consider a collection or useful comparison.
A question to resolve
Consider an explanation with a relevant next step.
Aleyda Solís: product pages can carry more of the answer
The official SearchPilot recap of Aleyda Solís’ discussion with Will Critchlow emphasizes useful product information and consistency across visible content, structured data and feeds. It provides an expert perspective on ecommerce discovery, not a controlled finding that every question should become a product page.
Use the shopper’s decision to choose the format. An exact-item question may belong beside the variant selector or product details. A choice among several suitable products may need a collection or comparison. A broader explanation may deserve a guide with a clear route back to the relevant assortment. The amount of text alone does not determine the page type; the interface and next action matter too.
This distinction prevents a common planning error: commissioning a blog post for every phrase that contains a question word. A customer asking whether a particular bundle includes an applicator needs an authoritative answer about that bundle, not a generic article about applicators. Conversely, a category-level comparison should not force the reader to open every product page to reconstruct the differences.
Map three related pages before expanding the keyword list
Imagine a brand selling three tinted lip products. This is an original planning example. The exact shade and size belong on each product page. A customer choosing between finishes needs a comparison that uses the same criteria for all three. A customer learning how to select a finish may benefit from a guide, provided it answers a distinct question rather than repeats the comparison with more introductory prose.
Before creating the guide, inspect relevant US search results and existing coverage. Note which formats appear, what they help customers do and where your planned page would contribute something missing. This observation is intent evidence, not proof of a specific search volume. If the same page already satisfies the primary question, improve that destination instead of creating a near-duplicate.
Plan the links before writing. The guide should lead to the comparison or product when the reader is ready to choose. The comparison should link directly to each option. Add the guide to a relevant collection or resource hub so people can find it while browsing the site.
| Customer question | Best starting destination | Natural next link |
|---|---|---|
| Does this exact shade contain shimmer? | The current product and selected variant | Another variant only if the shopper is comparing. |
| Which of these finishes suits my preference? | A fair comparison or useful collection | The exact product selected. |
| How should I choose a finish? | A distinct explanatory guide if needed | The comparison and relevant assortment. |
Give each question a destination and a next step
Define
State the decision in customer language.
Assign
Use the existing suitable page where possible.
Connect
Link the explanation to the next real choice.
A completed example for a small catalog
Imagine a brand selling a cleanser and two moisturizers. The best destination depends on what the visitor needs to decide. A small catalog may not justify a separate collection for every ingredient or use case.
| Question or query | Customer task | Page hypothesis | Work before publishing |
|---|---|---|---|
| Brand name + cleanser + size | Find a specific item | Existing cleanser product page | Verify exact identity, size and purchase details. |
| Lightweight moisturizers from the brand | Choose among suitable options | Existing collection if it has meaningful choices | Explain the difference between products and link to each. |
| Which of the brand's two moisturizers should I choose? | Compare products | Comparison on a collection or product page | Use supported differences; add a standalone guide only if substantial detail is needed. |
| How does a cleanser fit into a routine? | Understand use | Product-page answer or a substantive guide | Check relevance, approved usage and whether an existing page already answers it. |
Read the results as evidence
For each query, record the visible page types and the decisions they help people make. If the useful results are mostly collections, a short general article may be a poor response. If the query needs instruction, a bare product listing may leave the question unanswered.
Do not copy the format without examining the substance. A competitor's page is not proof that the same topic fits your brand. Include the actual product connection and the evidence your team can contribute in the brief.
Improve, create or decline
Improve an existing destination when it already owns the customer question and simply needs a clearer answer. Create a new page when the task is distinct and there is enough useful material to support it. Decline a topic when it attracts an audience or decision the brand cannot serve.
Record the decision in the content plan. This prevents several team members from commissioning competing pages for the same intent and makes internal linking more deliberate.
A page earns its place
Existing answer?
Use and improve the current destination where appropriate.
Distinct missing task?
Create only when a useful contribution is available.
Relevant product?
Connect the answer to the purchase decision.
No useful fit?
Leave the topic out of the active plan.
Make the next step easy to understand
A collection should help shoppers reach products. A guide should link to the product or collection that follows naturally from its explanation. Use descriptive link text so readers understand the destination, and give new pages an inbound path from a relevant hub.
Review whether the selected page attracts the intended questions and whether visitors continue to useful shopping tasks. Dahna can connect this page map to website and SEO work, avoiding a separate publishing plan that does not fit the store.
For the small skincare catalog, a guide about choosing between the two moisturizers could link to each product using its actual name. The moisturizer collection can link to that guide with “compare our two moisturizers.” Each product can link back to the relevant collection. Those links have different jobs: choose a category, resolve a comparison, or inspect an item. Repeating the same keyword in every anchor would make the navigation less clear.
- Customer task stated in one sentence
- Current US result types recorded with a date
- Existing destination checked for overlap
- New contribution identified if a page is proposed
- Relevant incoming and outgoing links chosen
Map questions to pages
Prepare a question-to-page map with search evidence, current pages, proposed changes, internal links and a clear reason for each new page.
Use the downloadable planning sheet linked below to adapt the examples to your brand. Add the current product information, the person responsible for each task and the check that will show the work is complete. Keep unanswered questions visible for the project discussion.
About the sources
The adidas example comes from SearchPilot’s interview recap with Matthew Morrisey and Will Critchlow, published in November 2025 and updated in February 2026. It describes a flat conversion test and a positive SEO result, without a numerical uplift or raw experiment data.
Aleyda Solís’ advice is taken from SearchPilot’s official July 2025 webinar recap with Will Critchlow. The complete video transcript was not reviewed. This is practitioner guidance, rather than a controlled study of gains in AI visibility.
Sources & further reading
- SEO vs. GEO: Mastering E-Commerce Search in an AI-First WorldSearchPilot / Aleyda Solis and Will Critchlow
- Ecommerce SEO Tutorial to Get More Free Search TrafficAhrefs / Sam Oh
- Help Google understand your ecommerce website structureGoogle Search Central
- Inside adidas: an insight-first SEO programSearchPilot / Will Critchlow / Matthew Morrisey
- Share your product data with GoogleGoogle Search Central
- Introduction to Product structured dataGoogle Search Central
Build a useful page plan
Dahna can map your customer questions to product pages, collections and guides, then help improve the pages that need work. You’ll have a clear reason for each proposed page and a plan for how it connects to the store.
Why consider Dahna for this work?
Dahna brings bilingual Korean and English strategy together with creator, content, and measurement work for brands growing in the US. You can review the people behind the recommendations and the kind of work we propose before starting a conversation.
Founder experience includes prior and contracted roles. Sample deliverables illustrate our approach; they are not client results or a performance promise.
We’ll agree on deliverables, responsibilities and approvals before work begins.



