Click-through gets shoppers onto your listing; conversion gets them to buy. This playbook diagnoses the specific reasons shoppers hesitate, then tests improved image stacks and copy against the live competitor set until the listing converts. Where the Amazon main image playbook optimizes the thumbnail that wins the click, this one optimizes the detail page that wins the purchase. The loop is designed to be run autonomously by an AI agent (Claude, ChatGPT, Cursor, or any client with PickFu MCP / CLI / API access) with minimal human intervention.Documentation Index
Fetch the complete documentation index at: https://www.pickfu.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
When to use this playbook
| Use it when | Skip it when |
|---|---|
| Shoppers reach your listing but don’t buy | Your problem is getting clicks, not conversions. Use the main image playbook |
| You can change your image stack, copy, or A+ content | You can’t change the listing |
| You have 2–3 competitor listings to benchmark against | You’re pre-launch — validate the concept first |
The optimization loop
Audit conversion blockers
Show shoppers your live listing and ask what stops them from buying. This surfaces the specific
objections to fix.
Baseline your image stack against competitors
Test your current image stack vs. 2–3 competitor stacks. Save this competitor set — you reuse it
in the final validation.
Generate improvements
Use the audit feedback to rewrite copy and generate improved images
(generate_image via MCP, CLI, or API).
Test variants
Run head-to-head or ranked polls comparing improved copy / images against the original until a
variant wins with a score of 70 or higher.
Sample size and cost. This playbook defaults to small, cheap polls — 50 respondents for
the audit, baseline, and final validation, 15 respondents per iteration. The loop triangulates
across many polls, so a single noisy poll gets corrected by the next. Scale up only when stakes
justify it: bump the final validation to 100–200 before a costly listing overhaul. Open-ended
audits (steps 1, 3) benefit from a few more responses if you want richer themes — 50–100 is a good
range. See sample size guidance.
Run this playbook with an AI agent
Copy prompt for AI
Paste this prompt into Claude, ChatGPT, Cursor, or any AI agent connected to the
PickFu MCP server, CLI,
or REST API. The agent will run the entire loop on your behalf —
creating polls, reading responses, and iterating until a winning variation emerges.
Step-by-step (human operator view)
1. Audit conversion blockers
Show shoppers your live listing and ask what stops them from buying.| Setting | Value |
|---|---|
| Poll type | Open-ended |
| Question | ”Review the listing. What prevents you from purchasing, and what would change your mind?” |
| Audience | General |
| Sample size | 50 |
2. Baseline your image stack against competitors
| Setting | Value |
|---|---|
| Poll type | Ranked choice |
| Question | ”If you were shopping on Amazon for [search term], which product would you buy?” |
| Options | Your image stack + 2–3 competitor stacks (import by ASIN) |
| Audience | General |
| Sample size | 50 |

3. Generate improvements
Address the top blockers from step 1. Use PickFu’sgenerate_image to produce improved listing
images (size reference, benefits callouts, lifestyle context), and rewrite copy to resolve the
objections respondents raised.
4. Test variants
| Setting | Value |
|---|---|
| Poll type | Head-to-head (2 options) or Ranked (3–8 options) |
| Question | ”Which version makes you more likely to buy, and why?” |
| Options | Improved variant(s) + original |
| Audience | General |
| Sample size | 15 |
5. Re-validate against the original competitor set
| Setting | Value |
|---|---|
| Poll type | Ranked choice |
| Question | ”If you were shopping on Amazon for [search term], which product would you buy?” |
| Options | Improved listing + the same 2–3 competitor stacks from step 2 |
| Audience | General |
| Sample size | 50 (bump to 100–200 for a high-stakes overhaul) |
Troubleshooting
The audit feedback is vague ('looks fine', 'good price'). What now?
The audit feedback is vague ('looks fine', 'good price'). What now?
Vague feedback usually means the listing has no glaring blocker — the gains will come from
sharpening, not fixing. Pull the most specific 10–15 comments and look for faint signals
(one person confused about size, another about materials). Those micro-objections compound.
My variant wins head-to-head but doesn't beat competitors in step 5.
My variant wins head-to-head but doesn't beat competitors in step 5.
You improved relative to your old listing but not relative to the category. The remaining gap is
usually price, brand trust, or the hero image. Re-run the audit with the improved listing to find
the next blocker.
Should I test images or copy first?
Should I test images or copy first?
Images. Shoppers scan the image stack before reading bullets, so image-stack problems cap
conversion before copy even gets read. Fix the stack, then optimize copy.
When will Amazon CVR actually move?
When will Amazon CVR actually move?
Listing changes can affect conversion within days, but Amazon’s metrics are noisy at low order
volumes. Give it 1–2 weeks of steady traffic before judging the live impact.
Related
- Amazon CVR help: getting started & FAQs — how to start it in the app + common questions
- Amazon main image playbook — for click-through rather than conversion
- Best practices for survey design
- MCP server reference
- PickFu CLI
