There is a moment every book blogger knows. The book is finished, opinions are swirling, and the cursor is blinking. What comes out is often either breathless praise or a demolition job — and neither is much use to the reader deciding whether to spend their money.
A fair review sits between those two poles. It says what the book is trying to do, how well it does it, and who might enjoy it, without pretending that taste is the same as truth. It also respects the fact that someone spent years writing the thing — and that another reader, with different expectations and a different life behind them, might take something completely different from it.
Fairness is not the same as blandness. A fair review can be a five-star rave. It can be quietly furious. What it cannot be is careless: a handful of vibes dressed up as judgement, typed out in ten minutes because the post is due and the ARC has been sitting on the shelf since March. That is the sort of review nobody needed, least of all you.
Here is how to build one, from the first note you scribble to the last line you publish.
Read With a Notebook, Not a Scorecard
Fairness starts before you sit down to write. Keep a notes file open while you read: page numbers, sentences you admired, the exact point where your attention began to wander, the name of the character you could never quite keep straight, the chapter that made you put the kettle on rather than turn the page.
Compare these two lines. I got bored in the middle is a feeling. The middle third loses momentum once the characters leave the coast, and the subplot about the missing sister never rejoins the main story is evidence. You can build a review on the second one. The first one you can only repeat, and repeating it teaches your reader nothing.
Notes also protect you from the recency effect — the trick your brain plays by remembering only the final fifty pages. Most of us finish a book and grade it on its ending. Flicking back through your notes often reveals that you adored the first half and resented the last, or that the slow opening paid off beautifully by chapter nine. A two-line verdict written from memory would have flattened all of that.
Try not to measure a book against expectations it never set for itself. A quiet novel about grief is not failing because it lacks a car chase. A cosy crime mystery is not a lesser book because it doesn't interrogate the human condition. If you picked up a romantic comedy and it turned out to be a bleak family saga, the useful question is not "why isn't this funny?" but "does it work as the thing it actually is?"
And if you didn't finish? That's allowed. Say where you stopped and why, then review what you actually read rather than what you assume happens later. Readers trust a reviewer who admits a limit far more than one who bluffs. I read to page 120 and stopped, because the constant shifting between six perspectives kept me at arm's length is honest, specific and still a review.
A Structure That Nearly Always Works
Reviews don't need a formula, but a loose shape stops them wandering off into three paragraphs about your week. For most blog posts, this order works:
- A line or two about what the book is and the mood it left you in.
- A short summary in your own words, covering the setup only.
- What worked, with at least one example.
- What didn't, with at least one example.
- The readers it suits, and the readers it won't.
- A verdict in two or three sentences.
The balance between praise and criticism needn't be even; it needs to be proportionate. A book that attempts something ambitious and misses deserves more discussion than a pleasant, forgettable one. And if the only real problem is that you don't like the genre, say so plainly, then review the book on its own terms anyway.
The Summary Is Not a Synopsis
Aim for 80 to 120 words. Enough to orient a reader who has never heard of the book; not so much that they feel they have already read it. Never copy the publisher's blurb — it is written to sell, not to describe, and your readers can tell the difference instantly. If you can't summarise the setup without giving away a twist, summarise the feeling instead: a novel about a family returning to a house they shouldn't have kept tells me more about the reading experience than a plot diagram would.
Balance Is Proportion, Not Politeness
Some bloggers operate a strict "two good points, two bad points" rule. It can be a useful training wheel, but it also produces reviews that sigh politely at brilliant books and invent faults in bad ones. Follow your notes instead. If a novel did almost everything right, say so and use your one criticism honestly. If it fell apart, explain the mechanism of the collapse.
The Spoiler Question
There is no universal rule, but there is a decent test: would a reader be annoyed to learn this before picking the book up? A plot point from the first fifty pages is fair game. The identity of the murderer, the death in chapter twenty-two, the reveal that the narrator has been lying, the ending — those need a warning, however famous the book is.
If you genuinely need to discuss the ending, put a clear line in the post — Spoilers below — and give readers somewhere to stop. Most will stop. The ones who stay have already read it, and they are exactly the people who want to argue with you in the comments, which is one of the nicer parts of blogging.
A review is a conversation with future readers, not a verdict handed down from above.
Free Books, Blog Tours and the Honesty Problem
Most UK book bloggers review at least some books they didn't pay for: a NetGalley approval, a parcel from a publisher's mailing list, an invitation to a blog tour. None of that makes a review dishonest. But it does make a short disclosure line sensible — one sentence near the top, in plain English: I received a free copy from the publisher in exchange for an honest review.
Then actually be honest. A blog tour post that is all adjectives and no argument isn't a review; it is a press release with your name on it. Most publicists would rather have a thoughtful mixed review than another round of unputdownable. Nobody's career ends because a blogger gave a book three stars, but a blogger who has clearly never disliked anything quietly loses the thing that made them worth approaching in the first place.
Two rules worth keeping: never review a book you haven't read, and never let a free copy shift your rating by a single star.
Ratings, If You Use Them
Five stars, four stars, half stars, or no rating at all — pick a system and stay consistent, because a rating only means something once readers have learned what your four stars looks like. If your four covers both "very good, a few rough edges" and "the best thing I've read this year but not quite five", the number stops carrying information.
Ratings also can't hold nuance. That is what the words are for. A three-star review that explains the prose is gorgeous and the plot is a mess has done its job perfectly — and is far more useful than a five-star review that says only that the author is a genius.
Watch Your Wording
Review the book, not the person who wrote it. You have no idea what was happening in their life during the eighteen months they spent on it, and you have no evidence for claims about their motives.
Compare the pacing collapses in the final act with the author clearly ran out of ideas and rushed the ending. The first is a judgement about the text, supported by your reading. The second is a guess about a stranger, dressed up as fact. Words like clearly, obviously and objectively usually signal that a personal reaction is being inflated into a universal law. Phrases like I found, it seems to me and for this reader don't weaken your point — they make it harder to dismiss.
The Ten Minutes Before You Publish
Run through this list. It takes less time than writing the post, and it catches most of the things that make a review feel unfair.
- Does the opening line tell a reader whether they'd want this book?
- Is the summary in your own words, with no blurb copy-pasted?
- Have you given a concrete example for each point you've made?
- Have you said who the book is for, as well as who it isn't?
- Is there a spoiler warning if you needed one?
- Have you disclosed a free copy, if there was one?
- Would you be comfortable if the author read this?
That last question isn't about softening the criticism. It is about making sure the criticism is aimed at the book rather than at the person who wrote it — and that you'd stand behind every sentence if somebody quoted it back to you.
Fairness Is a Habit, Not a Talent
Nobody writes a good review on their first attempt, or their fortieth. Early posts tend to be either plot summaries with a verdict stapled on, or long personal essays about how a book made you feel with almost nothing about how it was made. Both are normal. Both get better with practice, and the practice is simply this: read carefully, take notes, show your working, and say what you actually think in language you'd be happy to use out loud.
Over a year or two, something quietly useful happens. Readers start to know what your four stars means. They learn that when you say a book is slow you usually mean atmospheric, and when you say a book is gripping you are not easily impressed. That is trust, and it is the only real currency a book blog has.
Say what you read. Say what you thought. Say why. Then hit publish.
Photo: StartupStockPhotos / Pixabay
