How to structure a newsletter for skim reading

The honest reality of newsletter reading is that most subscribers skim. They read the subject line, the first sentence, glance at the headers, scan for anything that catches their eye, and decide in five seconds whether to keep reading or move on. Designing the structure for skimmers (without dumbing down the content for readers who actually engage) is one of the highest-leverage edits you can make.

Here is the practical version.

What skim-reading looks like

Eye-tracking research from the Nielsen Norman Group, Litmus, and various email-testing services consistently shows the same pattern. Newsletter readers rarely read top to bottom. They scan in an F-pattern: heavily across the top, less heavily down the left, and skim diagonally through the rest.

This means three things matter disproportionately.

The subject line and pre-header. The reader sees these before opening. They decide whether to open at all.

The first paragraph. The reader reads the first one or two sentences carefully. The rest gets skimmed unless something hooks them.

The headers. Section headers act as navigation. Skimmers read headers to decide which sections deserve attention.

Everything else gets variable attention, with the bottom of the email getting the least.

The structure of the newsletter should respect this pattern, not fight it.

Lead with the answer

The single most important structural rule is to put the most useful sentence at the top.

If you are explaining how to do something, the answer comes first. The why and the qualifications come after.

If you are sharing a perspective, the perspective comes first. The supporting argument follows.

If you are summarising news, the news comes first. The context follows.

This is the opposite of how academic and corporate writing teaches you to structure things. Academic writing builds up to the conclusion. Newsletter writing puts the conclusion at the top and earns the reader's attention through the rest of the piece.

The reason is structural. A skimmer who reads only the first paragraph should still walk away with the main point. A reader who keeps going gets the full argument as a reward, not as a prerequisite.

Use headers as a table of contents

Section headers do real work in newsletters. They tell skimmers what is in each section so they can decide which to read.

Three rules for headers.

Make them descriptive, not clever. "What changed this week" beats "Notable shifts." "How to fix it" beats "The path forward."

Front-load the meaning. The first three words of a header carry the most weight because they are what skimmers read.

Use them every two to three paragraphs. Walls of text without headers are skipped. Excessive headers (one per paragraph) feel like marketing.

The H2 level (## in Markdown) is usually the right header level for newsletter sections. H3 (###) for sub-sections within longer pieces. Anything deeper than H3 is a sign the structure has too many levels.

Short paragraphs, mostly

Paragraph length affects perceived readability. Short paragraphs feel readable. Long ones feel intimidating.

That said, "every sentence on its own line" is a separate (and worse) anti-pattern. One-sentence paragraphs read as fragmented and feel like marketing copy.

The right shape is real paragraphs of two to four sentences, occasionally one short paragraph for emphasis. Variation matters. A page of identical four-sentence paragraphs reads as monotonous. A page of single-sentence stand-alones reads as choppy.

Use bullets only when bullets are actually right

Bullets are useful for genuinely listed information: steps in order, ingredients in a recipe, items in a comparison. They are the wrong tool for prose.

A page of bullets reads as someone who could not be bothered to write paragraphs. Each bullet feels disconnected from the next. The argument loses its thread.

A useful test: if your bullets all start with similar verbs and could be rewritten as a short paragraph with no loss of meaning, they should be a paragraph. If they really are a list of distinct items, bullets help.

Bold sparingly

Bold text in newsletters draws the eye. Used sparingly, it reinforces the most important sentence in a section. Used heavily, it loses meaning entirely.

The rule of thumb: bold one phrase per section, maximum. If everything is bold, nothing is.

Italic for emphasis, occasionally. Not for whole paragraphs.

Coloured text is rarely worth using in email. Colours render unpredictably across email clients and dark mode. Restraint serves you.

CTAs need to be visible

If your newsletter has a call to action, the skimmer needs to see it without effort.

Three placements work.

After one or two paragraphs, when the reader has just engaged with content. This catches readers who liked what they read so far.

Halfway through, written naturally as part of the prose. This catches readers who are still scrolling.

At the end, as a final clear ask. This catches readers who got all the way through.

Most newsletters do well with two of the three placements. All three is sometimes too many.

For more on CTA writing specifically, see how to write a newsletter CTA people actually click.

Length and pacing

Newsletter length depends on category. As rough defaults:

Curated industry digest: 600-1000 words.

Personal-essay newsletter: 800-1500 words.

Long-form analysis: 1500-2500 words.

The honest reality is that most newsletters are too long. Cutting twenty percent of any first draft almost always improves it. The remaining content reads better, ships faster, and respects the reader's time.

If your newsletter is consistently over 2000 words, ask whether you are using length as a substitute for clarity. Often, longer means less edited, not more thoughtful.

What goes at the end

The end of the email gets the least skim attention. That makes it a good place for:

Brief sign-off. Personal voice. Two or three sentences.

Footnotes, appendices, or supplementary material that engaged readers might want.

Your email address or contact details, for replies.

The mandatory unsubscribe link and identifying information for compliance.

Avoid putting your most important CTA only at the end. Most readers do not get there.

Preview text and pre-header

The pre-header is the line of text that appears next to the subject line in the inbox. Most ESPs let you set it. Many writers do not.

If you do not set a pre-header, the email client shows the first words of the email body, which are often "View this email in your browser" or your salutation. Both look like spam.

Setting a thoughtful pre-header that previews the value of the email lifts open rates by a meaningful margin. It is a five-minute fix that pays for itself.

Test on mobile

A meaningful share of newsletter opens happen on mobile. The structure that works on desktop sometimes breaks on mobile.

Common mobile-specific issues:

Headers that are too long on small screens.

Multi-column layouts that stack awkwardly.

Tables that scroll horizontally.

Long bullet lists that take up the whole screen.

Send a test to yourself. Open it on your phone. Read it as a skimmer. If anything feels off, fix the structure, not just the formatting.

The honest summary

Most newsletters get better with structural editing, not just copy editing. Lead with the answer. Use descriptive headers. Keep paragraphs short but real. Use bullets only when they are right. Bold sparingly. Place CTAs where skimmers will find them. Test on mobile.

If you remember nothing else: assume your reader will skim. Write for the skimmer. Reward the careful reader.

For more on the writing side, see how to write a newsletter that people actually read.

Cheers.