How to Fix a Low Readability Score (Flesch Reading Ease)
This check averages the Flesch reading ease score of every crawled page with enough prose to measure. An average below 50 means most visitors and AI systems find your copy hard to read, and below 30 is academic-paper territory. By the end of this guide you will have found your hardest pages, rewritten them toward a 60+ score (about grade 8–9), and confirmed the new site average.

Why it matters
Flesch reading ease is driven by two things: words per sentence and syllables per word. Dense copy makes people leave product and service pages before they reach the call to action. It also makes your claims harder for AI answer engines to quote cleanly, because they prefer short, self-contained sentences they can lift word for word.
5 reading-level guidance. The rewrite is the same either way: shorter sentences, shorter words.
What you need
Step-by-step fix
Find the pages dragging your average down
The score is an average across pages, so a few dense pages can sink the whole site. List the pages with real body copy: home, service, product, about and blog posts. Rank them by traffic in Search Console (Performance > Pages) and start with the top 10.
Pages with almost no text, like contact forms, are not scored and can be skipped.
Measure a baseline score for each page
Copy the main body text of each page, without the menu and footer, into your tool and note the Flesch reading ease. In Microsoft Word, turn on File > Options > Proofing > Show readability statistics, then run Review > Spelling & Grammar (or Editor > Insights in Microsoft 365). For batch checks, use Python with textstat.
Record each score in a spreadsheet so you can compare later.
pip install textstat
python3 -c "import textstat; t=open('page.txt', encoding='utf-8').read(); print('Flesch:', textstat.flesch_reading_ease(t), '| Grade:', textstat.flesch_kincaid_grade(t))"Split long sentences
Sentence length has the biggest effect on the score. Aim for an average of 15–18 words per sentence, and break up anything over 25. Look for natural break points:
- "and", "which", "while", "because" joining two ideas
- semicolons and long dashes
- lists of three or more items squeezed into one sentence (turn them into bullets)
Vary the length a little so the text doesn't sound robotic.
Before (38 words): Example Co provides a comprehensive range of bookkeeping services designed to help small businesses manage their finances more efficiently, which means you can spend less time on paperwork and more time growing your business while staying compliant. After (3 sentences, avg 10 words): Example Co does the bookkeeping for small businesses. You spend less time on paperwork. Your books stay compliant while you grow.
Replace long words with short ones
Syllables per word is the second input to the formula. Every 3–4 syllable word you swap for a 1–2 syllable word raises the score. Use the swap list below, and search your CMS for the worst offenders.
Keep industry terms your customers actually search for, but explain them once in plain words.
utilize → use facilitate → help approximately → about commence → start additional → more / extra functionality → features implement → set up / do numerous → many subsequently → then / later in order to → to prior to → before demonstrate → show comprehensive → full / complete individuals → people
Switch to active voice and direct verbs
Passive voice and noun-heavy phrases add words and syllables. Change "The report is generated by the system" to "The system creates the report." Turn hidden verbs back into verbs: "make a decision" becomes "decide", "provide assistance" becomes "help". Address the reader as "you" and your company as "we"; both are one-syllable words that also make the copy warmer.
Before: Optimization of your account settings can be performed by an administrator. After: An admin can change your account settings.
Fix formatting that creates run-on sentences
Readability tools count a sentence as everything between full stops. Bullet lists, table cells and headings without end punctuation can be read as one huge sentence when the text is extracted. Do these things:
- Use real
<ul>/<li>lists, not line breaks inside one paragraph. - End full-sentence bullets with a period.
- Keep long spec tables out of the main prose, or break them into short labeled rows.
- Delete repeated boilerplate paragraphs that appear in the body of every page.
<!-- Avoid --> <p>Features include real-time sync<br>automated invoice reminders<br>multi-currency support</p> <!-- Better --> <ul> <li>Real-time sync.</li> <li>Automatic invoice reminders.</li> <li>Multi-currency support.</li> </ul>
Re-score, publish and run the audit again
Paste each rewritten page back into your tool and confirm it scores 60 or close to it. Publish the changes and clear any page or CDN cache so the crawler sees the new text. Then re-run the audit.
The site-wide average should now be 50 or higher. Add the readability check to your editorial checklist so new pages don't pull the average back down.
Platform-specific notes
WordPress
Yoast SEO shows a Flesch reading ease score under the Readability tab in the post editor sidebar. It also flags long sentences, passive voice and long paragraphs. Rank Math covers similar items under Content Readability in its SEO panel. For bulk text changes across posts, use a plugin like Better Search Replace, and back up your database first.
Shopify
Most scored prose sits in product descriptions (Products > select product > Description), collection descriptions and Online Store > Pages. Text from your theme sections (Online Store > Themes > Customize) can also be crawled. Rewrite those blocks too, or a dense homepage banner may lower the score.
Webflow
Blog and product copy usually lives in CMS Collections (CMS panel > Collection > item > Rich Text field), not on the static page. Edit the collection items. The template text is shared across every item page, so simplifying it once raises the score of all of them.
Wix
Edit text directly in the Editor or in Blog > Posts. For Wix Stores, product descriptions are under Store Products > Products. Wix has no built-in Flesch score, so check your copy in Hemingway or Word before you paste it in.
Next.js / static sites (MDX, Markdown)
Content lives in your repo, so you can automate checks. Run textstat or a linter like Vale with a readability rule in CI, and fail the build if a new .md or .mdx file scores below 50.
Check that it worked
✅ How to verify
- Re-run the site audit and confirm the message reports an average Flesch reading ease of 50 or more.
- Paste the live body text of your top 5 pages into Hemingway Editor or textstat and check each scores about 60 or higher (grade 8–9).
- View the live page source or use your browser's reader mode to confirm the rewritten copy is published and not served from an old cache.
⚠️ Common mistakes
- Only cutting sentences in half with periods while leaving the long words in place. Syllables per word moves the score almost as much as sentence length.
- Rewriting the blog but ignoring high-traffic service, product and home pages. Those are scored too, and they often carry the densest marketing language.
- Making copy so choppy that it reads like a list of fragments. Mix short and medium sentences rather than making every sentence 5 words.
- Running the formula on non-English pages. Flesch reading ease is calibrated for English, so scores for other languages are not comparable.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What is a good Flesch reading ease score for a website?
60–70 is plain English and roughly a grade 8–9 reading level, which suits most business and ecommerce sites. 50–60 is acceptable for technical B2B topics. Below 30 is very hard to read and usually means long sentences full of multi-syllable jargon.
Does readability directly affect Google rankings?
Google does not use a Flesch score as a ranking factor. Readable pages tend to keep visitors longer and answer queries more directly, and they are easier for AI Overviews and other answer engines to quote. Those effects can help visibility indirectly.
How is Flesch reading ease calculated?
Score = 206.835 − 1.015 × (words ÷ sentences) − 84.6 × (syllables ÷ words). Higher is easier. Shorter sentences and words with fewer syllables both raise the score.
Do I have to remove technical terms to improve readability?
No. Keep the terms your customers search for and use. Shorten the sentences around them, explain each term once in simple words, and cut the filler jargon such as "leverage", "synergy" and "comprehensive solution".
How to Fix Long Paragraphs So Your Pages Are Easy to Scan
How to Fix Content Freshness: Dates, Updates & Last-Modified
How to Fix Spelling and Grammar Errors on Your Website
How to Fix Duplicate Content Across Pages on Your Website
How to Fix Topical Coverage Gaps Against Your Competitors
How to Fix Thin Content: Expand or Merge Pages Under 300 Words