The heat map arrived as a PDF, red and orange smudges laid over an article you had polished for two evenings. Your favorite paragraph, the one with the long build and the turn at the end, was cold blue. The smudges clustered on the headline, the first two lines of text, one bolded phrase near the middle that you had emphasized almost by accident, and the subheadings.
You wrote an essay. Your visitors read a weather report.
That PDF is not an opinion; it is a recording of behavior. Web writing is not print writing with shorter paragraphs. It is writing for a reader whose default is scanning, who decides line by line whether your next sentence is worth dropping into.
What the eye-tracking cameras saw
The Nielsen Norman Group has been running eye-tracking studies of web users since the late 1990s, and the pattern they kept finding on text-heavy pages earned its own name: the F. Readers make a long horizontal scan across the opening lines. A second, shorter horizontal scan follows, a little further down. From there the eye drops straight down the left edge of the page, snagging on the first words of paragraphs, subheadings, and list items, and darting into any line that promises something.
Two details in that description should stop you. The real reading happens near the top; after the first couple of paragraphs, people are sampling, not following. And the fixations land on the first words of lines, which makes the left edge of your page the most valuable strip of text you own. Where you put information now predicts whether it survives contact with a reader.
One honest caveat: the F is a symptom, not a law. It is what people do when a page gives them no strong reason to read in order; they forage instead. The researchers who studied this foraging behavior called the cues readers follow "information scent." A subheading either smells like the thing your reader wants or it does not, and the nose decides before the brain does.
Front-load the sentence, not just the page
"Put the conclusion first" is the standard advice, and it is true but incomplete. The scanning eye samples the first words of a line before committing, so a sentence that buries its payload in a trailing clause never reaches the exact reader it was written for.
| Written this way | Rewritten this way | What moved |
|---|---|---|
| "In order to qualify for a refund, you must submit the form within 30 days." | "Submit the form within 30 days to qualify for a refund." | The action now leads the sentence |
| "It should be noted that fees may apply during the trial period." | "Fees may apply during the trial period." | The throat-clearing is gone |
| "There are three reasons the migration failed, and permissions are behind all of them." | "Permissions are behind all three reasons the migration failed." | The verdict arrived before the counting |
The same logic governs link text. "Click here" carries no scent; "Read the refund policy" tells a scanner what sits behind the link before they spend the detour. And if your openings lean on filler like the middle example above, our guide to cutting filler words is the fastest cleanup.
The inverted pyramid, from telegraph wire to feed
The oldest structural answer to scanners predates screens by a century. The story journalism historians tell is that Civil War correspondents, filing copy over telegraph lines that were expensive and could drop mid-transmission, sent the newest and most important facts first, so that whatever survived the wire was still a story. Editors trimming for space cut from the bottom for the same reason. The habit hardened into the inverted pyramid: conclusion first, supporting detail second, background last.
The web did not invent cutting from the bottom; it industrialized it. Feed previews truncate your text mid-sentence. Search snippets lift whatever fragment seems to answer the question. Readers quit on their own schedule, wherever their personal threshold sits. When the payoff can be severed from the tail, put it where the scissors cannot reach.
One caveat, because the pyramid is a tool rather than a religion: pure pyramid all the way down produces a first paragraph that spoils everything and a middle nobody finishes. News and direct answers deserve it; essays do better escalating toward a payoff, a craft question our piece on writing blog posts people finish works through.
Chunk to the screen, not the page
A paragraph of 130 words looks respectable on a sheet of A4. On a phone it is a wall with no doors. Screens expose only a few lines at a time, which means the paragraph break does double duty: it marks a change of thought, and it gives the eye a progress marker for judging distance. A reader facing an unbroken block on a small screen does not decide to read it slowly. They decide to leave.
The working habit is one idea per paragraph, with paragraphs of roughly one to four sentences. This is not a license to shred: a page of single-line paragraphs reads like a slide deck and starves the reader of connective reasoning, and the paragraph remains a unit of thought, as our guide to paragraph structure and length argues. What changes on screen is the visual budget, not the logic. To check the shape of a draft fast, a paragraph counter shows how your lengths distribute, and a word counter flags sections that have grown past one comfortable scroll.
Write for the interrupted
The mobile reader is not a smaller desktop reader. She is holding the phone one-handed on a train platform, glare washing out half the contrast, when a message lands about the thing she actually cares about. Interruption is the normal condition of web reading, and it changes the page in two ways.
First, subheadings are re-entry points. A reader yanked away and returned needs to reorient in a single glance, and the nearest subheading is the handhold that saves her from scrolling up and starting over. They should still make sense as a sequence, but the re-entry function is what mobile conditions add.
Second, define terms at first use, because scrolling back on a phone costs the reader her place, and most readers guess instead of checking. A guessed definition is how support tickets are born.
Frequently Asked Questions
Do people really not read online?
They read on demand. Scanning is the default, but the opening paragraphs get genuine reading, and a passage that visibly answers the question a reader arrived with will pull them in. Your job is to make continuing feel rational, line by line.
How long should a web paragraph be?
One idea, usually one to four sentences. If a paragraph needs a second idea to make sense, you have two paragraphs sharing an indent, and the reader pays for it on a small screen.
Does the F-pattern mean long pages don't work?
No. It means long pages must be structured so scanners can navigate them: front-loaded sections, informative subheadings, no unbroken blocks. Depth is not the problem. Depth with no entry points is.
Should I bold key phrases?
Sparingly, and on the scannable spine, meaning the short phrase that carries each paragraph's verdict. Emphasis is a currency; printing more of it makes each unit worth less.
Is writing for scanners the same as SEO writing?
No, though they cooperate. SEO writing is built around queries and crawlers; scanning-aware writing is built around the human who arrives from the search result. Both reward putting the answer early, which is why the two get confused.
The first-line audit
Take the page you care most about and read, in order, only this much: the headline, the first sentence of every paragraph, and the subheadings. That skeleton is the page most of your visitors actually read. If it teaches the core of what you came to say, scanners leave satisfied and readers settle in for the rest. If it does not, you now know exactly which lines to rebuild first.