What Is Readability Score? Flesch Reading Ease Explained
You can write something technically correct that's still hard to get through. A readability score is an attempt to estimate how easy or difficult a piece of text is for a reader to process — not whether the writing is good, and not whether it's right.
That distinction matters more than it sounds. A children's story should generally be very easy to read. A legal document may naturally score lower, because precision matters more than simplicity. Technical documentation often uses complex terminology even when it's well written for its actual audience. A readability score only means something once you interpret it against who the text is actually for.
What Is a Readability Score?
Readability, in this context, is a measure of how much effort a piece of text demands from a reader — mainly driven by how long the sentences are and how complex the words are. A readability score is a number produced by a formula that estimates that effort from the text itself, without knowing anything about the reader.
Two things a readability score does not measure: whether the content is factually accurate, and whether it's well-argued or well-organized. A short, simple sentence can still be wrong. A long, complex one can still be exactly what a specialist audience needs.
Compare these two:
Difficult: "The implementation of the authentication mechanism requires the utilization of cryptographic verification procedures."
Simpler: "Authentication uses cryptographic checks to verify a user."
The second version is easier to process for two concrete reasons: it's shorter, and it replaces inflated phrasing ("the utilization of") with plainer wording ("uses"). Neither version is more or less true than the other — the difference is entirely in how much work the sentence asks the reader to do.
What Is the Flesch Reading Ease Score?
Flesch Reading Ease is the most commonly cited readability formula. It produces a score generally ranging from 0 to 100, where a higher number means the text is easier to read. It's calculated as:
Flesch Reading Ease =
206.835
− (1.015 × Average Sentence Length)
− (84.6 × Average Syllables Per Word)The two inputs it needs:
- Average Sentence Length — total words divided by total sentences.
- Average Syllables Per Word — total syllables divided by total words.
The formula is really just penalizing two things: longer sentences, and words with more syllables. Both increase the subtracted amount, which pulls the score down.
Flesch Reading Ease Score Table
| Score | General interpretation |
|---|---|
| 90–100 | Very Easy |
| 80–89 | Easy |
| 70–79 | Fairly Easy |
| 60–69 | Standard |
| 50–59 | Fairly Difficult |
| 30–49 | Difficult |
| 0–29 | Very Confusing |
Treat these as general reference points, not universal rules. A "Standard" score isn't automatically the right target for every piece of writing — a technical explainer, an academic paper, or a legal notice can score lower than this table's middle range and still be exactly appropriate for its actual audience.
What Is Flesch-Kincaid Grade Level?
Flesch-Kincaid Grade Level is a second, related formula, calculated from the same two inputs:
Flesch-Kincaid Grade Level =
(0.39 × Average Sentence Length)
+ (11.8 × Average Syllables Per Word)
− 15.59The difference is what the output represents. Flesch Reading Ease gives you a 0–100 score. Flesch-Kincaid Grade Level gives you an estimated U.S. school grade level — a result of roughly 8 suggests text that reads at around an eighth-grade level. They're built from the same underlying measurements and tend to move together, but they answer slightly different questions: "how easy is this, on a 0–100 scale" versus "what grade level does this read at."
How Is Readability Calculated?
Step 1 — count words. Say a piece of text has 100 words.
Step 2 — count sentences. Say it has 5 sentences. Average sentence length is 100 ÷ 5 = 20 words.
Step 3 — estimate syllables. This is the part readability formulas need that isn't a simple count. Software estimates syllables algorithmically — typically by counting vowel groups in each word, with adjustments for common patterns like a silent trailing "e." It's an estimate, not a dictionary lookup, so it can be slightly off for unusual words, but it's consistent enough to be useful across a whole document.
Step 4 — apply the formula. Plug average sentence length and average syllables per word into the Flesch Reading Ease formula above, and the result is the score.
Example: Comparing Two Pieces of Writing
Here's a short passage rewritten two ways — both run through the actual Flesch Reading Ease and Flesch-Kincaid formulas, not estimated:
Version A: "Our application facilitates the utilization of automated mechanisms for the verification of user authentication credentials. This process is initiated whenever a user attempts to gain access to a restricted resource. The system subsequently performs a comparison between the submitted credentials and the previously stored values."
Version B: "Our application automatically verifies user login credentials. This happens whenever a user tries to access a restricted resource. The system then compares the submitted credentials with the stored values."
| Words | Avg. words/sentence | Flesch Reading Ease | Flesch-Kincaid Grade | |
|---|---|---|---|---|
| Version A | 45 | 15.0 | 9 (Very Confusing) | 15.7 |
| Version B | 29 | 9.7 | 31 (Difficult) | 11.4 |
Version B uses about a third fewer words, shorter sentences, and simpler phrasing, and its Flesch score moves up a full category as a result. Notice, though, that Version B still lands in "Difficult," not "Easy" — words like "credentials," "automatically," and "verifies" are still multi-syllable, and no amount of sentence-shortening turns them into one-syllable words. That's a fair illustration of a real limit: simplifying structure helps, but vocabulary tied to the subject matter has its own floor.
Also worth being direct about: a higher score here doesn't mean Version B is more accurate or more appropriate for every context — only that it demands less effort to read. If this were a precise technical spec where "facilitates the utilization of automated mechanisms" was intentionally exact, that would be a legitimate reason to keep more of Version A's structure despite the lower score.
What Is a Good Readability Score?
There isn't one target number that applies everywhere. What counts as appropriate depends heavily on the content type:
- General consumer content — an easier-to-read score is usually a genuine advantage, since the audience is broad and often skimming.
- Technical documentation — a lower score can be completely reasonable if the underlying concepts require precise, technical vocabulary.
- Academic content — complex terminology is often unavoidable and expected by the audience reading it.
- Legal content — precision matters more than simplicity; rewriting for a higher score can introduce ambiguity that isn't acceptable in that context.
- Children's content — much easier readability is usually the actual goal.
The underlying principle: choose a target readability based on your actual audience, not an arbitrary number pulled from a table.
How to Improve Readability
1. Shorten unnecessarily long sentences.
Instead of: "Because the system performs several validation procedures before allowing the request to continue, users may experience a delay when submitting the form."
Try: "The system performs several validation checks before submitting the form. This may cause a short delay."
2. Use simpler words where they say the same thing. "Utilize" → "use." "Approximately" → "about." This isn't about dumbing content down — it's about not adding syllables that don't add meaning.
3. Break up large paragraphs. A wall of text is harder to enter into, regardless of the words inside it.
4. Use headings. They let a reader scan the structure of a piece before committing to reading all of it.
5. Use lists for steps, features, requirements, examples, or options — anything that's naturally a set of discrete items reads better as one.
6. Prefer active voice when it improves clarity. "The system generated the report" is more direct than "The report was generated by the system." This isn't an absolute grammar rule — passive voice is sometimes the clearer or more appropriate choice — just a habit worth noticing when a sentence feels needlessly roundabout.
7. Remove filler that doesn't add meaning. "In order to" can almost always just be "to."
Readability Score vs Word Count
These measure different things. Word count tells you how much text exists. A readability score estimates how much effort that text takes to read. A 1,000-word article, written clearly, can be genuinely easier to read than a poorly structured 500-word one — length and difficulty aren't the same axis. If you're tracking both side by side, Kravoy's Word Counter gives you word count, character count, and reading time alongside a readability score, so you can see how they move independently rather than assuming a shorter piece is automatically an easier one.
Readability and SEO
Easier-to-read content can genuinely improve the experience for readers — it's easier to scan, easier to finish, and easier to act on. That's a real, direct benefit on its own terms. What it isn't is a guaranteed search ranking factor: getting a specific readability score is not something that, by itself, moves you up in Google's results. Treat readability as something you improve because it makes your writing better for the people reading it, not as a lever with a known, guaranteed SEO payoff. If you're also working on how a page's title and description appear in search results specifically, that's a related but separate concern covered in our guide to writing SEO-friendly meta titles and descriptions.
How to Check Your Readability Score
You don't need to compute any of these formulas by hand. Kravoy's Readability Score Checker runs your text through five formulas at once — Flesch Reading Ease, Flesch-Kincaid Grade Level, Gunning Fog, SMOG, and the Automated Readability Index — and highlights the specific sentences that are dragging the score down, so you know exactly what to revise rather than just seeing a single number. You can also check the result against a target audience preset (general public, high school, academic) to see whether your text roughly fits what you're aiming for.
Common Readability Mistakes
- Chasing a specific score. Don't rewrite genuinely good technical content just to move a number, especially if the audience already expects that level of detail.
- Making everything extremely simple. Some concepts require technical vocabulary to be precise — oversimplifying can cost accuracy.
- Confusing readability with correctness. A simple, easy-to-read sentence can still be factually wrong.
- Ignoring the target audience. A developer tutorial and a children's story shouldn't be written to the same readability target.
- Looking only at the score. Use it as one signal, then actually read the flagged sentences and judge for yourself whether they need changing.
Quick Readability Checklist
- Are any sentences unnecessarily long?
- Are paragraphs short enough to scan easily?
- Are headings descriptive, not just decorative?
- Can any complicated wording be simplified without losing meaning?
- Are technical terms explained where the audience might need it?
- Are lists used where the content is naturally a set of items?
- Is active voice used where it genuinely improves clarity?
- Does the writing style match the intended audience?
- Have you checked the readability score?
- Did you manually review the flagged sentences instead of just reacting to the number?
Frequently Asked Questions
What is a readability score?
A number, produced by a formula based mainly on sentence length and word complexity, that estimates how much effort a piece of text takes to read. It doesn't measure accuracy or overall writing quality.
What is a good Flesch Reading Ease score?
It depends on your audience. General consumer content often aims for a higher, easier-to-read score, while technical, academic, or legal writing can reasonably score lower. There's no single number that's correct for every type of content.
Is a higher readability score always better?
No. A higher score means the text is easier to process, not that it's more accurate, more appropriate, or better written. For specialist audiences, a lower score can be entirely correct.
How is Flesch Reading Ease calculated?
From two inputs: average sentence length (words ÷ sentences) and average syllables per word (syllables ÷ words), combined as 206.835 − (1.015 × average sentence length) − (84.6 × average syllables per word).
What is the difference between Flesch Reading Ease and Flesch-Kincaid Grade Level?
Both use the same two underlying measurements, but Flesch Reading Ease outputs a 0–100 score (higher is easier), while Flesch-Kincaid Grade Level outputs an estimated U.S. school grade level.
Does readability affect SEO?
It can improve the reader's experience — easier content is easier to scan and act on — but a specific readability score is not a guaranteed search ranking factor on its own.
How can I improve my readability score?
Shorten overly long sentences, replace inflated phrasing with plainer words, break up large paragraphs, use headings and lists where they fit naturally, and remove filler phrases that don't add meaning.