Readability Score

← Back to glossary · Category: Content

What a Readability Score Means, in Plain Language

A readability score is a number that estimates how easy or hard a piece of writing is to read, based on measurable features of the text itself, most often sentence length and word length. The best-known score, the Flesch Reading Ease score, runs from zero to one hundred, with higher numbers meaning easier reading: a score in the sixties and seventies is usually described as plain English for a general audience, while a score below thirty describes dense academic or legal prose. The score does not judge whether the writing is good, true, or interesting. It judges only how much effort the surface of the text demands from a reader, and that narrow judgment is both its value and its limit.

The Flesch formula behind the score is public and simple to state. It starts from a baseline of 206.835, subtracts a little more than the average number of words per sentence, and subtracts a much larger amount for the average number of syllables per word. Long sentences pull the score down, because each additional word adds to the load a reader must hold in mind before the sentence resolves. Long, multi-syllable words pull it down further, because they take longer to recognise and often signal specialist vocabulary. A text of short sentences built from short, familiar words will therefore score high, while a text of long sentences built from long, abstract words will score low, whatever its subject.

That simplicity is why the score is useful, and why it must not be over-read. A score can be computed automatically, in seconds, for any draft, which makes it a practical check during editing: a writer can compare two versions of the same paragraph and see, objectively, which one is easier to read. But the score knows nothing about whether the ideas are ordered well, whether the examples are apt, whether the tone suits the reader, or whether the facts are right. A text can score highly and still be confusing, because it uses simple words to express a muddled idea, and a text can score low and still be exactly right, because its readers are specialists who need precise terminology. The score is a surface measurement, and surface measurements guide revision; they do not replace judgment.

What a Readability Score Is Not

A readability score is not a grade for the writer, and it is not a target to hit at any cost. Aiming for a particular number by chopping every sentence short and replacing every long word with a short one can produce text that reads like a list of slogans: easy to score, hard to follow, because the connections between ideas have been cut away with the long sentences. Good readable writing keeps its connections, using short sentences where the idea is simple and longer ones where the idea needs its clauses, and choosing familiar words where they exist without banishing a necessary technical term. The score should prompt a writer to ask why a passage scores low, not command them to raise it by any means.

How a Readability Score Works

Every readability formula follows the same logic, even when its arithmetic differs: it counts something countable in the text, and it treats that count as a proxy for reading effort. Flesch Reading Ease counts words per sentence and syllables per word. Flesch-Kincaid Grade Level uses the same two counts with different weights to produce a grade. The Gunning Fog Index counts the share of words with three or more syllables, together with sentence length. The Automated Readability Index counts characters per word instead of syllables, which makes it easier to compute by machine. In each case, the formula was calibrated against passages whose difficulty had been tested on real readers, so the number is an estimate grounded in reading research, not an arbitrary invention.

The estimate works because sentence length and word length genuinely correlate with reading difficulty, but correlation is not the whole story. A short sentence can still be hard if it uses an unfamiliar concept, and a long sentence can still be easy if it is well punctuated and its clauses follow a familiar pattern. Familiarity matters as much as length: a short specialist word that the reader has never met is harder than a longer everyday word they know well. Formulas cannot see familiarity, context, layout, or the reader's background, so they miss exactly the things that make a particular text easy for a particular reader. That is why the score is best used as a first check, followed by reading the passage aloud and, where possible, testing it on a real reader.

Why a Readability Score Matters

A readability score matters because most readers do not finish what they cannot easily read. A blog reader arrives with a question, not with a commitment to struggle through dense prose, and a page that demands too much effort for its reward will lose that reader to another result, however accurate its information. The score gives a writer an early warning of that risk, before publication, when revision is still cheap. It is not the only warning, and it is not the most important one, but it is the one that can be checked in seconds, and a check that is easy to run is a check that actually gets run.

It matters also because it protects the writer from their own expertise. A person who knows a subject well tends to write in the subject's specialist language, to pack several qualifications into one sentence, and to assume background the reader may not have. That drift is invisible to the writer, because the specialist language feels natural to them, but it is immediately visible to a reader who lacks the background. A readability score makes the drift visible to the writer too, by showing that a passage they found clear scores as difficult. The score is, in that sense, a stand-in for the reader the writer cannot see, and a useful corrective to the curse of knowing too much.

Common Readability Score Mistakes

The first mistake is chasing a number instead of clarity. A writer who shortens every sentence and replaces every long word, regardless of meaning, will raise the score while damaging the writing, because the connections between ideas, the precision of terms, and the rhythm that carries a reader through a paragraph all suffer. The fix is to treat a low score as a question, not a verdict: read the passage, find the sentence or term that is doing the damage, and decide whether that sentence can be split, that term can be explained, or that passage genuinely needs its complexity. Sometimes the answer is that it does, and the score should be left alone.

The third mistake is trusting the score without reading the text. A passage can score well and still be confusing, because it uses simple words in a muddled order, because it omits a necessary step, or because its examples do not match its claims. A passage can score poorly and still be clear, because its long words are familiar to its readers and its long sentences are well built. The fix is always the same: after checking the number, read the passage aloud, slowly, and ask whether a reader who knows no more than the intended audience would follow it. If the answer is no, revise, whatever the number says. If the answer is yes, publish, whatever the number says.

How to Apply Readability Thinking Step by Step

Start by naming the reader before writing, in one sentence: who they are, what they already know, and what they need from the page. That sentence, not a score target, is the real standard the draft will be judged against. A guide for small business owners who are new to blogging needs everyday language and worked examples; a reference for experienced practitioners can use specialist terms, provided each term is used consistently and explained at first use. Write the reader sentence at the top of the draft, where it can be seen while writing, and return to it whenever a passage feels hard to write, because difficulty in writing often signals a passage whose reader has not yet been decided.

Next, draft freely, without watching any score. A first draft written under the eye of a readability checker tends to become timid, short-sentenced, and thin, because the writer edits for the number instead of for the idea. The score belongs to the revision stage, not the drafting stage, and a draft that says something worth saying in imperfect language is a better starting point than a draft that says little in perfectly scored language. Write the idea first, in full, and let the revision stage worry about how easily it can be read.

Then run the score on the draft, and use it to find passages to look at, not passages to condemn. Read the lowest-scoring sections slowly, and ask, for each, what is making it hard: a sentence that carries three ideas, a term the reader may not know, a paragraph with no example, or a chain of qualifications that buries the main point. Each cause has its own fix: split the sentence, explain the term, add the example, or move the qualifications to a later sentence. The entry on heading structure helps here too, because a well-structured page lets a reader navigate by headings even when a section is necessarily detailed, and the entry on title tag shows how the same clarity applies to the shortest text a page contains.

After that, revise for structure as well as for sentences. Shortening sentences helps, but breaking a long passage into headed sections, adding a list where the reader must follow steps, and giving each paragraph one main idea helps more, and none of those improvements is fully captured by a readability score. A page that is well structured can carry a lower score without losing its readers, because the reader can find the part they need and skip the part they do not. Structure and readability are partners: the score measures the surface of the sentences, while the headings measure the shape of the whole page.

Now read the revised draft aloud, from start to finish, and mark every place where you stumble, pause to re-read, or lose the thread. Those stumbles are the passages a reader will stumble on too, whatever the score says, and they are the most reliable readability test a writer has. Fix the stumbles by rewriting, not by tweaking words to game the formula: a passage that reads smoothly aloud will usually score reasonably, and a passage that scores well but stumbles aloud has been gamed, not improved. If a real reader from the intended audience is available, ask them to read it too, and listen to where they pause, because their pauses are data the formula cannot provide.

How Rankenza Handles Readability Scores

Rankenza's articles are written to be read by the small business owners and general readers they serve, not by specialists showing off specialist language. Each article starts from research into the top ten search results for its keyword, filtered by what the searcher actually wants, so the article's level follows from the reader's need rather than from a formula target. The draft is written in original words, reviewed by a human editor who reads it as a reader would, and given internal links from the customer's own sitemap, so that a reader who needs more depth can find it, and a reader who needs only the basics is not forced through it. The human review is the safeguard that a score alone cannot provide: it catches the muddled simple passage and the clear complex passage alike.

Rankenza does not promise a particular readability score, because the right score depends on the article's audience, and a promise of one number for every topic would be a promise to write badly for some of them. What it does offer is a low-risk way to judge the writing for yourself: the first article is free, then $3.60 per article or $89 for 50 credits, with no subscription. A small business can read the draft, check it against its own readers, and decide on evidence whether the level is right. The SEO Keyword Generator is a free starting point for finding topics whose readers' needs are clear enough to write for plainly.

For how readability fits a whole article, see writing blog posts that rank on Google.

How This Looks on Rankenza

The comparison below is method against method, without inventing traffic or ranking figures for either side.

Sources: What the Research Says

According to ReadabilityFormulas.com, Rudolph Flesch developed the Reading Ease formula in 1948, and it rates a text on a scale from zero to one hundred, with higher scores meaning easier reading, using average sentence length and average syllables per word. The Kansas State University plain language guide gives the same formula and the same interpretation, noting that most standard documents for the general public should aim for a score of approximately sixty to seventy. The plain language guidance carried by Digital.gov, adapted from PlainLanguage.gov, describes plain language as content that is clear and easy to understand, written for a specific audience, which is the purpose a readability score serves. Where this guide gives no other figure, that is deliberate: these sources describe a method and a range, not a single number that fits every audience.

• ReadabilityFormulas.com: The Flesch Reading Ease Formula
• Kansas State University: Principles and Practice of Plain Language Protocols
• PlainLanguage.gov: A Plain English Handbook
• Google Search Central: SEO Starter Guide

Frequently Asked Questions

What readability score should a blog aim for?

It depends on the audience, not on a universal rule. For a general audience, the Flesch Reading Ease range of roughly sixty to seventy is often described as plain English, and it is a reasonable starting orientation for a small business blog. For a specialist audience, a lower score may be exactly right, because the readers need precise terms and detailed reasoning. The useful question is not what number to hit, but who will read the page and what they already know; the score is a check on that judgment, not a replacement for it.

Does a readability score affect search ranking directly?

Not as a direct, published ranking factor. Search engines do not announce that a page ranks because its Flesch score is a particular number. Readability helps indirectly, because a page that is easy to read is easier to understand, easier to stay with, and easier to trust, and those qualities support the helpful, people-first content that search guidance rewards. A writer who chases a score for ranking reasons, rather than for readers' sake, is likely to damage the writing while gaining nothing measurable in search.

Should I remove long words to raise my score?

Only when a shorter, familiar word says the same thing without losing precision. A necessary technical term should be kept and explained at first use, not replaced with a vague short word that misleads the reader. A long word that is familiar to the audience, or that is the correct name for the thing being discussed, is not a problem to be fixed. The score should prompt a writer to explain terms and split overloaded sentences, not to banish every word over two syllables.

Can a passage score well and still be hard to read?

Yes, easily. Simple words in a muddled order, a missing step, an example that does not match the claim, or a paragraph with no clear main idea can all produce a high score and a confused reader. The formula counts sentence length and syllables; it cannot see order, logic, examples, or the reader's background. That is why reading the draft aloud, and testing it on a real reader where possible, remains the most reliable readability check, with the score as a useful first pass rather than a final verdict.