Webpage Readability Analyzer โ€” Flesch Score & Grade Level avatar

Webpage Readability Analyzer โ€” Flesch Score & Grade Level

Pricing

from $0.50 / 1,000 results

Go to Apify Store
Webpage Readability Analyzer โ€” Flesch Score & Grade Level

Webpage Readability Analyzer โ€” Flesch Score & Grade Level

$0.5/1K ๐Ÿ”ฅ Readability analyzer! Reading time, word count, Flesch score & grade level for any URL. No key. JSON, CSV, Excel or API in seconds. Score content for SEO & editorial โšก

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

ninhothedev

ninhothedev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Webpage Readability Analyzer ๐Ÿ“–

Measure how readable any webpage is โ€” in seconds, from just a URL. Get word count, estimated reading time, Flesch Reading Ease, Flesch-Kincaid grade level, and a plain-English difficulty label for any article, blog post, product page, or documentation page. No API key. No login. No configuration.

Paste a list of URLs, hit start, and get a clean table of readability scores you can sort, filter, and export to CSV, Excel, JSON, or Google Sheets.


Why readability matters

Readability is one of the strongest predictors of whether people actually read โ€” and understand โ€” your content. Google, editors, and accessibility guidelines all reward writing that is clear and easy to follow. This Actor turns that abstract goal into hard numbers you can act on.

  • Flesch Reading Ease (0โ€“100): higher is easier. 60โ€“70 is "standard" โ€” comfortable for most adults.
  • Flesch-Kincaid Grade: the US school grade level needed to understand the text (e.g. 8.0 = 8th grade).
  • Reading time: estimated minutes at 200 words per minute.
  • Difficulty label: Very Easy โ†’ Very Confusing, at a glance.

What you get per URL

FieldDescription
urlThe analyzed page
titlePage <title>
word_countWords in the main article text
sentence_countSentences detected
syllable_countTotal syllables (vowel-group heuristic)
avg_words_per_sentenceSentence length signal
avg_syllables_per_wordWord complexity signal
flesch_reading_ease0โ€“100, higher = easier
flesch_kincaid_gradeUS grade level
reading_time_minMinutes at 200 wpm
difficultyVery Easy โ€ฆ Very Confusing
sourceAlways readability
scraped_atUTC timestamp

Input

{
"mode": "analyze",
"urls": [
"https://en.wikipedia.org/wiki/Readability",
"https://www.bbc.com/news"
],
"maxItems": 100
}
  • mode โ€” analyze (URLs โ†’ readability metrics).
  • urls โ€” one or more webpage URLs.
  • maxItems โ€” cap on URLs per run (default 100, max 1000).

Example output

{
"url": "https://en.wikipedia.org/wiki/Readability",
"title": "Readability - Wikipedia",
"word_count": 8149,
"sentence_count": 1068,
"avg_words_per_sentence": 7.63,
"avg_syllables_per_word": 1.59,
"flesch_reading_ease": 64.9,
"flesch_kincaid_grade": 6.1,
"reading_time_min": 41,
"difficulty": "Standard",
"source": "readability",
"scraped_at": "2026-07-24T12:00:00Z"
}

Use cases

  • Content QA โ€” flag pages that are too dense before they ship.
  • SEO โ€” align content complexity with search intent and audience.
  • Editorial โ€” enforce a house readability standard across writers.
  • Accessibility โ€” surface pages that exceed a target grade level.

Pricing

Runs on a tiny 512 MB actor and only fetches lightweight HTML, so a typical run costs about $0.5 per 1,000 URLs in platform usage โ€” no third-party API fees, ever.



FAQ

Does it need an API key? No. Just provide URLs.

What language does it support? The formulas are tuned for English; other languages still return counts and reading time.

How is the main text extracted? Via trafilatura, with a <p>-tag fallback, so navigation and boilerplate are stripped out.