Publish-Ready Research Tool
Submit your book details and get a single publish-ready KDP report — 7 backend keyword slots with observed volume and estimated competition, 25–40 ad keyword targets with suggested bid bands, BISAC + browse categories, three description variants, and positioning notes. Every datapoint carries a confidence label so you know what's measured and what's estimated.
Questions authors ask before running it
What does the Publish-Ready Research tool produce?
A single report containing 7 KDP backend keyword slots with observed search volume and estimated competition, 25–40 Amazon Ads keyword targets with suggested bid ranges, recommended BISAC + KDP browse categories, three Amazon book description variants in different tones, and 5–10 positioning notes. Every datapoint carries a confidence label so you know what's measured versus estimated.
Is the tool really free?
Yes. It's limited to 3 reports per hour per IP and 5 per day per email address to keep DataForSEO costs sustainable, but there is no payment required. Authors get the inline result + a PDF download + an emailed PDF copy.
Where does the keyword volume data come from?
Search volume comes from DataForSEO's Amazon volume endpoint. We do not call DataForSEO's `competition` field competition — that field is frequently null and conflates ad-bid pressure with reader competition. Instead, competition is a separate conservative estimate derived from comp ASIN review-count signals and category saturation, always labeled as estimated, never measured.
How does the KDP keyword selector avoid wasting slots?
After the AI selects 7 slots, a post-LLM compliance validator checks each slot for: prohibited promotional claims (bestseller, award-winning, free), competitor author/title names, words already in the title or subtitle, exact category-label duplication, repeated stems across slots, and a conservative 50-character cap. If the slots fail, the selector re-rolls once before falling back with a clear caveat.
Does it scrape Amazon pages for comp data?
No. Comp resolution is ASIN-first via API only (Amazon Ads product API where authorized, or Product Advertising API where credentials are configured). If neither API path resolves an input, the report records the comp as unresolved and proceeds from title and category signals — surfaced as an explicit caveat.
How are the Amazon Ads keywords different from the KDP backend keywords?
They use different scoring models. KDP backend keywords prioritise relevance, discoverability, and compliance — they live inside Amazon's algorithm. Ads keywords prioritise commercial intent and bid efficiency, bucketed across broad/phrase/exact match types with suggested bid ranges. The same word may show up in both lists, or in neither.
What if I don't have comp titles or ASINs to provide?
The tool runs without them, but the report becomes weaker on competition estimates and positioning notes. You'll see explicit caveats telling you which sections were degraded.
How accurate is the suggested bid range?
The bids are heuristic guidance anchored to typical KDP book-ad CPCs, adjusted by observed volume and estimated competition. They are not advertiser-account data — your real auction prices may differ. Treat them as a starting band, not a target.