Free Text Paragraph Rules: When Plain Prose Is Correct

Free text is ordinary prose that carries a continuous explanation, argument, narrative, or transition. It is the fallback content form, not the default choice: before writing a paragraph, confirm that the passage does not have a more precise job already represented by a named element.

The practical rule is simple: choose by purpose before choosing by appearance. A paragraph that defines the page’s central term is still a definition, even if plain prose would look acceptable. A paragraph containing three ordered actions is still a procedure. Use free text only when its value comes from connected reasoning that should be read as sentences in sequence.

Why this element matters

Paragraphs are flexible, which is exactly why they are easy to misuse. Almost any material can be forced into prose: instructions can be buried in a sentence, comparison criteria can be scattered across four paragraphs, and warnings can be softened into an aside. The words may remain grammatically correct while the content becomes harder to scan, extract, maintain, and verify.

A named element makes a promise about purpose. A step list promises an ordered procedure. A warning promises a material risk. A comparison table promises consistent attributes across alternatives. Free text makes a narrower promise: the relationship between sentences matters more than a repeated field or independently scannable unit. Readers should be able to follow a line of thought from claim to reason, example, qualification, and conclusion.

That continuous shape also helps search and answer systems. A self-contained paragraph can be extracted as a passage when it names its subject, states a complete claim, and keeps necessary qualifications nearby. But machine extractability is not a reason to turn every sentence into a tiny paragraph. Fragmenting an argument removes the relationships that make the claim accurate.

The governing element writing rules therefore give typed elements precedence over free text. This page adds the fallback rules: how to decide that prose is genuinely correct, how long its paragraphs should be, and how to keep one coherent idea in each paragraph.

When to use it

Use free text when the passage performs one of four jobs:

• Explanation: it develops why or how something works through connected reasoning.
• Analysis: it interprets evidence, tradeoffs, causes, or implications that cannot be reduced to independent cells.
• Narrative: it reports events or a case in an order whose meaning depends on context and causality.
• Transition: it connects two sections by resolving the previous point and framing the next one.

Before drafting, run the precedence check:

1. State the passage’s primary job as a verb: define, answer, warn, instruct, compare, summarize, prove, quote, recommend, or explain.
2. Search the element library for that job and close synonyms.
3. If a named element matches the primary job, use it and follow its contract.
4. If no named element matches and sentence-to-sentence reasoning is the value, use free text.
5. If the passage contains both, place the typed element first or beside the prose it governs; do not hide the typed purpose inside the paragraph.

For example, “Select Export, choose CSV, then download the file” is not a paragraph merely because it fits on one line. Order affects the outcome, so it belongs in a step list . “CSV preserves tabular values but not formulas, so it is appropriate for importing results into another system” is explanatory reasoning and belongs in prose.

Do not use free text to avoid the work of modeling content. Parallel choices belong in a bullet list ; a central term may need a definition box ; repeated attributes across alternatives belong in a comparison table . Styling a paragraph with bold labels does not make those relationships explicit.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Where to place it

Place free text wherever the page needs reasoning between structural elements. The usual sequence is heading, opening paragraph, supporting element, then interpretation. The opening paragraph establishes the section’s claim and scope before a reader encounters evidence, examples, or controls. A paragraph after a table or figure should explain the conclusion rather than repeat every value.

Free text may also connect adjacent elements. A transition after a definition can explain why the distinction matters before the page moves into examples. A paragraph before a procedure can establish the prerequisite or decision context, but actual prerequisites and actions must remain in their named fields or elements.

Do not place an orphan paragraph between a heading and the element that directly fulfills that heading. If the heading says “Steps,” begin with the step element unless a short setup is essential. Do not place prose between a warning and the action it governs, between a claim and its citation, or between table rows. Placement must preserve the relationship that justified the chosen type.

At page level, avoid long runs of unbroken prose. Three to five paragraphs may form a coherent subsection, but a new subtopic needs a descriptive heading. The fix for visual monotony is better information architecture, not random callouts or one-sentence paragraph spam.

Anatomy

A strong free text paragraph has four logical regions, even though they render as one ordinary <p> element:

1. Topic sentence: names the subject and makes the paragraph’s controlling claim or move.
2. Development: gives the reason, mechanism, evidence, or relevant detail.
3. Example or qualification: makes the claim concrete or sets its boundary when needed.
4. Handoff: completes the thought or creates a natural connection to what follows.

Not every paragraph needs four separate sentences. A 42-word paragraph may combine its claim and reason in the first sentence, then use the second for a concrete boundary. The anatomy describes logical work, not a fill-in-the-blanks formula.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Design examples

Free text should inherit the site’s normal article typography. Its variants are based on editorial function, not decorative treatment.

Standard explanatory paragraph

Use a comfortable measure, normal body size, and ordinary spacing. It should feel quieter than callouts, tables, and headings because it carries the connective tissue of the page.

Short transition

A transition may be 15–30 words when it closes one idea and names the next. It should not be enlarged, centered, or styled as a quotation merely because it is short.

Qualified analysis

An analytical paragraph may reach 90–120 words when separating it would detach a conclusion from its assumptions or limitations. The longer form still needs one controlling idea and readable line length.

Narrow viewport

On mobile, paragraphs must wrap without horizontal scrolling, preserve link visibility, and avoid lines so wide or indented that the reading column collapses.

Parameters

Free text has no custom component attributes. Its contract is editorial and maps to native paragraph markup.

The target band is 30–90 words. A deliberate transition may use 15–30 words. A paragraph may extend to 120 words only when one claim needs an attached qualification, evidence boundary, or causal chain. These are review bands, not automatic pass/fail counts: coherence takes priority within the hard ceiling.

Free text does not accept a variant, color, icon, title, or columns parameter. If the author needs those fields, the passage probably has a different semantic purpose and must repeat the precedence check.

Syntax and code examples

Because free text is native document content, portable Markdown needs no directive:

Caching reduces the work required to serve repeated requests, so it can improve response time without changing the page itself. The useful cache duration depends on how often the underlying content changes.

Hugo receives the same Markdown paragraph. Do not wrap it in a shortcode merely to expose ordinary prose:

Caching reduces the work required to serve repeated requests, so it can improve response time without changing the page itself. The useful cache duration depends on how often the underlying content changes.

WordPress stores equivalent prose in its native paragraph block:

<!-- wp:paragraph -->
<p>Caching reduces the work required to serve repeated requests, so it can improve response time without changing the page itself. The useful cache duration depends on how often the underlying content changes.</p>
<!-- /wp:paragraph -->

The absence of a custom wrapper is intentional. Importers should preserve the paragraph boundary, inline links, emphasis, code spans, and language direction. They must not concatenate adjacent paragraphs into one block or split every sentence into a separate block.

When a paragraph’s purpose changes during editing, change its representation. A sequence discovered inside prose becomes a step element; comparable facts become a table; a material caveat becomes the appropriate warning. Source simplicity never takes precedence over semantic accuracy.

Examples

Good: one idea developed through reason and boundary

A canonical URL consolidates duplicate page signals only when crawlers can access the declared target. If the target is blocked or redirects elsewhere, the declaration becomes ambiguous, so crawlability must be checked before the canonical is treated as effective.

This paragraph controls one idea: a canonical declaration depends on an accessible, consistent target. The second sentence does not introduce a new topic; it explains the failure condition and the resulting check. Converting it to bullets would weaken the causal relationship.

Good: concise transition

The audit identifies which templates fail. The next step is to separate shared template defects from page-specific exceptions.

The transition closes the diagnostic stage and opens the classification stage. Its brevity is purposeful, and it does not pretend to be a summary or instruction set.

Bad: several semantic jobs hidden in prose

Structured data helps machines understand a page. Product schema includes price and availability. Open the template, add the fields, validate the markup, and publish it. Be careful because invalid prices can mislead customers. Basic plans cost less than Pro plans.

This paragraph contains an explanation, a field specification, four ordered actions, a warning, and a comparison. No single topic sentence can govern all five jobs. It must be decomposed into explanatory prose plus the appropriate named elements.

Bad: artificial paragraph fragmentation

A content inventory records the pages a site currently publishes.

It also records ownership.

It may include performance data.

This information supports audit decisions.

Each sentence is related to the same controlling idea. Splitting them creates false emphasis and forces the reader to reconstruct the relationship. Combine them: “A content inventory records published pages, ownership, and relevant performance data so audit decisions use one accountable source.”

Bad: one paragraph containing two unrelated ideas

Review the query sample before changing the prompt set, because a narrow sample can produce a misleading baseline. The report card should also use the approved brand colors.

The second sentence changes from measurement validity to presentation. It needs a separate paragraph only if the design detail is relevant; otherwise it should be removed or placed in the appropriate design specification.

Schema markup and accessibility

Free text has no dedicated Schema.org type. It remains visible content inside the page’s truthful Article, TechArticle, Product, FAQPage, or other supported page-level markup. Do not wrap ordinary paragraphs in invented JSON-LD objects, and do not repeat the entire paragraph in structured data merely to make it look machine-readable.

Use semantic <p> elements for paragraphs. Do not simulate them with repeated <div> elements, line breaks, text in images, or CSS-generated content. Preserve the source order because assistive technologies and extraction systems rely on the same sequence to recover the argument.

Links must describe their destination without turning the paragraph into a chain of competing anchors. Emphasis must remain meaningful without color. Inline code should use semantic code markup. If the language or text direction changes within a paragraph, mark that change in HTML rather than asking the reader or screen reader to infer it.

Readable presentation matters, but authors should not hard-code it. The renderer owns line length, font size, line height, spacing, contrast, reflow, and focus treatment. At 200% zoom and on a narrow viewport, text must wrap without loss or horizontal scrolling. Paragraph meaning must survive when all custom styling is removed.

Writing rules

Reason before rule: paragraphs work when readers can hold one subject and one logical move in working memory. Therefore, write one idea per paragraph. “Idea” means a controlling claim plus the sentences required to explain, support, exemplify, or qualify it—not one sentence and not one keyword.

Start a new paragraph when any of these changes:

• The subject or actor changes.
• The paragraph moves from explanation to instruction, comparison, warning, or recommendation.
• The time frame or stage of a process changes.
• The argument moves from claim to a genuinely separate implication.
• A new audience, condition, or exception needs its own controlling sentence.

Keep sentences in a deliberate order: claim before detail, reason before rule, general case before exception, and evidence before conclusion unless the post type explicitly requires a direct answer first. Name the subject instead of relying on vague openings such as “This,” “It,” or “They” when the paragraph may be extracted from context.

Use the paragraph-length bands as diagnostic signals:

• 15–30 words: a transition, deliberate emphasis, or compact answer. Repeated short paragraphs create choppy rhythm and false importance.
• 30–90 words: the normal band for one developed idea. Most explanatory prose belongs here.
• 90–120 words: a justified exception for attached evidence, assumptions, or qualifications. Review every sentence for unity.
• More than 120 words: split, restructure, or convert the material unless a quoted or legally controlled passage must remain intact.

Length alone cannot determine structure. Two 55-word paragraphs should be combined when the second merely continues the first idea. One 70-word paragraph should be split when it switches from explaining a problem to prescribing actions. Run the purpose test before the word-count test.

Prefer concrete nouns, active verbs, and explicit relationships such as “because,” “therefore,” “however,” and “only when.” Remove throat-clearing phrases, repeated H2 wording, empty promises about what the article will cover, and conclusions that only restate the opening. A paragraph should add reasoning, not occupy space between components.

Post types that use it

Every long-form page may need prose, but these post types depend on it for specific connective work. Inclusion in postTypes does not make free text a required slot; the precedence check still applies to every passage.

Commercial and reference pages can also use free text when reasoning is needed. Product descriptions, legal disclosures, review summaries, and pricing conditions are not automatically “free text” merely because they appear as paragraphs; their governing page and element contracts still apply.

QA checklist

Before publication, verify every item:

• The passage passed the precedence check and no named element expresses its primary purpose more accurately.
• Its purpose is explanation, analysis, narrative, or transition.
• One controlling idea governs every sentence.
• The first sentence names the subject and establishes the paragraph’s move.
• Reasons appear before rules, and qualifications remain attached to the claims they limit.
• A subject, actor, time-frame, audience, or logical-purpose change starts a new paragraph.
• Normal paragraphs fall within 30–90 words; shorter and longer bands have a clear editorial reason.
• No paragraph exceeds 120 words unless controlled quoted or legal text must remain intact.
• Instructions, warnings, comparisons, definitions, summaries, evidence modules, and repeated fields use their named elements.
• Short paragraphs do not create a choppy stack or manufacture visual emphasis.
• Long paragraphs have not hidden a list, sequence, table, or second idea.
• Pronouns and deictic words remain clear if the paragraph is extracted from its surroundings.
• Links are descriptive, limited, valid, and represented in frontmatter.
• The source uses native paragraphs without an unnecessary shortcode or custom wrapper.
• Paragraph order and meaning survive without visual styling and at narrow or zoomed layouts.
• Screenshot comments identify future captures without referencing nonexistent rendered assets.

FAQ

Is free text the default content element? No. It is the fallback after the passage passes the precedence check. If a named element matches the primary purpose, that element wins even when a paragraph would be easier to type.

How long should a free text paragraph be? Most should contain 30–90 words. Use 15–30 words for a purposeful transition and 90–120 only when one argument needs its qualification or evidence attached. Split or remodel anything longer.

Does one idea per paragraph mean one sentence per paragraph? No. A coherent idea can require a claim, reason, example, and qualification. Sentence count is not the test; a change in subject or logical purpose is.

When should prose become a list or table? Use a list for parallel independent items, a step list when order affects the outcome, and a table when the same attributes must be compared. Keep prose when the relationships between sentences carry the meaning.

Does free text need special schema markup? No. Use semantic paragraph markup inside the page’s truthful schema type. Clear source order and self-contained writing provide more value than invented structured data.

Plain prose earns its place when connected reasoning is the content. Run the precedence check first, keep one idea within a justified length band, and let every typed purpose use its named element.