Type‑Token Ratio: The Secret Metric Editors Love
Updated September 2025
Type‑Token Ratio (TTR) measures vocabulary diversity by dividing the number of unique words (types) by the total number of words (tokens). A higher TTR suggests varied language, while a lower TTR suggests repetition. Editors use TTR to quickly assess whether a draft feels fresh or redundant.
Why TTR matters
Readers engage when ideas advance and phrasing varies. Excess repetition can feel amateurish or manipulative. For SEO, variety helps cover a topic more comprehensively and can align with a broader set of related queries.
How to read TTR
- 0.45–0.60: Typical for clear, informative web writing.
- 0.60–0.75: High variety; useful for essays and creative work.
- < 0.45: Consider reducing repetitive phrasing and adding synonyms.
Improving TTR without losing clarity
- Replace repeated filler words with stronger verbs and nouns.
- Use synonyms where meaning stays intact.
- Break long sentences; vary rhythm and structure.
- Add examples and analogies to introduce fresh vocabulary.
Example workflow
A 900‑word product guide had a TTR of 0.41. After trimming boilerplate and adding specific examples, TTR rose to 0.57. The page became easier to scan and ranked for additional long‑tail phrases.
Caveats
TTR depends on text length: very short texts can have artificially high TTR. Don’t chase a number—use it to spot heavy repetition and guide revision.
Run your draft through our Word Frequency Counter, note the uniques and totals, and iterate until your language feels natural and precise.
Practical Ways to Raise TTR (without padding)
- Replace repeated modifiers with concrete verbs.
- Consolidate synonyms by choosing one precise term.
- Add varied examples instead of restating the same one.
- Use parallel structure for lists, but vary sentence openings.
- Trim boilerplate; it depresses TTR without adding value.
Editor’s Micro‑Checklist
- Mark the five most repeated non‑stopwords.
- Rewrite two sentences to swap abstraction for action.
- Add one table or figure — visuals reduce verbal repetition.
Tip: Aim for variety where it improves clarity, not to game the number.
TTR Pitfalls to Watch
- Chasing variety by adding synonyms that muddle consistency.
- Cutting necessary repetition in steps and warnings.
- Ignoring domain terms that readers expect to see repeated.
Low‑Variety Rescue Plan
- Underline the five most repeated non‑stopwords.
- Replace two generic adjectives with concrete outcomes.
- Add a short example that uses different nouns and verbs.
Measure Variety by Section
Compute TTR per section, not only for the whole page. Intros and CTAs can repeat on purpose; variety matters most in explanations and examples.
Variety without Vagueness
- Swap “optimize” with the specific outcome (e.g., “reduce load time”).
- Alternate sentence starts: subject → clause → imperative.
- Use concrete nouns (table, chart, API) over abstractions.
Section‑Level Benchmarks
| Section type | Healthy TTR | Note |
|---|---|---|
| Intro/summary | 0.35–0.50 | Repetition sets context |
| Explanations | 0.45–0.65 | Room for variety and examples |
| Step lists | 0.30–0.45 | Commands repeat by design |
Lexical Variety Drills
- Rewrite one paragraph replacing two abstract nouns with actions.
- Add one fresh example that uses different nouns/verbs.
- Collapse two near‑duplicate sentences into one precise line.
TTR & Comprehension
Use variety to distinguish concepts, not to decorate prose. Readers recall steps better when adjacent sentences don’t recycle the same generic verbs.
Section Rewrite Template
Original: <paste paragraph> 1) Cut filler (keep domain terms). 2) Replace vague verbs with actions. 3) Add one specific example. 4) Re‑run TTR for this section only.
TTR & Tone
Variety can shift tone from formal to approachable. Keep domain terms constant, but vary scaffolding around them to match audience expectations.
Micro‑Edits That Raise Variety
- Swap “in order to” → “to”.
- Replace “utilize” → “use”.
- Trade passive voice for active subjects.
- Add one contrasting example (“works well when… / not when…”).