A store is not one conversion problem. It is four pages doing four different jobs, and each one fails in its own way.
Fixing the wrong one is the usual reason a redesign changes nothing.
A visitor rarely meets one page. They arrive on a category from search, browse a grid, open a product, and decide. A weak homepage sets the scepticism the product page then has to overcome. A weak collection page means the product page never gets the traffic it deserved.
That is why we treat these four templates as one system. Each has its own sequence of jobs, in its own order, and each guide below is the working checklist we build against.
Each opens as a full guide. None of them is a sales page with the detail removed.
Swipe the frameworks
Product pages built to close the sale
Position. Persuade. Prove. Protect. Push.
A product page is not a description. If it does not remove uncertainty, build the case and make buying feel safe, traffic arrives and leaves again.
Collection pages built for search and discovery
Target. Guide. Filter. Sell. Rank.
Collection pages are the bridge between search traffic, browsing and a product click. They have to satisfy a search engine and an impatient shopper at the same time.
Homepages built to establish trust and route visitors
Hook. Explain. Prove. Direct. Build Desire.
A homepage does not need to sell the whole range. It needs to make a visitor feel they have found the right brand, then send them into the right journey.
Landing pages built to convert paid traffic
Match. Sell. Prove. Remove Risk. Close.
Landing pages are about continuity, clarity, proof and closing. Paid traffic sent to a general page pays for the click and wastes the intent.
Pick by symptom rather than by preference.
| What you are seeing | Usually the page | Framework |
|---|---|---|
| Traffic arrives on products and does not convert | Product page: proof and risk are thin | Product page blueprint |
| Organic category traffic bounces | Collection page: structure and filtering | Collection page framework |
| Visitors leave the first screen | Homepage: no positioning, no early proof | Homepage framework |
| Paid campaigns spend without return | Landing page: the advert and page disagree | Landing page framework |
| Every change needs a developer | The theme itself, not any single template | Shopify development |
The structure applies to any ecommerce platform. Shopify is where we implement it, because templates and sections can be built without adding weight to the store.
We build them. A template rebuild is a bounded project with a scope, a price and a handover, like any other piece of work here.
Yes, as monthly support where there is a genuine backlog worth prioritising. It is a separate service and it is never a condition of a build.
No. The smaller the traffic, the more each page has to earn. The order of the jobs does not change with catalogue size.
Usually at the page carrying the most qualified traffic. For most stores that is the product page; for stores living on organic category traffic it is the collection page.
Send the store and the pages you suspect. We will tell you which of the four is actually costing you, and what the fix is worth.
