Common Mistakes New Book Reviewers Make – and How to Avoid Them

A first review is an odd piece of writing. You are trying to be fair, useful and interesting at the same time, and the habits that make for good conversation — enthusiasm, plot summary, generosity towards a friend's recommendation — often work against you on the page. The mistakes new reviewers make are rarely failures of taste. They are failures of technique, and most of that technique can be learned in an afternoon. Here are the ones that turn up again and again, with fixes you can apply to your next review before you publish it.

Spoiling the Plot Without Noticing

Most reviewers know not to give away the ending. Far fewer notice the smaller betrayals: the mid-book death, the estranged sister who turns out to be the narrator, the fact that the wedding in chapter three never happens. A workable rule is to stay inside the first fifth of the book. If the publisher's blurb mentions it, you can mention it. If it doesn't, you are probably handing something over that isn't yours to hand over.

Watch out, too, for the coy spoiler. "All I'll say is that nothing prepares you for the final chapter" tells the reader a great deal — it tells them to brace, which changes how they read every page before it. If a twist is genuinely central to your argument, signpost it plainly: I need to discuss the ending here, so look away if you haven't finished. Readers respect a clear warning far more than a knowing hint.

Vague Praise Is Worse Than Silence

"Beautifully written" and "I couldn't put it down" appear in hundreds of reviews a week, and they tell a reader almost nothing. Specificity is the whole job. Compare these pairs:

• "The characters were relatable." Say instead what a character chooses, and whether you believed the choice. Relatability isn't a quality of the book; it's a reaction of yours, and reactions need evidence.
• "Beautifully written." Describe the prose. Short, clipped sentences that hurry the eye along. Long looping ones that hold you still. Dialogue that sounds like people talking over each other. If one line stopped you dead, quote it briefly.
• "I couldn't put it down." Tell us where you nearly did. A book that grips for three hundred pages and sags for forty is worth describing precisely — that is a real, useful judgement.
• "A must-read." For whom? A reader who loves slow, interior novels and a reader who wants a plot that moves are different people, and your review should let both of them decide.

Vague criticism does the same damage. "The characters were flat" is an accusation without a case. Name one. Describe the moment you stopped believing in them. Then the author, and the reader, has something to argue with.

Retelling the Story Instead of Reviewing It

Long summaries are the most common filler in beginners' reviews. The trouble is that a summary has no argument in it. Trim yours to a single short paragraph and make sure every detail in that paragraph is there to set up a judgement. If you could delete your opinion and the summary would still stand perfectly well on its own, you have written a synopsis rather than a review. Ask of each sentence: does this help a reader decide?

Judging the Book You Wanted, Not the One You Read

A quiet literary novel is not a failed thriller. A thriller is not a failed poem. Before you criticise, work out what the book is trying to do, then judge whether it does that — and whether it was worth doing. This is not the same as being kind. A book can aim high and miss, and saying so, with reasons, is entirely fair. What isn't fair is docking marks because the author wrote the book they wanted instead of the one you had in mind.

The same discipline applies to the author. The narrator is not the author, and an unlikeable voice is often the point. Keep the biography out of it unless the book invites it in.

Ratings, Scores and the Temptation to Inflate

Star ratings mean different things to different people, which is why it helps to explain yours in a line. Whatever system you use, use it consistently: if five stars is your highest praise, spending it on a book you liked perfectly well leaves you nowhere to go. Write the review first, then choose the number that matches what you have argued. If the two disagree, the review is the more honest of the pair.

Write for the Reader, Not for the Author

Every review has three possible audiences: the reader deciding what to buy, the reader who has already finished the book, and the author. Aim at the first. Say who might enjoy it, what it resembles in mood or pace, and what a reader should bring to it. Include the practical detail people actually want. Is it long? Is it slow? Is it bleak? Does it need a quiet week and no interruptions?

Then read your draft aloud once. Wrong character names, a plot point you have misremembered, a typo in the title: these are the small errors that quietly tell a reader you skimmed.

A Last Look Before You Publish

Six questions, answered honestly:

1. Can a reader tell from this whether they would like the book?
2. Have I given away anything past the first fifth?
3. Have I replaced every vague adjective with one specific observation?
4. Am I judging the book that exists, or the one I expected?
5. Would I say this, in these words, to the author's face?
6. Have I read it aloud and checked the names?

Reviews improve faster than almost any other kind of writing, because the feedback arrives immediately: you know whether you were fair and clear the moment you reread your own words. Write the next one. And keep a notebook of the details a book made you notice — the phrase you underlined, the scene you described to someone else straight afterwards. That notebook, not the star rating, is where good reviewing starts.

Photo: Pexels / Pixabay