Content & Messaging
Scannability
People scan web pages rather than read them — structure content so scanners still get the point.
Where it comes from
It comes out of decades of eye-tracking and reading research at the Nielsen Norman Group, beginning with Jakob Nielsen's 1997 finding that people rarely read web pages word by word, and reinforced by later studies that mapped the F-shaped and 'layer-cake' patterns the eye actually follows.
Why it matters for your website
Users don't read — they scan, hunting for the thing that answers their question. NN/G eye-tracking research shows most people read only a fraction of the words on a page, typically in an F-shaped or layer-cake pattern. Content built for scanners — short paragraphs, clear subheadings, key phrases that stand out — consistently beats walls of text.
Scanning isn't laziness — it's how people cope with abundance. A visitor arrives with a question and a low tolerance for hunting, so they skim for the words that look like an answer and skip everything else. If your point lives in the middle of a dense paragraph, most readers sail straight past it, however well it's argued.
Writing for scanners is mostly a structural job, not a writing-shorter one. The same words become far more effective when the page is broken into short paragraphs, meaningful subheadings, and front-loaded sentences — so that even a reader taking in only the headings and first lines still leaves with the gist.
Wrong vs right
A landing page that explains its value in three long, unbroken paragraphs — the key benefit is in sentence four of the second block, where almost no one reaches it.
The same content with a clear subheading per idea, the benefit stated first, and supporting detail beneath. A scanner gets the point from the headings alone.
A feature list written as flowing prose, so the reader has to parse full sentences to extract each capability.
A short bulleted list with the key term at the start of each item, scannable in a couple of seconds.
Subheadings that are clever but uninformative ('Think different') above the content they label, giving the scanning eye nothing to grab.
Descriptive subheadings that summarise the section below them, so reading only the headings still tells a coherent story.
Understanding Scannability
Scannability is the quality of a page that lets someone extract its meaning without reading it in full. The research behind it is unusually consistent: eye-tracking studies repeatedly show people read only a portion of the text on a page — often around a fifth to a quarter — and move through it in predictable shapes. The F-pattern (heavy attention to the top and left, tapering down) and the layer-cake pattern (jumping between headings and skipping the prose between) are the two most common.
Designing for that behaviour means building a page that survives being skimmed. The load-bearing elements are subheadings that genuinely describe their sections, short paragraphs that each make one point, bulleted lists for sets of things, bold key phrases used sparingly, and sentences that put the important word first. Together they create entry points — places for the scanning eye to land and decide whether to slow down.
It's worth being clear about what scannability is not. It isn't dumbing down, and it isn't simply cutting words — a well-structured long article scans better than a short but undifferentiated one. The aim is a page that works at two speeds at once: fully legible to the rare person reading every word, and still coherent to the majority who only graze the headings and the first line of each block.
How Kweri checks it
Kweri can assess much of scannability structurally — it looks at paragraph length, the presence and distribution of headings, list usage, and whether the page is one dense block or broken into digestible units. What it can't fully judge by machine is whether your subheadings are actually *informative* rather than merely present, or whether the most important point is front-loaded within each section — that's a reading-comprehension call. So Kweri reliably flags walls of text and missing structure, and raises softer prompts about whether the structure you do have is pulling its weight.
FAQ
What does scannability mean in web design?
Scannability is how easily a reader can skim a page and still grasp its main points without reading every word. It's achieved through clear headings, short paragraphs, lists, and key phrases that stand out.
Why do people scan instead of read?
Because they arrive with a specific question and limited patience. Eye-tracking research shows most visitors read only a fraction of the words on a page, skimming for whatever looks like it answers their need and skipping the rest.
How do I make content more scannable?
Use descriptive subheadings, keep paragraphs to one idea each, break sets of items into bulleted lists, front-load the key word in each sentence, and bold the occasional crucial phrase. The test is whether someone reading only the headings and first lines still gets the gist.
What is the F-pattern?
The F-pattern is a common reading path in which people read across the top of the content, then down the left side with progressively shorter horizontal glances, forming an F shape. It's one reason key information belongs at the top and the start of lines.
Does writing for scanners mean writing less?
Not necessarily. Scannability is mostly about structure, not length — a long but well-organised page with clear headings and short paragraphs scans better than a short, undifferentiated block of text.
Are subheadings really that important?
Yes. Many people read in a 'layer-cake' pattern, taking in headings and skipping the prose between them. Informative subheadings that summarise their sections let those readers follow the whole argument from the headings alone.
Related principles
Readers often scan in an F shape — strong across the top, weaker across a second line, then down the left.
Breaking information into small, meaningful groups makes it faster to scan, understand, and remember.
Plain, direct language is understood faster and trusted more — jargon and complexity are barriers.
Space around and between elements is not wasted — it creates hierarchy, grouping, and focus.
Attribution & sources
Identified by Nielsen Norman Group (Jakob Nielsen) (1997, with later eye-tracking studies). Catalogued from Nielsen Norman Group — Text Scanning Patterns: Eyetracking Evidence.
Grounded in NN/G's long-running eye-tracking research into how people read online.
See Scannability on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →