Guide 03

Writing a book description that sells

Amazon gives you 4,000 characters and a handful of HTML tags. The first two lines are what most readers see. Here's the structure that works.

Last updated Apr 21, 2026v1 · pending Spellbound

The book description is not a summary. It's a sales page, and the thing it's selling is an emotional promise: "if you read this, you'll feel X". Write it as a summary and you'll get polite nods and no clicks.

The hard limits

KDP gives you 4,000 characters in the description field. That includes every HTML tag you use. A description with heavy <b>/<br> formatting will have fewer visible words than a plain one with the same character count — a realistic working target is 300–400 visible words once formatting is in.

Supported HTML tags:

<b> bold
<i> italic
<br> line break
<h1>, <h2>, <h3> headings
<p> paragraph

Unsupported (Amazon strips them, keeps the text): <div>, <span>, <ul>, <ol>, <a>, <img>. Don't waste characters on tags that get removed.

What readers actually see

Amazon shows roughly the first two lines of your description before a "Read more" link. On mobile, less than that. This means your first 150–200 characters are doing most of the work. Treat them like the subject line of a cold email: they decide whether the reader keeps reading or bounces.

The structure that works for novels

Hook (1–2 lines). The first concrete, specific thing that makes someone curious. Not the setup, not the world-building — the thing the book is actually about. "When the sky began to scream, Ethan was already seventeen hours into the worst day of his life." This is your top-of-description real estate.
Stakes (2–4 lines). Who is the protagonist, what do they want, what's in the way, what happens if they fail? Keep it concrete. Proper nouns for places and people, not abstractions. Mention the genre signals without saying the genre — "the last arcology", "the crashed cruiser", "the voice speaking from every surface at once".
Promise (1–2 lines). What experience is this book going to give the reader? "A first-contact novel about the cost of being curious in a city that punishes it."
Comps or endorsement (optional, 1–2 lines). Perfect for readers of [Author X] and [Author Y]. Or a quote from a reputable review. Don't fake these; Amazon reviewers spot it.
Call to action (1 line). Short. "The crash is just the beginning. Read on."

This gets you to about 350 words. The visible area will be used up by parts 1 and 2; parts 3–5 are for the reader who clicked "Read more" and is 70% committed already.

Tactical notes

Lead with a sentence, not a paragraph. A one-sentence hook followed by a line break reads scannably. A dense opening paragraph doesn't.
Use <b> sparingly. Two to three bold phrases total. Usually the opening hook and the promise line.
Drop most adjectives. "Gripping", "pulse-pounding", "unforgettable" are marketing throat-clearing. Readers discount them. Replace with concrete detail.
Genre signals in the specifics. Instead of writing "In this dark fantasy novel, our hero...", write a first line that reads like dark fantasy. The genre is conveyed by what's on the page.
No spoilers, but no teasing either. "But there's a twist you won't believe!" is a red flag. Trust the premise.
Update it. Amazon lets you change the description anytime. A/B testing is informal — change it, wait two weeks, see if conversion moves.

The short version

Write the hook first — one or two lines, concrete, specific, opens with an event or image, not a setup.
Add 2–4 lines of stakes with proper nouns.
One line of promise.
Optional comps.
One-line CTA.
Format with <b> on the hook and promise, <br><br> between paragraphs. Check total character count under 4,000.

Anthony's take