Services / Amazon listings & A+
A marketplace listing is a search result and a sales page at once, and they want different things.
Most listings are optimised for the algorithm or for the shopper, and lose the other. The discipline is knowing which element serves which: the title and backend terms are for retrieval, the image stack is for conversion, and confusing the two is why keyword-stuffed titles convert badly.
The canon
The principles this rests on, named.
Each with who established it, so the claim can be checked rather than taken on our word.
The image stack carries the sale, not the copy.
Consistent marketplace behaviour data; mobile shoppers swipe before reading
On mobile, bullets are below the fold and often collapsed. The image carousel is the actual sales page and should be built as one.
Every image answers one objection, in the order objections occur.
Direct-response sequencing, applied to a carousel
Hero for recognition, scale for 'how big', in-use for 'is it for me', detail for 'is it well made', comparison for 'why this one', and specification for the last hesitation.
Relevance beats volume in keyword selection.
Marketplace ranking behaviour; conversion feeds back into rank
A high-volume term you convert badly on damages rank. Ranking is partly earned by converting the traffic you already get.
Ambiguity is the enemy of the return rate.
Returns analysis across categories
Most returns are expectation mismatches, not defects. A scale image and an honest specification cost a few conversions and save many more returns.
A+ content is read by the undecided, not the arriving.
Scroll-depth behaviour on product detail pages
The people who reach A+ have already not bought from the images. It should answer the remaining doubt, not repeat the hero claim.
Mobile is the default view, not the adaptation.
Marketplace traffic composition in India
Text baked into images at desktop scale is unreadable on a phone, which is where the majority of the traffic is.
Method
What actually happens, in order.
Competitor one and two star reviews are the objection list, written by customers, for free. That list becomes the image brief.
Category terms, attribute terms, use-case terms and brand-defensive terms, each with a decided place: title, bullets, backend, or nowhere.
Brand, product, key attribute, size or count. Readable. Backend search terms carry the long tail so the title does not have to.
Seven frames, each with one job, written down before anything is shot.
Lead each with the benefit in capitals, follow with the mechanism. Not a paragraph in a bullet's clothing.
Comparison table, use-case module, brand story last. It is a doubt-clearing page, not a second hero.
What goes wrong
The failure modes nobody advertises.
Reads as a low-quality seller, suppresses click-through, and increasingly gets truncated or rewritten by the marketplace anyway.
A carousel that shows the product from every side and answers no question. Angles are not objections.
Infographic overlays set for a desktop preview become illegible in the actual app view.
The single largest driver of size-related returns, and the cheapest thing to fix.
Lifestyle imagery and mission statements where a comparison table should be. It converts nobody who was hesitating on a specification.
What we refuse
A studio is defined as much by this list.
- We do not keyword-stuff a title.
- We do not make a claim the product cannot support, however common it is in the category.
- We do not use competitor brand names in backend terms.
- We do not ship an image stack that has not been checked at mobile size.
Measured, not felt
How anyone can tell whether it worked.
Click-through rate from search results, per keyword.
Session-to-order conversion on the detail page.
Return rate and, specifically, the share of returns tagged as expectation mismatch.
Organic rank on the terms actually chosen, not the vanity head term.