How people read online

The single most important fact for web writing: people don't read online — they scan. Decades of research show web users skim, skip, and hunt for what they want, rarely reading word-for-word. Understanding how people actually read online is what makes you write content they'll actually consume. This lesson covers online reading behaviour. Let's face the truth about reading. Let's understand how people read online.

How people actually read online

THE KEY TRUTH: users SCAN, they don't read. Research (Nielsen Norman Group + others)
shows online reading behaviour:

- PEOPLE SCAN, NOT READ WORD-FOR-WORD — on a typical page, users read only ~20-28% of
  the words. They SKIM for keywords, headings, links, + what's relevant to their
  goal — skipping the rest.
- SCANNING PATTERNS:
  - F-PATTERN — eyes sweep across the top, then down the left, reading less as they go
    (an "F" shape). The TOP + LEFT get the most attention; the important stuff must be
    there.
  - Z-pattern / layer-cake (scanning headings) + spot-checking. People jump around.
- THEY'RE IMPATIENT + GOAL-DRIVEN — users arrive with a TASK/question, want it FAST,
  + have low patience. They decide in SECONDS whether a page is worth it (+ leave if
  not).
- THEY DON'T READ TOP-TO-BOTTOM — they jump to what looks relevant, skip intros/fluff,
  + bail when they get their answer (or get bored/lost).
- SCREENS ARE HARDER — reading on screens is slower + more tiring than print; mobile
  screens are small. This reinforces scanning + short attention.
- LOW COMMITMENT — one click away from leaving; no captive audience. You must EARN
  every moment of attention.

The key truth: users scan, they don't read — and research (Nielsen Norman Group and others) shows the behaviour. People scan, not read word-for-word — on a typical page, users read only ~20–28% of the words, skimming for keywords, headings, links, and what's relevant to their goal, skipping the rest. There are scanning patterns: the F-pattern (eyes sweep across the top, then down the left, reading less as they go — an "F" shape — so the top and left get the most attention and the important stuff must be there), plus Z-pattern / layer-cake (scanning headings) and spot-checking — people jump around. They're impatient + goal-driven — users arrive with a task/question, want it fast, and have low patience, deciding in seconds whether a page is worth it (and leaving if not). They don't read top-to-bottom — they jump to what looks relevant, skip intros/fluff, and bail when they get their answer (or get bored/lost). Screens are harder — reading on screens is slower and more tiring than print, and mobile screens are small, which reinforces scanning and short attention. And there's low commitment — users are one click away from leaving (no captive audience), so you must earn every moment of attention. This is the reality you write for.

Writing for scanners

WRITE FOR HOW PEOPLE ACTUALLY READ — make content SCANNABLE + front-loaded (this
drives most web-writing rules; see scannability + structure lessons):

- FRONT-LOAD THE KEY INFO (INVERTED PYRAMID) — put the most important point/answer
  FIRST (at the top + start of sections). Don't bury the lede or make people dig.
  Scanners grab the top.
- USE SCANNABLE STRUCTURE — descriptive HEADINGS + subheadings (so scanners navigate),
  SHORT paragraphs (1-3 sentences), BULLET LISTS, BOLD keywords, + white space. Break
  content into chunks.
- HIGHLIGHT KEYWORDS + THE IMPORTANT BITS — the words scanners' eyes catch (headings,
  bold, links) should carry the meaning. Make the scannable elements informative.
- BE CONCISE — cut words, fluff, + long intros. Less text = easier to scan + read.
  Say it in half the words.
- MAKE IT USEFUL + RELEVANT FAST — deliver value quickly so the impatient reader stays.
  Answer their question; don't waste their time.
- PUT KEY THINGS TOP + LEFT (F-pattern) — headlines, key info, + important links where
  eyes land first.
- WRITE FOR MOBILE — short, clear, chunked content that works on small screens.

THE PRINCIPLE: people SCAN, don't read — impatient, goal-driven, jumping around,
reading a fraction of the words. So write SCANNABLE, front-loaded, concise, useful
content: key info first, clear headings, short chunks, highlighted keywords. Design
your writing for scanning, + people will actually get your message.

You write for how people actually read — making content scannable and front-loaded (this drives most web-writing rules). Front-load the key info (inverted pyramid) — put the most important point/answer first (at the top and start of sections) — don't bury the lede or make people dig (scanners grab the top). Use scannable structure — descriptive headings and subheadings (so scanners navigate), short paragraphs (1–3 sentences), bullet lists, bold keywords, and white space — break content into chunks. Highlight keywords + the important bits — the words scanners' eyes catch (headings, bold, links) should carry the meaning (make the scannable elements informative). Be concise — cut words, fluff, and long intros (less text = easier to scan and read — say it in half the words). Make it useful + relevant fast — deliver value quickly so the impatient reader stays (answer their question, don't waste their time). Put key things top + left (F-pattern) — headlines, key info, and important links where eyes land first. And write for mobile — short, clear, chunked content that works on small screens. The principle: people scan, don't read — impatient, goal-driven, jumping around, reading a fraction of the words — so write scannable, front-loaded, concise, useful content: key info first, clear headings, short chunks, highlighted keywords — design your writing for scanning, and people will actually get your message.

The mistake beginners make

The first mistake is writing for readers who read every word — assuming attention the reader won't give, with long intros, dense paragraphs, and buried points; write for scanners (front-loaded, chunked). The second mistake is burying the key info — making readers dig through fluff for the answer (they'll leave first); front-load the point (inverted pyramid). The third mistake is walls of text (not scannable) — big blocks with no headings, lists, or white space, which scanners skip; use scannable structure. And long-winded/fluffy writing — padding that wastes the impatient reader's time; be concise. And ignoring the F-pattern/top-of-page + mobile — putting key info where eyes don't land, or not writing for small screens; put important things top/left and write for mobile. Write for scanners, front-load the point, make it scannable, be concise, and respect the F-pattern + mobile.

Your turn

---

Your turn

1. Front-load the point: take a piece and move the most important information/answer to the very top and the start of each section (inverted pyramid), so a scanner gets it immediately.
2. Make it scannable: add descriptive headings/subheadings, break text into short paragraphs (1-3 sentences), use a bullet list, and bold the key words - so the eye can skim it.
3. Cut it in half: ruthlessly trim fluff, long intros, and padding so the same message takes far fewer words (easier to scan and read).
4. Respect the F-pattern: put your headline, key info, and important links near the top and left where eyes land first, and make headings/bold carry the meaning for skimmers.
5. Test the scan: skim your own page for 5 seconds (like a real user) and check you can grasp the main points from just the headings, bold, and first lines - if not, restructure.

Key points

• The key truth: users SCAN, they don't read (research — NN/g): on a typical page they read only ~20-28% of the words, skimming for keywords/headings/links relevant to their goal + skipping the rest. Scanning patterns: F-PATTERN (top + left get the most attention — put important stuff there), plus layer-cake (scanning headings) + jumping around.
• They're IMPATIENT + goal-driven (a task, want it fast, decide in SECONDS + leave if not worth it), don't read top-to-bottom (jump to what's relevant, skip intros/fluff, bail on their answer), screens are harder (slower/tiring; mobile is small), and there's LOW COMMITMENT (one click from leaving — earn every moment).
• Write for scanners: FRONT-LOAD the key info (inverted pyramid — point/answer first, don't bury the lede), use SCANNABLE structure (descriptive headings, short 1-3 sentence paragraphs, bullet lists, bold keywords, white space), HIGHLIGHT keywords/important bits (make headings/bold carry the meaning), be CONCISE (cut fluff/long intros — say it in half the words), deliver value FAST, put key things TOP + LEFT (F-pattern), and write for MOBILE.
• Design your writing FOR scanning and people will actually get your message.
• The mistakes: writing for readers who read every word (they won't — write for scanners), burying the key info (they leave first — front-load it), walls of text / not scannable (skipped), long-winded/fluffy writing (wastes impatient readers' time), and ignoring the F-pattern/top-of-page + mobile.