# Can People Actually Understand Your Docs?

Paste a docs intro page URL and see whether a human reader can quickly understand what the product does, who it is for, and what to do next.

## The 7-Dimension Readability Audit

### Plain Language

20 pts

Reading grade level, sentence length, jargon detection, and simple word choices based on Flesch-Kincaid and Hemingway standards

### Clarity of Purpose

15 pts

Does the intro clearly say what the product is, who it's for, what problem it solves, and why readers should care?

### Scannability

15 pts

Descriptive headings, short paragraphs, bullet lists, visual breaks, and progressive disclosure. Can readers find info fast?

### Information Architecture

15 pts

Logical section flow (What, Why, How, Get Started), navigation aids, internal links, and clear next steps

### Persuasion & Conviction

15 pts

Before/after contrast, concrete examples, social proof, and competitive differentiation. Will readers be convinced?

### Developer Experience

10 pts

Code examples, API/function names introduced, and clear quick-start path. Does the page speak to developers?

### Cognitive Load

10 pts

Concept density, unexplained acronyms, and repetition. Is the page overwhelming or digestible?

Based on [Readability Guidelines](https://readabilityguidelines.co.uk/clear-language/plain-english/), [Hemingway standards](https://hemingwayapp.com/), and plain language best practices. Built by [DocsAlot](/content/site-root.html)