Paragraph breaks are structural decisions, not pauses
Paragraph breaks partition ideas, not prose rhythm
I see this constantly: writers breaking paragraphs when they "feel" like taking a breath, or worse, when they think the block looks too long on screen. That's aesthetic timidity masquerading as structure. A paragraph break is a semantic boundary—it tells the reader "this unit of meaning is complete, the next unit begins now." If you're breaking for visual comfort or imagined pacing, you're undermining your own information architecture at the sentence level.
The test is simple: can you articulate what changed between the paragraph you just ended and the one you're starting? If the answer is "nothing, it just felt long," you've made a formatting choice, not a structural one. Formatting choices are the domain of your stylesheet. Your job as a writer is to mark where one thought-unit ends and another begins.
One claim per paragraph, actually
The "one idea per paragraph" rule gets taught everywhere and ignored constantly. Here's why it fails in practice: writers don't define "idea" with enough precision. An idea isn't a topic. It's not a subject area. It's a defensible claim or a discrete observation.
Consider: "Our CMS supports custom fields. You can add text fields, date pickers, and relationship fields. Most teams use five to eight custom fields per content type." That's three sentences, one topic, three separate claims. The first asserts capability. The second enumerates options. The third quantifies typical usage. Each could anchor its own paragraph if you're building an argument or explanation that needs that level of granularity.
Most writers would lump those together because they're "about custom fields." But if your reader needs to extract the quantification claim specifically, you've just made them parse two irrelevant sentences first. That's friction you chose.
White space is not the same as structure
Yes, shorter paragraphs improve scannability. Yes, dense blocks intimidate readers. But if you're breaking paragraphs to "add air" without changing the informational payload, you're applying a visual treatment that belongs in CSS, not in your content model.
The correct fix for a six-sentence paragraph that feels too dense is not to split it arbitrarily at sentence three. The correct fix is to ask whether those six sentences actually constitute a single claim or observation. If they do, keep them together and let your typography handle the visual load. If they don't, you've identified a structural problem that breaking mid-thought won't solve—you need to re-sequence the sentences so each paragraph has a clear job.
This matters more on small sites than anywhere else, because you don't have the luxury of paginating concepts across multiple articles. Your 600-word service page needs to carry four or five distinct ideas, and the paragraph breaks are the only structural markup you have to keep them separable. Waste those breaks on aesthetics and you've collapsed your hierarchy.
Break before you pivot, not after
Here's the practical heuristic: when you write a sentence that changes direction, introduces a contrasting point, or shifts from abstract to concrete (or vice versa), that sentence starts a new paragraph. Not the sentence after it. Not two sentences later when the block "looks long." Right there, at the pivot.
Example: "Most teams export content as JSON for version control. But raw JSON diffs are unreadable for non-technical editors. We use a diffing tool that renders changes in plain language." That second sentence is the pivot—it's the "but" that changes the claim from capability to limitation. It must start a new paragraph, because it's marking a new informational unit.
If you're writing headings before sections, you already know where your major pivots are. Paragraph breaks are just the fine-grained version of the same structural discipline. The heading says "this section covers X." The paragraph break says "this sub-claim within X is complete."
Your CMS doesn't care, but your readers do
No CMS I know of enforces paragraph coherence. You can mash Enter whenever you want. But every reader—especially the Friday-afternoon skimmer—is trying to extract meaning by scanning the first sentence of each paragraph. If your breaks are arbitrary, those first sentences won't form a coherent outline of your argument. The reader has to slow down and read linearly, which on the web means they leave.
Treat paragraph breaks as the smallest structural unit you control. Decide what each paragraph asserts before you decide where it ends. The visual rhythm will follow if your claims are clear. The inverse is not true.