What Readability Score helps you do
Estimate Flesch Reading Ease and a U.S. grade level from word, sentence and syllable counts. It is a rough guide to how difficult a passage is to read, useful for adjusting tone for an audience. The report also shows the raw word, sentence and syllable totals so you can see what drove the score.
Readability scoring runs locally in your browser; nothing is uploaded.
How it works
These tools scan the pasted text in the browser with a pattern or parser and return the matches in first-seen order. Extraction is a candidate list, not a verification step: an email-shaped string may not be deliverable, a URL may not resolve, and a number may be part of a date or an identifier. Nothing is uploaded, and the source text is never changed. The result is a snapshot of the pasted text; editing the source afterwards does not update the list.
How to use Readability Score
- Paste a passage of at least a few sentences.
- Calculate the readability scores.
- Read the ease and grade together with the raw counts.
- Use the result to decide whether to simplify the copy.
When to use it
- Check whether a help article suits a general audience.
- Compare two drafts to see which reads more easily.
- Set a target reading level for a style guide.
- Review a landing page before publishing it.
- Check a translation for overly long sentences.
- Prepare a plain-language summary for a client.
- Check a summary before sending it to a client.
When not to use it
- Do not use it as a grammar or fact check.
- Do not apply the U.S. grade level to non-English text without caution.
- Do not treat a single score as proof of clarity.
Example
Short sentences with common words score a higher reading ease and a lower grade level than long, technical prose. The syllable count is approximate, so a word with an unusual pronunciation may shift the score slightly. The label is a convenience, not a certification.
What you can do with Readability Score
- Calculate Flesch Reading Ease.
- Estimate a U.S. grade level.
- Count words, sentences and syllables.
- Show a plain-language label such as Easy or Difficult.
- Copy the report for a review.
- Run the analysis locally with no upload.
Example: check the matches on a sample
Paste a short sample first and count the expected matches by eye. Compare that count with the result before running a large file, because a missing match is easier to spot in a small sample.
Read a few matches in context to catch false positives. A phone-like number inside an order ID, or a URL inside a code snippet, is common and should not be treated as a contact or a live link.
Copy the list and keep the original. If the extraction feeds a mail merge or a report, verify a sample of the destinations rather than assuming every match is valid.
If the result is empty, check the input format before assuming the tool is broken. A bare domain without http, an address split across a line, or JSON with a trailing comma are common reasons for no matches.
For a list that will be contacted or published, keep the source and the extracted list side by side. The source is the only way to resolve a questionable match or explain why one was missed.
What to know before you start
- The formulas assume English words and are unreliable for other languages.
- Syllable counting is approximate, so scores are estimates rather than exact measures.
- It does not assess coherence, accuracy or tone.
- Technical terms and abbreviations can skew the syllable count.
Common mistakes
- Optimizing the score instead of the reader's understanding.
- Comparing scores across languages.
- Ignoring the raw sentence count when the text is very short.
- Assuming a low grade level means the content is accurate or useful.
Troubleshooting
If the score looks extreme, the passage may be very short; use at least a few sentences.
If the grade level seems high, check for long sentences and technical vocabulary.
If the syllable count looks off, the heuristic may misread abbreviations or numbers.
If the report is empty, the text may contain no words.
Related standards and documentation
- Email addresses follow RFC 5322, but the tool uses a practical pattern rather than a full parser.
- URLs follow RFC 3986; the extractor recognises http, https and www forms.
- Regular-expression matching is not a validation service and can miss unusual formats.
- No extraction tool can prove that a match is valid or safe; that requires a separate check.
- Test on a small sample first.
- Check false positives in context.
- Review before a mail merge or report.
- Empty output usually means the format, not the tool.