Disclosure: this post is written by the team behind KDP Quick Scout, and our extension is one of the tools mentioned below. The method works with a spreadsheet alone; product claims were checked against version 0.8.2 of the extension on October 13, 2026.
Open a competitor’s book page, read the BSR, close the tab. You now know one thing: the rank at the moment you looked. Almost every question worth asking about a competitor is a question about time. Was that #8,000 a launch spike or the new baseline? Did last week’s price drop actually move anything? Is the whole niche seasonal? A snapshot cannot answer any of those. A few weeks of history can.
Tracking competitor books is one of the highest-leverage habits in this space, and the barrier isn’t cost. It’s the bookkeeping. This post covers the free method end to end: what to record, how often, and how to read what you collect, with or without a tool.
What tracking actually is
Strip away the interface and tracking is one mechanical thing: a dated snapshot of a book’s public signals, taken repeatedly. For KDP purposes, two signals earn a place in every snapshot:
- BSR, both the overall Books rank and the subcategory ranks. This is the demand signal, and what it can and cannot tell you is a separate question worth reading before you build a habit around it.
- Price, per format. Kindle, paperback, hardcover, and the rest move independently, and the pattern of who discounts when is half the story (what format prices reveal).
Review counts and ratings are visible on the page whenever you look, and they move slowly relative to rank and price. For a weekly tracking habit, they rarely need their own column.
The value is entirely in repetition. One snapshot is an anecdote. Twenty snapshots over a month is a dataset you can make decisions from.
The manual free method: a spreadsheet
Nothing stops you from doing this with a browser tab and a spreadsheet, and the setup takes ten minutes:
- Pick three to five books that compete directly with yours (same niche, comparable length and format, independently published where possible).
- Make a column per book, a row per check-in. Date, BSR, Kindle price, paperback price. That’s the schema.
- Check the pages once a week, same day, and add a row.
This works. Authors have validated niches this way for years, and if you only track a couple of books for a month, it remains a reasonable choice.
It also has three failure modes, and they’re predictable:
- You stop. Not out of laziness; weeks get busy. The spreadsheet’s value compounds, and every missed week breaks the compound. The data doesn’t degrade gracefully; it just accumulates gaps.
- You check at the wrong moments. A weekly Monday glance systematically misses weekend promos and midweek rank spikes. You see the aftermath and never the event.
- You can’t compare in your head. Five books times a few formats times several weeks is past what working memory does. The spreadsheet holds the numbers; the pattern still has to be assembled by eye.
None of that is an argument against tracking. It’s an argument for separating the checking from the recording.
The same method, minus the bookkeeping
KDP Quick Scout is a free Chrome extension that overlays research data on Amazon book pages. Tracking is one of its features, and it turns the manual method into this:
- Open any Amazon book page. The extension’s panel appears on the page itself, and Alt+K toggles it. It works on Amazon.com and 5 other Amazon marketplaces.
- Click “Track this Book.” The first snapshot is recorded immediately. No account is required; the data lives in your browser by default.
- Every later visit to that page records another snapshot, automatically. You were going to check the page anyway; now the check also files itself.
- Open the My Books tab to see everything you track: latest BSR, current price, and a small rank sparkline per book, sortable by rank, price, or date added.
- Click into any book for the full view: a BSR trend chart, a price chart with one line per format, and the complete snapshot history in a table.
Repeat visits within about four hours don’t stack snapshots, so checking the same book five times in an afternoon adds one entry, not five. Amazon gives each format its own rank, so tracking the paperback of a book you already track as Kindle creates a separate entry; the extension warns you before doing that, and you can track it anyway.
There is also an optional daily background refresh (off by default) that can collect a snapshot on days you don’t open the page, for books where you’ve turned on sync. It exists; visiting the page remains the primary way history accumulates.
Reading the charts
Two conventions matter, and both exist to stop you misreading the picture:
- The BSR axis is inverted. The line moving up means the rank number got smaller, that is, the book sold better. Chart-up is good; don’t let your eyes run the usual “higher line, bigger number” reflex.
- Price lines are per format. A paperback drifting up while Kindle holds flat is a common pattern and a different signal from both formats dropping together.
Charts need at least two snapshots to appear. After that, the useful reading isn’t any single point, it’s the shape: a tight band around #12,000 for a month is a different animal from the same average produced by swings between #3,000 and #60,000. (How to interpret those shapes is covered separately; the short version is that stable beats spiky for niche evidence.)
You can also select two or three tracked books and plot their BSR trends on one time-aligned chart. That’s the comparison view, and it answers the question a single book never can: is this niche moving as a whole, or is one book carrying the impression.
What the free plan covers
Tracking itself has no book count limit on the free plan. If your browser storage fills up, the extension warns you well before that becomes a problem, and you can remove books you no longer need to free up space. The limits that do exist are about history and sync:
- History: the last 30 days of price and BSR snapshots per book. Older snapshots are trimmed automatically as new ones arrive; the book stays tracked with its recent window intact. A future paid tier will keep full history; it isn’t for sale yet.
- Sync: up to 10 books per account. Sync is optional, per book, and off by default on free. It’s what carries tracked books across devices, and what the daily background refresh requires. The 10-book number applies here, not to tracking itself.
- Snapshots per book: up to 90 retained. Inside a 30-day window that only binds if you open the same page many times a day.
One consequence worth internalizing: 30 days is enough to answer the questions this post opened with (spike or baseline, promo effect, monthly rhythm), and not enough for seasonality across a year. For seasonal niches, keep a sparse spreadsheet alongside: one row per month per book, BSR and price. Two minutes a month, and it covers what the rolling window can’t.
A practical weekly routine
If you adopt nothing else from this post, adopt the routine. Total time: under ten minutes a week once the books are tracked.
- Set up (once). Track three to five direct competitors. If you already use a spreadsheet, keep it for the monthly seasonality row described above; drop the weekly transcription.
- Browse as usual. Open competitor pages when curiosity strikes; each visit files a snapshot. If you’ve enabled sync and the daily refresh on a book, it may also add snapshots on days you skip, though visiting the page remains the reliable path.
- Once a week, skim My Books. Sparklines answer “did anything move” in seconds. Only open the detail view for books that moved.
- Every few weeks, run a comparison. Select the two or three books that matter to your next pricing or release decision and read the aligned trends together.
- Close the loop into decisions. A rank band that held while you held price means your price point has support. A competitor dropped to $0.99, the rank snapped up and decayed back: that looks like a promo, not a new baseline (pricing implications here). The whole niche’s ranks tightened over a month: demand is consolidating, and you should check whether yours is among the books actually selling.
The practical takeaway
- A snapshot answers “what is.” Only history answers “what’s changing,” and almost every useful competitor question is the second kind.
- The free manual method (spreadsheet, weekly rows) is legitimate; it fails on consistency and comparison, not on data quality. Automate the recording, keep the judgment.
- Track BSR and per-format price. Review counts and sales estimates rarely need columns: the first is visible on demand, the second is computed, not observed.
- KDP Quick Scout’s free plan tracks books with no count limit locally (browser storage is the only ceiling), keeps 30 days of history per book, and records a snapshot on every visit to the page. No account needed to start; sync across devices is optional and capped at 10 books.
- Read shapes, not points. A stable band is evidence; a spike is an event; knowing which is which is the whole game.
You don’t need perfect data to track a niche well. You need a habit that records the signals while you go about your other work, and a weekly glance to read what they add up to.
(The number you’re looking at on a competitor page means more when it arrives with a direction. KDP Quick Scout’s tracking is free, works on the page you’re already on, and setup takes about a minute per book.)
Frequently asked questions
Do I need an account to track books?
No. Tracking is local to your browser by default. An account (Google or email) is needed only for two things: syncing tracked books across devices, and running AI niche analyses.
How many books can I track on the free plan?
There is no count limit on tracking; browser storage is the only ceiling, and the extension warns you well before it’s full. The 10-book limit applies to optional cloud sync, which is what carries books across devices.
How much history does the free plan keep?
The last 30 days of price and BSR snapshots per book. Older snapshots are trimmed automatically; the book itself stays tracked with its recent window intact. A future paid tier will keep full history; it isn’t for sale yet.
How often are snapshots recorded?
Once when you click Track, then once per later visit to that page, with repeat visits within about four hours collapsing into one snapshot. An optional daily background refresh (off by default) can add snapshots on days you don’t visit, for books where sync is enabled.
Does tracking record sales estimates?
No. The monthly sales estimate on the book tab is computed from the book’s current rank each time you view it (why estimates are reconstructions). Tracking history stores rank and price, the observed signals, and charts those.
What’s the difference between tracking and AI niche analysis?
Tracking is passive and automatic: no account, no quota, it accumulates while you browse. AI niche analysis is an on-demand report on a niche, requires signing in, and has free limits (currently two per hour, five per day).