What Makes a Good Book Review? An Explainer for New Reviewers

What Makes a Good Book Review? An Explainer for New Reviewers

Anyone who has finished a book and opened a blank page knows the feeling. You have opinions — plenty of them — and no clear sense of which ones belong in a review. The temptation is to retell the plot and then announce whether you liked it. That leaves a reader with almost nothing to work with.

A good review does something harder. It explains what the book set out to do, how well it managed it, and who will be glad they read it. None of that requires a literature degree, just attention, honesty and a bit of structure.

It also helps to remember that a review is not a verdict handed down from a judge's bench. It is a conversation with a stranger in a bookshop. Your job is to give that stranger enough clear, specific information to decide whether this book is worth their time — and perhaps enough pleasure in the prose to make the review worth reading on its own.

Start With What the Book Is Trying to Do

Fair judgement starts with intent. A cosy crime novel is not failing because it lacks bleak existential dread, and a history book is not failing because it has no plot twists. Before deciding whether a book works, work out what it is attempting: to entertain, to unsettle, to argue a case, to capture a particular voice, to make you laugh on a train.

That means reading on the book's terms rather than your own. If a thriller's job is to keep you turning pages, then pace, tension and clarity matter more than lyrical sentences. If a memoir's job is honesty about a life, then the quality of its observation matters more than whether you would have made the same choices.

Try writing a one-sentence version of the book's promise. For example: This is a novel that wants to make a small town feel enormous, and to show how a single rumour reshapes every relationship in it. Once you have that sentence, your review has a spine. Every judgement can then be tested against it: does the book keep its promise, complicate it, or quietly abandon it halfway through?

None of this means being soft. If a novel aims for warmth and lands on sentimentality, say so, and show where the tone slips. Judging a book against its own ambitions is stricter than judging it against your preferences, not looser.

The Anatomy of a Useful Review

Most useful reviews, whatever their length, do five things in roughly this order.

1. Hook the reader. One or two sentences that give a sense of the book's tone or its central tension. Not "this is a novel about a woman who moves to Cornwall", but something that makes the next sentence necessary.
2. Place the book. Genre, period, style, and two or three honest comparisons, so a reader can picture what they are being offered.
3. Describe the experience of reading it. Voice, pacing, structure, characters, the overall shape. This is where most of a review lives.
4. Show your working. A short quotation, a scene, a repeated habit in the prose. Evidence is what separates a review from a mood.
5. Land the verdict. Who will love it, who will bounce off it, and what it asks of the reader in time and attention. Say plainly whether you would recommend it.

A hundred and fifty words cannot do all five at length, but it can still do all five in miniature. In a longer piece, the order matters: a reader who is three paragraphs in and still has no idea what the book is like has been let down.

It can help to think of these five moves as a shape: a doorway, a map, a journey, a piece of evidence, and a signpost. The doorway invites the reader in. The map tells them where they are. The journey describes what it felt like to travel. The evidence proves you were paying attention. The signpost tells them where they might go next.

How to Judge a Book Fairly

Separate taste from craft

"I found this slow" and "the middle third sags because two subplots never connect" are both honest, but only one of them helps someone decide. Personal reaction belongs in a review, and is often the most interesting part, as long as you explain what produced it. Name the cause, not just the feeling.

If you disliked a character, ask whether the author intended you to dislike them. If you were bored, identify the pages where your attention drifted and what the book was doing there. If you were moved, find the sentence or scene that did it. That specificity turns a private reaction into public criticism.

Mind your blind spots

Every reader has them. Present-tense narration, dialect, second-person address, long digressions about food: something will irritate you more than it irritates the next person. Notice it. If a stylistic choice would not bother you in a book by an author you already love, it is worth asking whether it is the book's problem or yours.

Blind spots are not always negative. You may be a sucker for a certain kind of ending, a certain kind of narrator, a certain kind of sentence. Knowing your soft spots is as useful as knowing your allergies. It lets you say, I am inclined to forgive this book its flaws because I love what it is trying to do, but readers who do not share that taste may feel differently.

Consider the intended reader

You are not reviewing for everyone. A book written for teenagers should be judged partly by whether it respects teenage readers, not by whether it suits a forty-year-old critic's mood. A scholarly monograph should be judged by the standards of its field, not by whether it would make good beach reading. A romance should be judged by whether it delivers emotional payoff, not by whether it avoids every familiar beat.

That does not mean surrendering your own response. It means holding two questions at once: Who is this for? and What did I, as one reader, get from it? The best reviews answer both, and make clear which is which.

What to Do About Spoilers

Spoilers are not a matter of never mentioning what happens. They are a matter of not stealing the experience the author designed. Revealing that a detective solves the case is usually fine; revealing which suspect did it, and why, is usually not. In literary fiction, the distinction can be subtler: a death on page fifty may be the premise, while the consequences of that death are the story.

A useful rule is to describe events at the level of the book's setup, not its revelations. You can say that a marriage unravels after a secret surfaces without naming the secret. You can say that the final chapter recontextualises everything without explaining how. If a spoiler is unavoidable for the point you want to make — and sometimes it is — warn the reader first, and keep the discussion brief. A review that depends on a ruined surprise is rarely worth the cost.

Use Evidence, Not Just Adjectives

Adjectives are cheap. Beautiful, gripping, disappointing, original — all of them can be true, and all of them can mean almost anything. Evidence is what gives them weight. A short quotation, a description of a structural choice, or a comparison to another book can show a reader exactly what you mean.

Example: Instead of saying "the prose is beautiful," you might write, "The prose is beautiful in a narrow, exact way: the author rarely uses two adjectives where one will do, and the result is a landscape that feels carved rather than painted."

One quotation is often enough, but choose it carefully. A good quotation should be representative, not exceptional. If you pick the single best sentence in the book, you are not giving a fair sample. If you pick a bad sentence to mock, make sure it is not an outlier. Quote in service of a point, not as decoration.

Common Pitfalls for New Reviewers

• Retelling the plot. A synopsis is not a review. Keep plot summary short and use it only to set up your judgement.
• Being vague. "I loved it" or "it wasn't for me" tells a reader nothing they could not guess.
• Being cruel for effect. Wit at the expense of accuracy persuades no one who was actually considering the book.
• Ignoring the audience. A review that never says who the book is for leaves the reader to do all the work.
• Reviewing the author instead of the book. Context can matter, but the primary question is what the book does on the page.
• Forgetting to say what the book is like. Genre, tone, pace and style are not spoilers. They are the map.

A Simple Checklist Before You Publish

1. Have I said what the book is trying to do?
2. Have I described what reading it is actually like?
3. Have I given at least one concrete example or quotation?
4. Have I separated my taste from the book's craft?
5. Have I said who will love it and who might not?
6. Have I made my recommendation clear?
7. Have I avoided unnecessary spoilers?
8. Would a stranger finish this review knowing whether to read the book?

If you can answer yes to most of those, you are already writing better reviews than most. If you can answer yes to all of them, you are writing reviews that people will seek out, trust, and argue with — which is the highest compliment a review can receive.

The Point of It All

Reviews are not just consumer advice. They are part of how books continue to live after publication. A thoughtful review can send a reader to a book they would never have found, or help them understand why a book they disliked still mattered. It can preserve a sentence, a scene, a way of seeing. It can disagree without diminishing.

So when you sit down with your blank page, you do not need to be cleverer than the book. You need to be clear about what you noticed, honest about what you felt, and generous enough to imagine the reader on the other side. Do that, and your review will be useful — which is the first and most lasting thing a good review can be.

Photo: Pexels / Pixabay