What Are Readability Scores, and Why Do They Matter?

A "readability score" sounds like it should measure whether a piece of writing is good — but it doesn't, and treating it as if it does is the single most common misunderstanding about these formulas. What it actually measures is much narrower and much more mechanical: how easy a passage is to parse based on how long its sentences and words tend to be. That narrower definition is still genuinely useful, especially for plain-language writing, technical documentation, and anything meant to be understood quickly by a broad audience — but it's worth understanding exactly what the formula counts, and just as importantly, what it doesn't, before leaning on a score too heavily.

What a readability score actually measures

Nearly every widely-used readability formula, including the one this guide walks through in detail, is built from just two structural signals: how many words are packed into the average sentence, and how structurally complex the average word is (approximated by syllable count). Neither signal has anything to do with whether the content is accurate, whether the argument makes sense, or whether the writing is interesting to read — a readability formula has no way to detect any of that. It measures processing difficulty at the sentence and word level, which is a real and useful thing to measure, but it is a narrower claim than "quality," and conflating the two is where readability scores get misused most often.

The Flesch Reading Ease formula

The most widely used readability formula, developed by Rudolf Flesch, produces a score generally between 0 and 100 from three simple counts — total words, total sentences, and total syllables in a passage:

\[ \text{Score} = 206.835 - 1.015 \times \left(\frac{\text{total words}}{\text{total sentences}}\right) - 84.6 \times \left(\frac{\text{total syllables}}{\text{total words}}\right) \]

The two fractions inside the formula are exactly the two structural signals described above: words per sentence (a proxy for sentence length) and syllables per word (a proxy for word complexity). Higher values of either one pull the score down, which matches the intuition that longer sentences and longer words both make text harder to read.

A full worked example

Take this short two-sentence passage:

"The cat sat on the mat. It was warm and sunny outside, so the cat decided to take a long nap in the afternoon sun."

Counting carefully, sentence by sentence:

Sentence	Words	Syllables
"The cat sat on the mat."	6	6
"It was warm and sunny outside, so the cat decided to take a long nap in the afternoon sun."	19	25
Total	25	31

With 2 sentences, 25 words, and 31 syllables total:

Words per sentence = 25 ÷ 2 = 12.5
Syllables per word = 31 ÷ 25 = 1.24

Plugging into the formula:

206.835 − (1.015 × 12.5) − (84.6 × 1.24)
= 206.835 − 12.6875 − 104.904
= 89.2

A score of 89.2 falls right at the boundary of the "very easy" band described below — which lines up with intuition, since the passage uses short, everyday words and moderate-length sentences with no technical vocabulary at all.

What the score ranges mean

Flesch Reading Ease scores are commonly interpreted against bands like these, widely cited across style guides and writing tools:

Score	Reading level	Description
90–100	5th grade	Very easy to read
60–70	8th–9th grade	Plain English, easily understood
30–50	College level	Difficult, best suited to an educated audience
0–30	Graduate level	Very difficult, dense technical or academic text

These bands are the standard, commonly-cited interpretation of the score rather than a strict scientific classification — a score of exactly 55, for instance, sits between the labeled bands and is reasonably read as "fairly difficult," roughly high-school to early-college level. The bands are a useful map for interpreting a score at a glance, not a rigid boundary.

The Flesch-Kincaid Grade Level formula

A closely related formula, derived from the same underlying word-count and syllable-count inputs, outputs a US school grade level directly instead of a 0–100 score:

\[ \text{Grade level} = 0.39 \times \left(\frac{\text{total words}}{\text{total sentences}}\right) + 11.8 \times \left(\frac{\text{total syllables}}{\text{total words}}\right) - 15.59 \]

Using the exact same passage and counts as above (words per sentence = 12.5, syllables per word = 1.24):

(0.39 × 12.5) + (11.8 × 1.24) − 15.59
= 4.875 + 14.632 − 15.59
= 3.9

A grade level of roughly 3.9 means the passage is estimated to be readable by a student in the ninth month of 3rd/4th grade — consistent with the very easy 89.2 Flesch Reading Ease score calculated for the same passage, since the two formulas share the same underlying inputs and simply present the result on a different scale. The grade-level version is used particularly heavily in technical writing, legal plain-language initiatives, and government content standards, because "this document tests at an 8th-grade reading level" is a more directly actionable statement for a policy or style guide than a 0–100 score would be — it maps straight onto a familiar, concrete benchmark.

Writing tips that genuinely improve readability scores

Because the formulas are built entirely from sentence length and word/syllable complexity, the changes that actually move a readability score are concrete and provable — not vague "write more clearly" advice:

Shorten sentences

Before: Although the meeting was originally scheduled for Tuesday, it was moved to
Wednesday because several key stakeholders, including the regional director and the
finance lead, were unable to attend due to scheduling conflicts that arose earlier in
the week.

After: The meeting moved to Wednesday. Several key stakeholders could not attend on
Tuesday because of scheduling conflicts.

Splitting one long sentence into two shorter ones directly lowers the "words per sentence" term in both formulas, which is the single highest-leverage lever in either equation.

Use simpler, more common words

Before: We must utilize a methodology that facilitates the expeditious resolution of
customer inquiries.

After: We need a way to answer customer questions faster.

Replacing multi-syllable words ("utilize," "methodology," "facilitates," "expeditious") with shorter, more common equivalents directly lowers the "syllables per word" term, since each swapped word contributes fewer syllables to the total.

Prefer active voice

Before: The report was reviewed by the manager before it was submitted to the board.

After: The manager reviewed the report before submitting it to the board.

Active voice doesn't just read more directly — it also tends to shorten sentences by removing extra helper words ("was... by"), which again reduces the words-per-sentence term that both formulas penalize.

Break up long paragraphs

A wall of unbroken text doesn't directly appear anywhere in the Flesch formula itself (which only counts words, sentences, and syllables), but long paragraphs are strongly correlated with long, run-on sentences in practice, and breaking a dense paragraph into several shorter ones with a clear point each tends to force shorter sentences along with it — improving both the measured score and, just as importantly, the actual reading experience.

Honest limitations of readability formulas

None of this should be read as "a high readability score means good writing." The Flesch formulas — and every formula like them — are blind to several things that matter just as much as sentence and word length:

• Accuracy. A completely false or misleading sentence can score extremely easy to read; the formula only measures structure, never truth.
• Organization. A passage made of short, simple sentences presented in a confusing or poorly ordered sequence can score "easy" while still leaving a reader lost, because the formula has no concept of logical flow or structure between sentences.
• Engagement. Whether a piece of writing is actually interesting, persuasive, or enjoyable to read is a completely separate quality from its structural readability, and a technically "easy" passage can still be dull, and a more complex one can still be gripping.
• Domain-appropriate complexity. Some technical or legal content genuinely needs precise, complex language to remain accurate — artificially simplifying it purely to chase a higher score can actually make it less correct or less useful for its intended, specialist audience.

The practical takeaway is to treat a readability score as one useful, objective signal about sentence and word complexity — genuinely worth checking, especially for general-audience or plain-language writing — rather than a complete verdict on whether a piece of writing succeeds.

Frequently asked questions

What's a "good" readability score for a general website or blog?

Content aimed at a broad general audience commonly targets somewhere in the 60–70 Flesch Reading Ease range — plain, everyday English understandable without specialist background — though the right target genuinely depends on the audience; a piece for industry specialists can reasonably score lower without being poorly written.

Can two completely different sentences get the identical readability score?

Yes, easily — since the formula only counts word count, sentence count, and syllable count, any two passages with matching values for those three counts produce an identical score regardless of what the words actually say or how well-organized the ideas are.

Does adding more punctuation, like semicolons, affect the score?

Not directly — the Flesch formulas count sentences (typically delimited by terminal punctuation like periods, question marks, and exclamation points), words, and syllables, not punctuation marks themselves. However, using a semicolon to join two independent clauses into one longer sentence does affect the sentence count and therefore the score, even though the semicolon itself isn't directly counted.

Is a very high readability score always the goal?

No — the right target depends entirely on the intended audience and purpose. A children's reading passage benefits from chasing a very high score; a legal contract or academic paper has different, sometimes competing priorities (precision, established terminology) where artificially maximizing readability could come at the cost of accuracy.

Check your own writing

DocNectar's Readability Checker runs the Flesch Reading Ease and Flesch-Kincaid Grade Level formulas (among others) on any passage you paste in, and the Word Counter gives the underlying word, sentence, and character counts these formulas are built from — useful for understanding exactly why a passage scored the way it did.