New format
How to structure an article so people (and search) can follow it
Article structure is the logical frame: block order, headings, and how paragraphs lead to a takeaway. There’s no universal template for every brief — you fit the frame to the goal, length, and page format.
Here’s why structure matters for readers and search, how heading levels work, when you can skip H2s, and how not to clone the same skeleton everywhere. Writing the full article is a separate process; site IA (sections, URLs) lives in the SEO site structure guide.
What text structure means
Structure is the logical base of the piece: internal order and how paragraphs connect. You usually sketch it before typing and revise while writing; in the end it looks like a table of contents.
There’s no perfect specimen. A good frame helps the brief, but blind-copying someone else’s outline for another job hurts. Stay creative: logic and usefulness first — not schema alone.
Who it’s for — and why it matters
A wall of text without anchors is harder for readers: finding a fragment and seeing where the article goes is tougher. Headed blocks let people scan and read selectively.
Search cares about clarity and headings that match the content. H1–H6 markup separates headings from paragraphs. That isn’t a ranking guarantee — ranking is broader than “put an H2 with a keyword.”
Heading levels
H1 is the title of the whole piece (usually one per page). H2s are major meaning chunks. H3s refine inside an H2 and keep subsections clear.
How many levels you need depends on length and topic. Big guides and roundups tolerate a deeper grid; short posts don’t.
H4–H6 are rare in practice: visually noisy, confusing for readers, and often excess for SEO.
Practical minimum:
- one H1 with the page’s essence
- H2s for the reader’s big questions
- H3 only if a block truly splits
- heading = content — no clickbait that fights the text
When a lighter structure works
Not every text needs a full H2/H3 grid. The call depends on length, purpose, and page template (layout sometimes limits splitting).
Short descriptions, teasers, cards, and mini-tips often live on paragraphs, lists, and emphasis without subheads — if the main idea stays clear.
In chaos without anchors you can lose the point. Then at least lists and a clear CTA beat a wall of sentences.
Recommendations
Build the frame before the draft — easier to highlight what matters and not wander off topic.
Don’t clone one template across every piece: sameness tires readers. Keep the logic; change delivery for the format (how-to, review, opinion, case).
Tied to the writing process: outline → draft → revise structure if the line of thought changed.
Remember:
- structure is for reading and clarity — not an SEO checkbox
- H1–H3 is usually enough
- short texts can live without H2
- a heading must match its block
- site and article are different structure levels
FAQ
Is article structure the same as a table of contents?
Almost. The pre-writing outline becomes the TOC after you write. The TOC is the finished structure.
Are H2s required in short copy?
Not always. Up to about 1–1.5k characters, paragraphs, lists, and emphasis often suffice — if the idea is already clear.
How many heading levels do I need?
Usually H1 + H2, plus H3 when needed. H4–H6 on landings and blogs are rarely justified — they confuse the eye.
Do keywords in headings help rankings?
Headings should match the block’s meaning and intent. Stuffing SEO phrases without usefulness doesn’t replace a good answer.
Who decides hierarchy — SEO or the writer?
Together. The writer owns reading logic; SEO owns intent and sensible markup. Don’t break meaning for a schema.
How is this different from site structure?
Here — the frame of one text. Site structure is sections, URL hierarchy, and internal links.
Do I need one template for the whole blog?
A reference frame helps; cloning every article doesn’t. Readers tire of identical blocks.
Articles scanning poorly — or H2s just for “SEO”?
We’ll rebuild the outline around reader questions so headings match the blocks — not keyword stuffing.
Discuss the task
