The most common mistake in readability editing is treating a score as a universal grade. A writer sees a grade-level result, decides it is too high, and chops sentences until the number falls. The result often reads worse — because the number was never the goal. The goal is a text that the intended reader can understand with reasonable effort, and what counts as reasonable effort depends entirely on who that reader is.
A guide written for first-time renters choosing a patio heater and a specification written for heating engineers are not failing at the same task when they score differently. They are succeeding at different tasks. The Content Analyzer is most useful when you choose your audience first, pick a target range that fits that audience, and then edit toward the range — stopping when the text serves the reader, not when the score looks impressive.
Two audiences, two honest targets
Imagine the same basic information written for two different readers.
For a general reader — someone browsing for a heater for a small balcony — the text needs plain words, short explanations, and no assumed knowledge. A sensible working target is easy general prose: sentences averaging roughly fifteen to twenty words, everyday vocabulary, and any necessary technical term explained when it first appears.
For a technical reader — an installer, a buyer for a trade supplier, or an engineer comparing models — the same information can, and should, keep its precise vocabulary. Terms like clearance, BTU output, and ingress protection are not obstacles for this reader; they are the shorthand the reader already uses. Aiming this text at the same easy-reading target as the general guide would mean stripping out the very precision the reader came for.
That is why the first step in any readability edit is not opening the tool, but answering one question in writing: who is this for, and what do they already know?
Step 1: Write the audience down before you measure
Before pasting anything into the Content Analyzer, write a single sentence describing the reader. For example: "A renter with a small balcony, no technical background, choosing their first outdoor heater." Or: "A trade buyer comparing heater specifications for a rental fleet." This sentence becomes your editing standard. Every later decision — keep this term or explain it, split this sentence or leave it — gets tested against it.
Without it, editing drifts toward whatever the score rewards, which is always shorter and simpler, regardless of whether shorter and simpler serves the reader. With it, you have a reason to keep a long sentence that carries a necessary condition, and a reason to split a short sentence that still confuses a beginner.
Step 2: Measure the draft, then compare it with the target
Paste the draft into the analyzer and note the readability scores, the average sentence length, and the longest sentences. Then compare those numbers with the target you set — not with a universal ideal.
Suppose the general-reader draft scores at a level that suggests a university text, with an average sentence length of twenty-eight words. That gap tells you something specific: the draft is probably written in the author's vocabulary rather than the reader's, and the longest sentences are the first place to look. Suppose instead the technical draft scores at an easy general level: that may mean the specifications have been simplified so far that a trade reader can no longer tell models apart.
Use the Word Counter alongside the analyzer to check sentence counts and length at a glance, and keep earlier versions in the Text Compare tool so you can see whether each round of edits moved the draft toward your target or past it.
Step 3: Edit toward the target — in both directions
Editing for a general audience usually means three moves. First, split the longest sentences, especially those carrying a list or a condition. Second, replace jargon with plain words where a plain word means the same thing — "use" for "utilise," "keep away from" for "maintain clearance from" when the reader is a homeowner, not an installer. Third, explain the terms that must stay: a single clause — "BTU, a measure of heat output" — lets a beginner keep reading without a detour.
Editing for a technical audience moves differently, and sometimes in the opposite direction. Keep the precise term rather than a vague plain equivalent: "clearance" means something specific that "space around it" does not. Keep a longer sentence when it holds a condition together — splitting "Rated for outdoor use only when installed under a covered structure" into two sentences risks a reader acting on the first half alone. Explain less, but define more precisely: a technical reader wants the rating, the standard, and the limit, not a simplified summary of them.
In both cases, the reader — not the score — drives the edit.
A worked example: one fact, two versions
Take a single fact: a heater needs space around it, and fabric too close to it is a fire risk.
For general readers:
"Keep the heater away from cushions, curtains, and anything that can catch fire. Leave at least one metre of clear space around it on every side."
A beginner can act on this immediately.
For technical readers:
"Maintain a minimum clearance of one metre on all sides, and keep combustible materials — including fabric, paper, and untreated timber — outside that zone."
One sentence, the precise term "clearance," the precise category "combustible materials," and the same distance. A trade reader gets the specification in the form they can check against a datasheet.
Both versions carry the same fact and the same distance. They would score differently, and that difference is correct. Forcing the technical version to match the general version's score would mean replacing "combustible materials" with a longer, vaguer description and losing the term the reader needs for compliance checks. The score is a measurement of the text, not a judgement of the writer.
Step 4: Stop before the score becomes the goal
Stop when a reader like the one you described could understand the text without unnecessary effort, and when further simplification would cost precision or completeness. Warning signs that you have gone past that point include sentences so short they read as abrupt, technical terms replaced by vague paraphrases, and conditions dropped because they made a sentence long. If your edits start removing information to improve a number, the number has stopped helping.
A final read-through by someone like the intended reader, or reading the text aloud and imagining that reader, catches what scores cannot. Those are audience questions, and no formula answers them.
For more on the editing techniques used here, see the guide on how to improve readability.
Honest limitations
Readability scores measure sentence length and word length, not truth, clarity of ideas, or audience fit. They cannot tell you whether your audience description is right, whether a technical term is familiar to your readers, or whether the advice itself is correct. The Content Analyzer also does not detect AI-written text, and a score should never be presented as proof of quality, accuracy, or authorship. Choose the audience, use the score as a check on your editing, and judge the ideas yourself.
Frequently asked questions
What readability target should I aim for with general readers?
Aim for easy general prose: average sentences of roughly fifteen to twenty words, everyday vocabulary, and technical terms explained at first use. Treat that as a working range, not a pass mark — a text inside the range that still confuses a reader needs a rewrite of its ideas, not a better score.
Should technical writing aim for the same target?
No. Technical readers already know their field's vocabulary, and precision matters more than simplicity for them. Keep exact terms, keep conditions attached to the claims they qualify, and accept a more demanding score when the subject genuinely requires it. Simplifying past the point of precision makes technical writing less useful, not more accessible.
What if my audience is mixed — beginners and specialists together?
Write for the less experienced reader in the main text, and put specialist detail where specialists will look for it: specifications in a table, conditions in a clearly labelled note, definitions at first use. That way beginners are not blocked and specialists are not starved of the detail they need.
Is chasing a perfect readability score ever useful?
Rarely. A perfect score usually means every sentence is short and every word is simple, which is the wrong shape for most real writing — it reads as choppy, and it often hides lost precision. Use the score to check that an edit moved the text in the direction you intended, then stop when the text serves its reader.
human review pending client designation