Common Mistakes in Book Reviews: A Checklist for Fair, Spoiler-Free Criticism
A review does two jobs at once: it tells a reader what a book is like, and it protects them from learning too much too soon. Get the balance wrong and you either bury the book under a retelling of its own plot or give away the one turn the author spent three hundred pages setting up. Most reviews that go wrong aren't written by careless people. They're written quickly, by readers who liked the book and wanted to say so. What follows are the mistakes that turn up again and again, and how to fix each one.
The Plot Summary That Eats the Review
If more than a third of your review is "and then", you've written a synopsis with an opinion attached. The blurb already tells readers what happens; your job is to tell them what it's like to read. A useful test: cover the middle of your draft and read only the sentences that aren't describing events. If almost nothing remains, start again.
Place the book with two sentences. "A widower returns to the coastal town where he grew up, and the neighbours remember more than he does." That's enough to orient anyone. The inheritance, the second-act betrayal and the dog's fate can wait. Before drafting, write your summary in three sentences, then delete two. If a detail matters to your judgement of the book, mention it as evidence rather than as plot — "the middle sags because two subplots compete for the same twenty pages" tells a reader more than a scene-by-scene account ever will.
Vague Praise and Blunt Scorn
Adjectives do very little work on their own. "Beautifully written" and "compelling" could describe a thousand books; so could "unputdownable", which also isn't a word. The fix is simple but takes effort: replace the adjective with the thing that caused it. Name the technique. Was it the voice, the pacing, the dialogue, the structure, the restraint? A reader who knows what you noticed can decide whether they'd notice it too.
- "Beautifully written" — say what the prose does. Short, hard sentences that refuse to comfort? Long, looping paragraphs that mimic a character's anxiety?
- "Compelling" — say what kept you reading, and where you slowed down.
- "Unlikeable characters" — say whether the book wants you to like them, and whether it earns the difficulty.
- "Slow" — say whether it's slow and deliberate or slow and tangled. They're different problems.
- "Not for me" — say who it is for, or admit you're not the right reader.
Vague: "The prose is beautiful and the characters are unforgettable."
Specific: "The sentences are short and flat, and the grief sits in what the characters don't say to each other."
Scorn needs the same treatment. A one-line dismissal reads as bad temper, not criticism. If a book fails, describe the failure precisely, and be fair about what it was attempting.
Forgetting Who the Book Is For
A review that ignores its audience helps nobody. If you found a novel slow, say that it's a quiet, interior book with very little incident — then a reader who wants exactly that will pick it up, and a reader who doesn't will save their money. Both outcomes are good.
Judge books by their own aims, too. A romance isn't failing because there's no murder investigation; a thriller isn't failing because the couple end up together. Mention the genre, name the kind of reader it suits, and note where expectations are likely to trip people up. If you're reviewing a sequel, say plainly whether it stands alone, without describing how the earlier book ends.
Spoilers Are More Than Endings
Most reviewers know not to reveal the final page. Fewer think about the other reveals: a narrator's identity, a structural trick, a death at the halfway mark, the fact that two timelines are actually one. Publishers hide these on purpose, so treat anything past the first fifty pages as confidential unless the jacket copy already mentions it.
Two habits help. First, describe the effect rather than the event: "there's a turn around the middle that changes how you read everything before it" warns the reader without ruining anything. Second, don't announce that a twist exists at all if you can avoid it — some readers will spend the whole book braced for it. And if you must include a spoiler, put it clearly behind a warning rather than burying it in the middle of a paragraph. A polite note at the top costs you nothing and keeps a reader's goodwill.
Judging the Book You Wished It Was
It's easy to review the novel in your head rather than the one in your hands: the one with a tighter ending, a different protagonist, a little less description of the weather. When you catch yourself writing "I wanted this to be...", pause. Ask what the book set out to do, and whether it does that well. Disappointment is worth recording — just be honest that the gap is between the book and your expectations, not between the book and some universal standard.
Ratings That Fight the Text
Readers scan the stars before they read a word, so make sure the two agree. A rave review attached to two stars, or a furious four-star write-up, reads as muddle. If you use a rating system, check that your score matches your tone, and say briefly what your scale means — a three from a generous reviewer and a three from a severe one aren't the same thing.
A Checklist Before You Publish
- Can the plot summary be cut to two sentences without losing the sense of the book?
- Does every compliment name something specific — a technique, a scene, a quality of voice?
- Have you said who will love it and who won't?
- Are you judging it by its own aims and its genre?
- Have you checked for mid-book reveals, structural twists and sequel spoilers?
- Does your rating match your tone?
- Would the review make sense to someone who hasn't read a single other review of this book?
- Is there one sentence you'd defend if the author read it?
Read the draft once more with those questions in mind, then cut the first paragraph and the last. What's left is usually the review: a clear, fair recommendation from one reader to another, with the pleasure of the book still intact for whoever picks it up next.
Photo: StockSnap / Pixabay
