How to Write a Book Review for Classic Literature That Stands Out

Last winter a student asked me to look over her review of Jane Eyre. It was fine. Clear summary, tidy paragraphs, quotes in the right places. And completely lifeless — because everything she said about the book could have been written by someone who had never read it. The novel was treated as a museum piece you're supposed to admire, not a piece of writing you're supposed to argue with.

That's the trap with writing a book review for classic literature. Unlike a review of a new novel, where you can surprise your reader with plot and personality, a classic arrives pre-loaded with reverence. Everyone knows the ending. Everyone knows it's supposed to be good. Your job is not to inform people of the plot or to confirm what they already suspect about its greatness. Your job is to make them see a familiar book differently.

Here's how I do it, what I got wrong for years, and the specific criteria I use when the book in front of me has been in print for a century or two.

Why reviewing a classic is a different job from reviewing a new book

A review of a fresh novel has one built-in advantage: the reader doesn't know what happens. You control the pacing of revelation. With Great Expectations or Madame Bovary, that advantage is gone. Your reader has probably absorbed the plot through cultural osmosis without ever opening the book — through adaptations, school syllabi, jokes, a film their parents liked.

So what are you actually offering?

Two things, in my experience. First, the experience of reading it now: what it feels like in 2026, where it drags, where it stuns, where the translator's choices make your teeth ache. Second, a judgment on its reputation: does the book deserve the place it holds, or has it survived on inertia?

Both require you to have a real opinion. This is where most student reviews collapse. They assemble a balanced-sounding paragraph about "themes of love and loss" that could be pasted onto a dozen different novels without changing a word.

What makes a book classic literature, and why that matters to your review

There is no committee and no certificate. A classic is a book that keeps getting reprinted, retaught, re-adapted and reargued with across generations — the thing that makes it "classic" is that people keep returning to it for reasons that outlast the moment it was written. That's why a review of a classic is inherently a review of a conversation, not just a text.

Practically: your opinion is one voice in a long argument. Say where you stand in it. "Critics have long read the novel as X; I think that reading flattens the ending" is a stronger sentence than any isolated verdict, because it shows you know other people have read this book before you.

What are the 5 C's of a literature review?

The 5 C's are a planning framework often taught for literature reviews: cite, compare, contrast, critique, connect. They're borrowed from academic writing about source reviews, and they transfer neatly to reviewing a classic.

• Cite — identify the edition, translator, date, and the passage you're quoting. Not decoration: a reviewer who can't point to a page hasn't read the book.
• Compare — place the work alongside others. How does Wuthering Heights sit next to Jane Eyre, published a year earlier by the same family?
• Contrast — where does it break with its own period or with its imitators?
• Critique — the part everyone skips. Commit to a judgment about what works and what doesn't.
• Connect — why should a reader today spend two weeks on it instead of anything else.

Note the imbalance: four of those five are about argument, and only one is about identifying the book. That ratio is roughly right. If your draft spends more words on who wrote what and when than on whether it works, you've written a catalogue entry.

How I actually use the framework

I don't march through the C's in order. I use them as a checklist to catch gaps after a first draft. My early reviews — and I say this with some embarrassment — were almost pure cite and compare with a single paragraph of critique bolted on at the end, like a salad served after dessert. Running the list afterwards showed me every time that the critique section was the shortest. It should usually be the longest.

What is the 50 page rule?

The 50 page rule is a practical guideline: give a book roughly fifty pages before deciding whether it's worth continuing. Fifty pages is past the setup, past the first impression, and usually far enough in to feel whether the author's voice and pace will sustain you.

It's a reading rule, not a law, and reviewers quote it loosely — some interpretations apply it to novels, some to any long book. What matters for your review is that it's a fair test to invoke. If you're going to criticise a classic for being slow, be honest about whether you gave it those fifty pages. Two chapters in, Moby-Dick looks like a mistake. A hundred pages in, it's a completely different animal.

And the reverse holds. If you abandoned a book at page thirty and you're reviewing it anyway, say so in the text. Readers forgive a partial reading; they don't forgive a concealed one, and the gaps always show in the specificity of the evidence.

The criteria I actually grade a classic against

Vague praise ("richly drawn characters," "timeless themes") is the sound of a reviewer with no criteria. Here's the grid I use, and I'd rather show it than describe it:

Criterion	What I'm asking	Where it shows up in the review
Prose and translation	Does the sentence-level writing reward attention, in this edition?	A quoted passage with a line of analysis
Structure and pace	Is the architecture deliberate, or does it sag in the middle third?	A named structural problem, with page range
Thematic depth	Does it say something the plot alone couldn't?	One theme traced through two scenes
Historical position	What was it doing that its contemporaries weren't?	A comparison, not a context dump
Relevance now	What lands in 2026, and what reads as period furniture?	Your honest judgment — both directions

Two or three of these rows will carry most of your review. Don't try to give all five equal weight; that produces the flat, evenly-distributed paragraphs nobody finishes. I'd argue prose and structure deserve the most space in a classic review, because that's the part a reader cannot get from a summary.

Handling the era question without hedging

The trickiest judgment with an old book is how much to blame it for the assumptions of its time. My position, which I'll defend: judge a book primarily by what it was doing inside its own moment, then state plainly how it reads outside it. Two moves, not one compromise.

So a sentence like "the novel's treatment of its female characters is a product of its decade, and it also makes the final chapter hard to take seriously" does the work. It's not defensive and it's not anachronistic. What doesn't work is the waffling middle: "while some modern readers may find certain aspects problematic, others appreciate…" That sentence says nothing and everyone knows it.

What is an example of a good book review?

Rather than point you at a publication, here's a skeleton of a review that would actually work — for a hypothetical but typical nineteenth-century novel, so you can see the proportions:

1. Open with a specific claim, not a summary. "The novel's reputation rests on its final chapter, which is also the weakest thing in it." Now the reader has something to disagree with and will read on to do so.
2. One short paragraph of orientation — the book, the author, the year, the edition you read. Three or four sentences maximum.
3. The argument, in two sections. Each built on a named scene and a quoted line. This is where your review earns its existence.
4. The counterargument, honestly stated. The strongest case against your reading, then why you still hold yours.
5. A judgment. Who should read it, who should skip it, and — for a classic — whether the reputation holds.

Notice what's missing: an exhaustive plot retelling. In a review of a new thriller, the plot is the point. In a classic, the plot is the least interesting thing you can hand your reader. Two sentences of summary go a long way.

A short annotated extract

Here's the difference at sentence level, which matters more than structure. Weak: "The novel explores themes of isolation and society through its protagonist's struggles." Strong: "Isolation is the engine, not the theme — the protagonist's decision in chapter twelve to refuse the visitor is the moment the book stops being about loneliness and starts being about pride."

The second version names a chapter, names an action, and makes a claim you could argue with. That's all a review needs to be: arguable, specific, anchored in the text.

The practical business: edition, length, and spoilers

Three small decisions that quietly determine whether your review is worth reading.

Name your edition. I once spent a fortnight convinced a Victorian novel was clumsy and repetitive, only to discover I'd been reading a heavily abridged reissue with an editorial introduction that had been cut into the text. I rewrote the whole piece. For translated works, the translator's name goes in the first paragraph, always — a 1950s translation and a 2010s one can read like different novels.

Match length to your purpose. If you're writing for a course, follow the brief exactly; a 900-word assignment and a 400-word blog post need different proportions, not the same text with paragraphs shaved off. If you're writing for yourself, 600 to 900 words is a comfortable range for a single classic — enough room for an argument, not enough room to hide.

Stop worrying about spoilers. Reviews of classics routinely tiptoe around century-old endings, and it's a waste of words. Your reader already knows the ending. Discuss it openly, and spend the freed space on why the ending works or doesn't.

The one rule I'd keep if I had to throw out the rest

Make an argument you can lose.

Everything above — the 5 C's, the fifty-page test, the criteria table, the edition notes — is scaffolding around that single instruction. A review of a classic lives or dies on whether it gives the reader a proposition to accept or resist. The moment your draft becomes safe enough that nobody could disagree with it, you've stopped reviewing and started summarising.

Which is why I still keep that student's Jane Eyre draft in a folder. It's a perfect specimen of the failure mode: beautiful, correct, and completely without a stake. The rewrite she produced after we talked was rougher, had one sentence that ran to nearly fifty words, and argued — on the evidence of two scenes — that the novel's ending is a surrender rather than a resolution. I don't fully agree with her. That's exactly why I read it to the end.