How to Write a Book Description That Sells

Your book description is the hardest 150 words you will ever write — and the most valuable.

A reader arrives at your page from a cover they liked. What happens next is decided almost entirely by the paragraphs underneath it. Not by how good your book is; by how well those paragraphs promise what the book delivers.

I've read a lot of indie book descriptions putting this site together. Most of them make the same three mistakes, and all three are fixable in an afternoon.

What a description is actually for

A description is not a summary. This is the misunderstanding behind most weak blurbs.

A summary tells someone what happens. A description makes someone want to find out what happens. Those are opposite jobs — one satisfies curiosity, the other creates it.

Your description has one goal: convince a browsing stranger that this book is worth their evening. Everything that doesn't serve that goal is costing you readers.

Step 1: Open with a hook, not a setup

You have about one line before someone scrolls away. Spend it on the most interesting thing in your book.

Most first drafts open with throat-clearing:

"Sarah Mitchell was born in a small town in Yorkshire, where she lived a quiet life with her mother and two sisters…"

Nothing has happened yet, and the reader is already gone. Compare:

"Sarah has three days to prove her sister didn't do it."

Same book. The second version starts where the story gets interesting.

For non-fiction, the equivalent is leading with the reader's problem rather than your credentials:

"You've read four books on productivity and you're still behind."

Step 2: Follow the shape that works

Almost every effective description follows the same three-part shape.

Fiction:

1. The hook — one or two lines that create a question
2. The situation — who wants what, and what stands in the way (3–5 sentences)
3. The stakes — what it costs if they fail, ending on tension rather than resolution

Non-fiction:

1. The problem the reader recognises in themselves
2. The promise — what they'll be able to do after reading
3. The proof — briefly, why you're worth listening to

Notice what's missing from both: the ending. Never resolve the question in your description. The description sells the question; the book sells the answer.

Step 3: Cut everything that isn't working

Read your draft and delete:

• Character names beyond one or two. Readers can't track a cast they haven't met. "Her brother" is clearer than "Tobias, her half-brother from her father's second marriage."
• World-building nouns. Invented places, magic systems and factions mean nothing to someone who hasn't read the book yet.
• Subplots. One thread. The description is a trailer, not a table of contents.
• Praise of your own book. "A gripping, unforgettable masterpiece" is a claim only readers can make. Show them something gripping instead.
• Your writing process. "This book took me seven years" belongs in your bio, not your pitch.

If you cut a third of your first draft, you're on track.

Step 4: Format it to be skimmed

Nobody reads a description as a paragraph. They scan it.

• Short paragraphs — one to three sentences each
• A line break between each part of the structure above
• Bold sparingly — the hook line, maybe one more phrase
• 150–200 words for fiction; up to 250 for non-fiction

On Amazon, the description field supports limited HTML through KDP, so bold and line breaks survive — plain line breaks in a text box often don't. Whatever you do, check how it renders on a phone before you leave it: most of your readers will only ever see the first three lines and a "read more" link.

Step 5: Test the first two lines alone

Here's the test almost nobody runs. Copy just the first two lines of your description into a blank document and read them cold.

That's realistically all a browsing reader sees before deciding to expand or leave. If those two lines don't create a question, the other 180 words will never be read.

A template you can fill in

Fiction:

[One-line hook that creates a question.]

[Character] is [ordinary situation]. But when [inciting incident], [they] must [difficult goal] before [deadline or consequence].

[Complication that makes it harder.] With [what's at stake], [character] will have to [hard choice] — or [cost of failure].

[Book title] is a [genre] for readers of [two comparable authors].

Non-fiction:

[The problem, stated as the reader experiences it.]

Most [audience] believe [common assumption]. But [why that fails].

In [Title], [author] shows you how to [specific outcome] — without [the thing they dread]. You'll learn [three concrete things].

For [specific reader], not [who it isn't for].

That last line matters more than it looks. Naming who a book isn't for makes the promise credible to the people it is for.

Where your description is working for you

Your description isn't only on Amazon. It's what search engines read to understand your book, what an AI assistant quotes when someone asks for a recommendation in your genre, and what appears on every site that lists you — including your free IndieFiction book page.

That's the practical reason to fix it once and use it everywhere. A book page with a strong description gets found and gets chosen; a page with a title and a cover and nothing else does neither.

If you already have a book listed with us and its description is thin, edit it from your account — it takes five minutes and it's the highest-return five minutes in indie publishing.

The one thing to remember

Your description is not a summary of your book. It's a promise about the experience of reading it.

Make the promise specific, make it in the first two lines, and stop before you give away the answer. Then go and check how it looks on your phone.

Once your description earns the click, the next question is whether anyone can find the page at all — that's how to promote your book as a beginner, and free places to list your book if you're starting from zero.