Clarity Through Structure: Chunking Content That Sticks

Phone numbers are written in groups for a reason. Ten digits in a row are hard to hold in your head; three groups of three or four are easy. The digits didn’t change. The chunks did. This is one of the oldest findings about human memory, and it applies to web pages just as directly as to phone numbers, though almost nobody writes pages as if it does.

A web page is a stream of information competing for a working memory that holds only a few things at once. The visitor can’t keep your whole page in their head, so they keep a compressed version: a handful of chunks, each with a rough label. “This part is about price. This part is about security. This part I skipped.” Whether your page sticks depends less on the quality of your sentences than on whether it divides into chunks the visitor can label. A page with five clean chunks survives in memory. A page that’s one undifferentiated flow, or thirty fragments, evaporates on scroll.

You can watch this fail in two opposite directions. The first is the wall: long paragraphs, no visual breaks, sections that bleed into each other. The writing may be excellent, but the visitor’s compression algorithm has nothing to grab. There are no seams, so there are no chunks, so there are no labels, so ten seconds after leaving they remember only “there was a lot of text.” The second failure is confetti: dozens of tiny cards, badges, and three-word blurbs, each too small to mean anything alone. Confetti looks scannable, and it is — there’s just nothing to scan into. Each fragment is below the threshold where a chunk can carry an idea. The wall gives you one chunk too big to swallow; confetti gives you fifty too small to matter. Both leave the visitor holding nothing.

The right size for a chunk is roughly one idea, where an idea is something the visitor could repeat afterward in a sentence. “It watches your site and emails you when something breaks” is an idea. “Powerful monitoring” is not; it’s a label without contents. “Our infrastructure leverages distributed observability pipelines” is contents without a graspable label. A good chunk has both: a boundary the eye can find and a payload the mind can restate. When I review pages, I try restating each section from memory after looking away. The sections I can’t restate are either overstuffed or empty, and it’s usually obvious which.

Boundaries matter as much as size, and this is where structure stops being a writing question and becomes a markup question. The visible seams of a page — headings, spacing, background shifts — tell sighted skimmers where chunks begin. The invisible seams — actual heading elements, in order, h1 then h2 then h3 without skipping — tell everyone else. A screen reader user navigates by jumping between headings; a heading hierarchy that’s really just bold text, or that jumps from h1 to h4 because the h4 looked right, hands them a table of contents with the page numbers shuffled. Search engines read the same hierarchy to understand what the page is about. It’s a small miracle of alignment: the outline that helps a distracted human skim is the same outline that helps assistive technology navigate and the same outline that helps a crawler index. One structure, three audiences. Getting it wrong shortchanges all three at once, which is why the structural checks in GazeSite’s audits ended up spanning what I’d initially thought were separate categories.

The test I trust most is reconstruction. Take your page, strip it to just the headings, and hand that skeleton to someone who’s never seen the product. Can they tell you the argument? A well-chunked page has headings that read as a sequence: what it is, how it works, what it costs, how to start. The skeleton alone tells the story, and the paragraphs under each heading are elaboration for whoever wants it. A badly chunked page has headings like “Features,” “Why Us,” “Solutions” — labels so generic they’d fit any company on earth. If your skeleton could be reassembled under a competitor’s logo without anyone noticing, your structure is carrying no information, and the visitor’s compressed memory of your page will carry none either.

What I like about chunking as a lens is that it’s mechanical enough to act on. “Write clearly” is advice that bottoms out in taste. “Divide the page into five sections, give each one idea and a heading that states it, and make the heading hierarchy real in the markup” is advice you can execute this afternoon without being a great writer. The words still matter. But structure is the part of clarity you can get right by procedure, and in my experience it moves comprehension more per hour of effort than any amount of sentence-polishing. Most unclear pages aren’t unclear because the sentences are bad. They’re unclear because nobody decided where the pieces were.

Decide where the pieces are. The visitor’s memory will do the rest, but only if you give it something shaped like a piece.