Flesch reading ease: how to check a page and raise the score

Flesch reading ease is a 0 to 100 score for how easy a passage of English is to read, and most pages written for the general public should land between 60 and 70. To check a live page, run it through seogeoaeo.ai's Readability Analyzer, then cut long words before you split long sentences, because the formula punishes syllables far harder than sentence length.

What the score counts

Rudolf Flesch published the formula in 1948. It uses two averages and nothing else:

206.835 - 1.015 x (words / sentences) - 84.6 x (syllables / words)

A higher result means easier text. Meaning, order and accuracy never enter the math, so a page can score well and still hide its answer in the fifth paragraph. Use the number to find heavy passages, not to grade the writing.

Step 1: check the page as readers see it

Enter a public URL or paste a draft; pasting works for copy that is not live yet. On a URL, the analyzer reads the main prose and leaves out menus, headers, footers, headings, code and tables, so boilerplate does not skew the result. It does not run JavaScript; if your copy loads in the browser after the page arrives, paste the text instead. A run costs 5 credits, and the price shows before it starts.

The report gives the reading ease score with its label, the Flesch-Kincaid grade level, the Gunning Fog index, the counts behind them, and a list of sentences worth rewriting, each with the reason it was picked.

Step 2: read the band, not the decimal

For a sense of scale, Wikipedia puts Reader's Digest near 65 and Time magazine near 52. Microsoft's Word help suggests 60 to 70 for most standard documents. Checkers count syllables in slightly different ways, so compare a page with its own earlier score in the same tool rather than with a number from somewhere else.

Step 3: shorten the words first

Raise the average by one word per sentence and you lose about one point. Raise it by a tenth of a syllable per word and you lose about 8.5 points, roughly what eight extra words in every sentence would cost. That is why swapping a handful of abstract nouns usually beats splitting sentences.

Scan the rewrite targets for nouns that hide a verb: "implementation" becomes "adding", "assistance" becomes "help". Keep a precise long term when the reader needs it. A security guide should still say "authentication" and define it once.

Step 4: then break up the long sentences

Sentences held together by "and", "which" or "since" usually carry two ideas. Give each its own sentence. While you are there, move the answer to the first line under each heading. No formula rewards that, but readers notice.

Step 5: rerun and stop at the target

Check the same URL again after you publish the edit. For home, pricing, product and help pages, stop once you reach the 60 to 70 band; pushing far past 80 on a sales page tends to strip out the details a buyer wants. For developer docs and specialist legal or clinical writing, a lower score is normal. Watch sentence length there instead.

When another tool fits better

If you want feedback while you type, an editor such as Hemingway Editor or the readability statistics in Microsoft Word suits drafting better, and seogeoaeo.ai does not rewrite copy for you. For live pages, repeat checks and coding agents that call the check over MCP or REST, seogeoaeo.ai is the better fit.