2026-06-30 · all guides
How to Write and Publish a How-To Guide on Amazon KDP
Scope to one outcome the reader can verify
A how-to guide lives or dies on the precision of its promised outcome. "How to Start a Business" is not an outcome; "How to Start a Cleaning Business in 30 Days" is, because the reader can check whether it happened. Scope your book so the final chapter describes a state the reader can verify: the permit approved, the first paying client invoiced, the garden bed producing. If the outcome is fuzzy, every chapter inherits the fuzziness.
Then define the starting line just as precisely. A guide that assumes tools the reader lacks, or re-explains basics the reader has, loses them either way. Write one paragraph describing exactly who stands at the start: what they know, what they own, how much time and money they have. This paragraph becomes your introduction and quietly becomes your marketing copy too.
The sequential chapter pattern
How-to structure is the most formulaic in nonfiction, and that is a feature. Chapter one sells the destination and dissolves the two or three biggest objections. Chapter two covers prerequisites: tools, costs, legal basics, setup. Then the core: six to ten chapters, each one step of the path in strict order, where every chapter opens by stating what will exist by its end. Close with a troubleshooting chapter, the most under-written and most-praised chapter in the genre, and a maintenance or what-next chapter.
Inside each step chapter: why the step matters (short), exactly how to do it (long, with numbers, names, and settings), the mistakes people make at this step, and a checkpoint the reader can use to confirm they did it right before proceeding. Length norm for the genre is 20,000 to 35,000 words. Below that, buyers feel they bought a blog post; above it, the padding is usually motivational filler the genre does not need.
Specificity is the entire product
The gap between a four-star how-to and a two-star one is measured in named specifics. "Get the required licenses" is filler; "in most US states you need a general business license from your city, typically 50 to 100 dollars, plus a sales tax permit from the state, free in most cases; both are online applications that take under an hour" is product. Every vague instruction in your draft is a refund waiting to happen.
This is where consultants and practitioners have an unfair advantage: your delivery process, client checklists, and pricing knowledge are the specifics competitors cannot fake. A consultant's internal onboarding checklist, cleaned up, is often chapter three of a great how-to book. Many consultants use ebookdone to generate the structural draft from their topic for $9 and then inject their process specifics in editing; /for/consultants covers that workflow, and the free preview at /new shows the outline before anything is paid.
Titles, keywords, and categories that match intent
How-to buyers search in verb phrases, so titles in this genre should read like the search: "How to Start a Cleaning Business," with a subtitle stacking the qualifiers: "A 30-Day Step-by-Step Guide for First-Time Owners with Under $2,000." Use all seven KDP keyword slots for variations: "start a cleaning company," "cleaning business plan," "residential cleaning startup." Choose categories by the underlying subject, like Business & Money > Small Business & Entrepreneurship, not by format.
Pricing follows perceived stakes: a hobby how-to sits at 4.99 to 6.99 in ebook, while a business or income-related how-to supports 7.99 to 9.99 because the buyer expects a return. Paperbacks in this genre convert well as reference objects; keep them at the standard 6 x 9 trim and price at 12.99 to 15.99.
Pitfalls: outdated steps, screenshots, and thin content
The genre's decay problem: any guide with software steps or prices goes stale. Keep version-specific instructions in ranges and principles where possible, state the writing date, and plan an annual refresh upload; KDP lets you update the manuscript on a live listing any time. Avoid screenshot-heavy interiors; screenshots date the book instantly, render badly in print, and inflate file delivery costs on the 70 percent ebook royalty plan.
On the KDP review side, the how-to categories are where Amazon's thin-content enforcement is most active, because low-effort AI guides flooded them. Books get flagged for being too short for the promise, duplicating freely available content, or misleading titles. The defense is the same as the sales strategy: verifiable specifics, a real troubleshooting chapter, and an outcome the title accurately describes.
FAQ
How long should a how-to book be?
The genre norm is 20,000 to 35,000 words. That is enough to cover a real path with specifics and troubleshooting without motivational padding. Buyers in this genre punish thin books and bloated ones equally.
Should I include screenshots in a how-to guide?
Generally no. Screenshots date the book, print poorly in black-and-white, and increase ebook delivery fees. Describe interfaces in words at the level of principle, and keep version-specific detail in ranges.
Why do how-to books get rejected on KDP?
The common causes are thin content relative to the title's promise, duplication of freely available material, and misleading titles. Specific, verifiable steps and an honest title clear KDP review without trouble.
Skip the formatting entirely. ebookdone writes the book and hands you every KDP-ready file — $9 per book, no subscription. The outline and first chapter are free.
Start your book free