The details · Amazon
Test one Amazon change at a time, and keep a dated log.
What Amazon does tell you is enough to start.
- From
- Case study · CS-002 · September 28, 2026
The test loop I'm building
- Pick one thing: Keyword, category, cover, description or price.
- Write it down: Date, change, format, marketplace, sales before.
- Let it land: 72 h for most changes, 24 h for price, up to a week for rank after a category change.
- Judge by sales: KDP orders and pages read, not rank. Each format on its own.
- Change the next one: Note anything else that happened that week.
Sources (1)
Source: Waiting times from Amazon's Timelines page CS3-127
What I found
Amazon tells you how long changes take to show up (up to 72 hours for keywords, categories and cover, a week for rank after a category change), and your KDP reports show orders and pages read. My loop uses just that: pick one thing (keyword, category, cover, description or price), write down the date and where sales stood, wait for it to land, judge by sales reports, then change the next thing.
So do this
Change one thing at a time and keep a dated log of what you changed and your sales before and after.
Keep in mind
I'm still building this. No results yet.
Source: The test model I'm buildingCS3-127
Read the full case studyI read eight Amazon algorithm guides. Here are two top factors, and the short list Amazon actually publishesWhat Amazon tells authors in its own words, what "we modeled it" really means, and the test model I'm building instead.Case study · CS-002 · 8 min read · 9 posts come from it