Readability Fixes: Making Every Page Easier to Read
People rarely read a web page from top to bottom. They scan for the part they need, and if the text makes that hard, they leave. The Readability Checker measures how much effort your writing asks of the reader.
It calculates Flesch Reading Ease, Flesch-Kincaid Grade Level and Gunning Fog, average sentence length, the share of passive sentences, paragraph length and jargon density, and it flags the sentences causing trouble with suggestions. This page explains what each measure really tells you, where the formulas fall short, and which guide fixes each finding.
What the scores measure
Readability formulas are older than the web. They were designed to estimate how hard a printed text is, using things a machine can count: words per sentence and syllables or long words per word. They do not understand meaning, but across a whole page they are a useful early warning.
| Measure | Built from | How to read it |
|---|---|---|
| Flesch Reading Ease | Average sentence length and average syllables per word | Higher is easier. Scores around 60 to 70 are usually described as plain English; below 30 is very hard going. |
| Flesch-Kincaid Grade Level | The same two inputs, weighted differently | Lower is easier. The number is a US school grade; add about five to get an approximate reading age. |
| Gunning Fog | Sentence length and the share of words with three or more syllables | Lower is easier. It is harsher on long words than Flesch. |
| Average sentence length | Words divided by sentences | A simple, reliable signal. Plain English guidance commonly suggests an average of about 15 to 20 words. |
| Passive voice share | Sentences built as "was done by" | Some passive is fine; a high share makes writing vague about who does what. |
| Paragraph length | Sentences per paragraph | Long blocks are hard to scan on a phone screen. |
| Jargon density | Words from lists of corporate or technical terms | A prompt to check whether your readers know those words. |
For reference, the Flesch Reading Ease formula is 206.835 − 1.015 × (words ÷ sentences) − 84.6 × (syllables ÷ words).
Both levers are visible in it: shorter sentences and shorter words raise the score. That is also its
weakness. A page of short, common words can still be muddled, and a precise technical term can be the
clearest word available.
The fix guides, from sentence to page
Each guide takes one finding, shows why it slows readers down, gives before and after rewrites and explains when the rule can be broken.
Sentence level
Fixing sentences over 20 words covers splitting sentences that pile up clauses: turning commas into full stops, breaking at "and" or "but", and giving a subordinate idea its own sentence, while keeping some variety for rhythm. Fixing excessive passive voice covers rewriting "the invoice was sent by our team" as "our team sent the invoice", and the cases where passive is the right choice because the actor is unknown or unimportant. Fixing weak or missing transitions covers linking words such as "however", "as a result" and "for example" that show how one idea leads to the next.
Word level
Fixing jargon and corporate-speak covers swapping inflated words for plain ones, such as "use" for "leverage", when an industry term is justified, and defining the terms you keep. Fixing a low Flesch Reading Ease score covers the two levers behind the score and how to choose a sensible target for your audience. Fixing a high reading grade level covers bringing the grade down without talking down to readers.
Page level
Fixing paragraphs over four sentences covers one idea per paragraph and leading with the point. Fixing vague or missing subheadings covers descriptive headings that start with the topic word, placed often enough that readers can scan to the part they need.
By type of content
Readability in blog posts and articles covers structure for skim-reading, from the opening conclusion to lists and headings. Readability in technical documentation covers defining terms on first use, numbered steps, code blocks and one task per page. Readability in product pages covers short, benefit-led copy with specifications in lists rather than paragraphs.
Which findings to fix first
A readability report can list dozens of sentences. Working through them in page order is slow. These priorities get the biggest improvement for the least rewriting.
- The top of the page. The opening paragraph and first heading decide whether people stay. Rewrite them first on your most visited pages.
- Very long sentences. A handful of 40 or 50 word sentences drag down the whole score and are the ones readers actually give up on. Splitting them is quick.
- Walls of text. Breaking long paragraphs and adding descriptive subheadings changes how a page feels on a phone more than any word swap.
- Jargon your readers do not share. Replace it or explain it. Keep the terms your audience searches for and uses themselves.
- Passive sentences that hide who acts. Especially in instructions, policies and anything about money, where readers need to know who does what.
- Transitions and rhythm. Polish that makes text flow once the structure is sound.
A worked rewrite
Most readability findings appear together in the same passages. Here is a typical paragraph from a service page, with the problems the checker would flag, followed by a rewrite.
Before
"Following the initial consultation, which is provided free of charge to all prospective clients, a bespoke proposal will be prepared by our team, leveraging our extensive experience across the sector in order to ensure that the solution which is ultimately delivered is optimally aligned with your organisation's strategic objectives and budgetary requirements."
That is one sentence of 52 words. It contains three passive constructions ("is provided", "will be prepared", "is delivered"), three pieces of corporate vocabulary ("bespoke", "leveraging", "optimally aligned") and a padded phrase ("in order to"). The reader has to hold the whole thing in mind to find the point, which is that the first meeting is free and a written proposal follows.
After
"Your first consultation is free. Afterwards, we will send you a written proposal based on what you told us. It will fit your goals and your budget, and it draws on our experience with similar businesses."
Three sentences, 36 words, all active, no jargon. Nothing of substance was lost, and the key fact now comes first. Notice what did not change: the rewrite is not childish, and it still sounds like a professional firm. That is the aim of every guide in this hub.
What changed, step by step
- The main point, a free consultation, moved to the start.
- The long sentence was split where each new idea began.
- Passive verbs became active, with "we" and "you" as the subjects.
- Inflated words were replaced with the plain words they stood for.
- Filler such as "in order to" and "ultimately" was removed.
What the scores cannot tell you
A readability score is a measurement of surface features, not of clarity. It is worth knowing where it misleads, so you can override it with confidence.
- Audience matters more than the number. A page for structural engineers can use terms a general reader would not know, as long as those engineers use them too. Choose a target for the people you write for, not an average reader.
- Short words are not always plain. "Tort" is one syllable; "negligence" is three. The formula prefers the first, most readers understand the second.
- Order and structure are invisible to it. Putting the answer first, using lists for steps and adding headings help enormously but barely move the score.
- Facts need to be there. A clear page that says nothing specific is still a weak page. Readability is about how you say it, not what you have to say.
Search engines do not publish a readability score as part of ranking, and Google has not said it uses one. The case for readable writing rests on readers: people who can find and understand what they came for are more likely to stay, act and come back. Clear, direct sentences that state one fact each are also easier for search features and AI assistants to quote accurately, which is one reason readability overlaps with answer engine work.
The most reliable test is still a person. Ask someone who matches your audience to find a specific fact on the page, and watch where they hesitate. Where they struggle is where to rewrite first, whatever the score says.
A sensible order of work
- Pick your ten most visited pages and run each through the Readability Checker.
- Look for patterns that repeat across pages, such as long opening sentences, stock jargon or boilerplate paragraphs. Fix those once in the template or style guide.
- Rewrite each page's opening paragraph so the main point comes first.
- Split the longest sentences and paragraphs the checker flags, and add or rename subheadings.
- Replace or define jargon, and rewrite passive sentences where the actor matters.
- Run the checker again, then read the page aloud. Anything you stumble on needs another look.
- Write the rules you settled on into a short house style guide so new content starts in better shape.
For the full reference, read the Readability Guide, see a finished report in the example report, or start with the beginner tutorial. Readable content also supports trust, which the E-E-A-T Guide covers.
1. What is a good Flesch Reading Ease score for a website?
It depends on the audience, but for general web content a score of around 60 or above is a sensible aim, because that range is usually described as plain English that most adults read comfortably. Specialist content for professionals can reasonably score lower, and simple consumer pages can score higher. Treat the number as a guide to find hard passages rather than a pass mark. A page that scores well but leaves readers confused has not really succeeded.
2. Is readability a Google ranking factor?
Google has not said that it uses a readability score, and there is no public evidence of a formula like Flesch being part of ranking. What Google does say is that it wants to rank helpful content written for people. Pages that are easy to scan and understand tend to satisfy readers better, and clear sentences are easier for search features to quote. So improve readability for your readers, and treat any search benefit as a side effect rather than the goal.
3. How long should sentences be on a web page?
There is no single rule, but plain English guidance commonly suggests an average of around 15 to 20 words, with plenty of variety. A mix of short and medium sentences reads naturally, while a run of 35 or 40 word sentences makes readers lose track. The Readability Checker flags sentences over 20 words so you can review them. Some long sentences are fine if they are well built; the problem is when most sentences are long.
4. Is passive voice always wrong?
No. The passive is the right choice when the person or thing doing the action is unknown, unimportant or obvious, as in the parcel was delivered at noon or the building was completed in 1902. It becomes a problem when it hides who is responsible, especially in instructions, policies and customer communications, where readers need to know who does what. Aim to use it on purpose rather than by habit, and rewrite passive sentences where the actor matters.
5. Does writing in plain English mean dumbing down?
No. Plain English is about removing effort that adds nothing, such as padded phrases, inflated words and sentences that bury the point. Expert readers benefit as much as anyone, because they are often busy and scanning too. You can keep precise technical terms your audience uses, explain complex ideas and write with authority. The aim is that the difficulty in a page comes from the subject itself, not from the way it is written.
6. Why do different readability tools give different scores for the same text?
Because they count things differently. Tools disagree on where sentences end, especially around headings, lists and abbreviations, and on how many syllables a word has, since syllable counting is done by rules rather than by a dictionary. Some tools include navigation and footer text, others only the main content. Compare scores from the same tool over time rather than between tools, and look at the flagged sentences rather than the headline number.
7. How often should I check readability?
Check new content before it is published, and review your most important pages whenever they are substantially updated. It is also worth running a site-wide check once or twice a year, because several authors writing over time tend to drift towards longer sentences and more jargon. The most effective long-term fix is a short house style guide covering sentence length, preferred words and headings, so writers get it right first time rather than fixing it afterwards.
The Readability Checker calculates Flesch Reading Ease, Flesch-Kincaid Grade Level, Gunning Fog, sentence and paragraph length, passive voice and jargon density, and flags the sentences that need attention.
Run the Readability Checker →