---
title: SEO article structure: the layout that ranks and gets quoted
description: A section by section SEO article structure: title, answer paragraph, question H2s, tables, FAQ, sources and links, with a worked outline you can copy.
canonical: https://www.postbing.com/blog/seo-article-structure
published: 2026-11-16
updated: 2026-11-16
author: The Postbing Team
---

# SEO article structure: the layout that ranks and gets quoted

A good SEO article structure puts the answer at the top and lets every later section stand on its own. In order: a title that matches the search, a 40 to 70 word answer paragraph, a visible "Last updated" date, one H2 per sub question with its answer in the first two sentences, a table wherever you compare things, an FAQ, sources and related links.

Last updated: November 16, 2026

## Why structure matters more than it used to

Structure decides whether a reader, Google and an AI assistant can each find the part they need without reading the whole page. Google builds title links partly from "the main visual title, heading elements, and other large and prominent text" (Google title link documentation), and its snippets come from page content. AI answers lift single paragraphs. A page where each section answers one question is easier to quote in all three places.

None of this needs special markup. Google's AI features page says there is "no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode, and that a page only has to be indexed and eligible for a snippet. So structure here means the order and shape of your writing, not hidden tags.

This page covers the layout of a single article. For where that article sits in your wider plan, start with the [SEO blog strategy guide](/blog/seo-blog-strategy-guide).

## The structure, top to bottom

Each part has one job. If a part does not do its job, cut it rather than pad it.

| Part | Its one job | Length | Common mistake |
|---|---|---|---|
| Title tag and H1 | Match the words the searcher used | 50 to 60 characters is a safe target | Clever titles nobody searches for |
| Answer paragraph | Answer the query outright | 40 to 70 words | A story or a definition of "SEO" first |
| Last updated line | Show the reader the page is current | One line | A date that changes with no edit behind it |
| Question H2s | Cover each sub question once | 150 to 350 words each | Headings like "Overview" or "Conclusion" |
| Table | Compare three or more named things | As many rows as there are options | Bullet lists that hide the comparison |
| Steps | A task the reader will do | Numbered, one action per step | Mixing advice and steps in one list |
| FAQ | Catch the leftover questions | 3 to 6 questions, 1 to 3 sentences each | Repeating the H2s word for word |
| Sources | Back every number and claim | One line per source with a date | "Studies show" with no study |
| Related reading | Send the reader to the next step | 3 to 6 links | Ten links to loosely related posts |

The word counts are our house targets, not Google rules. Google publishes no ideal length; see [how long a blog post should be](/blog/how-long-should-a-blog-post-be) for how to judge length from the results page instead.

## Title and H1: copy the searcher's words

Use the phrase people type, in roughly the order they type it, then add what the reader gets. "Content decay: how to spot it and what to refresh first" beats "Why your old posts are quietly dying" because the first contains the query and promises an outcome.

Google's title link documentation asks for titles that are "unique, descriptive, and concise" and warns against keyword stuffing and boilerplate. Make the H1 and the title tag say the same thing. If your CMS adds the site name to the title tag, leave room for it.

## The answer paragraph: write it before anything else

The first paragraph should be the answer a busy reader would accept if they read nothing else. Write it first, before the outline, because it forces you to know what the article concludes.

Rules that keep it useful:

1. Answer in the first sentence. "Run descaler through the boiler, then flush twice with clean water" is an answer; "Regular maintenance matters" is not.
2. Use names and numbers with a unit and a date where they apply.
3. Keep it between 40 and 70 words so it can be quoted whole.
4. No openers like "In this article we will look at".

## Body sections: one question per H2

Phrase each H2 as the question or the specific topic, then answer it in the two or three sentences right under the heading. Detail, examples and caveats come after. A reader skimming headings should be able to predict every answer.

To find the H2s, list the questions a person asks after the main one. For a query like "how to descale an espresso machine", the follow ups are predictable:

- How often should you descale an espresso machine?
- Can you use vinegar instead of descaler?
- How do you descale a machine with a steam wand?
- What happens if you never descale it?

Each becomes an H2. Order them by the reader's sequence, not by how interesting they are to write. Use H3s only inside an H2, for sub steps or options.

Google's starter guide puts it plainly: "Break up long content into paragraphs and sections, and provide headings to help users navigate your pages." Keep paragraphs short. Three to four sentences is plenty on a phone.

## Tables, lists and steps: use the right shape

Pick the format from the content, not for decoration:

- **Table** when you compare three or more named things on the same attributes (price, limits, who it suits). Put units and dates in the header or cells.
- **Numbered steps** when the reader will perform a task in order.
- **Bullets** for a short set of parallel items that have no order.
- **Prose** for reasoning, trade-offs and anything that needs "because".

A comparison buried in prose is a common structural miss. If you write "Tool A costs X, while Tool B costs Y, and Tool C costs Z", that is a table waiting to happen.

## Dates, sources and the trust layer

Show a visible "Last updated" date and keep it honest. Google's byline date documentation asks for a user-visible date labeled "Published" or "Last updated", and for structured data dates (datePublished, dateModified) that match it. Its helpful content guidance asks, as a warning sign: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" Only move the date when the page changed.

End with a Sources list. Every price, statistic and third party claim gets a line: the page name, what it supports, and the date you checked it. If you cannot point to a source, take the number out.

## The FAQ block: what it is for now

Keep a short FAQ, but for readers and AI answers, not for a search feature. Google stopped showing FAQ rich results in May 2026 and removed the documentation in June 2026 (Google Search Central updates page). The section still earns its place by catching follow up questions the body did not cover.

Write three to six real questions, answer each in one to three sentences, and make sure the answers agree with the body. If an answer contradicts a section above it, fix the body, not the FAQ.

## A worked outline you can copy

Here is the full skeleton for an article targeting "how to descale an espresso machine", in the order it appears on the page:

1. Title: How to descale an espresso machine (and how often to do it)
2. Answer paragraph: the method in one line, the usual frequency, and the one thing not to do.
3. Last updated: November 16, 2026
4. H2: What you need (short list)
5. H2: How to descale, step by step (numbered steps)
6. H2: How often should you descale? (answer, then a table by water hardness)
7. H2: Descaler vs vinegar vs citric acid (table: cost, risk to seals, smell)
8. H2: Machines with a steam wand or dual boiler (differences only)
9. H2: Signs you waited too long
10. FAQ: three to five leftover questions
11. Sources: manufacturer manuals and any test you cite, with dates
12. Related reading: the cleaning guide pillar and two sibling guides

Before writing, put this outline into a brief so the writer and the editor agree on it. The [SEO content brief guide](/blog/how-to-write-an-seo-content-brief) shows what else goes in that brief, and the [SEO blog post checklist](/blog/seo-blog-post-checklist) covers the pre-publish checks.

## Internal links inside the structure

Place one link to the topic's pillar in the first third of the article, then link to sibling articles where a reader would naturally want them, using anchors that describe the destination. Keep it under about 15 internal links. The [internal linking strategy guide](/blog/internal-linking-strategy-guide) covers how to plan these across a whole site.

If you publish with Postbing, this structure is the default output: each article ships with meta title and description, FAQs, JSON-LD schema and internal links, and you set the link rules per site. See how Postbing publishes to your CMS.

## FAQ

### What is the best structure for an SEO article?
Title that matches the query, a 40 to 70 word answer paragraph, a visible last updated date, one H2 per sub question with the answer first, tables for comparisons, a short FAQ, sources and related links.

### Should every H2 be a question?
No. Phrase the H2 as the question or as the specific topic it answers. What matters is that the first two or three sentences under it answer that question directly.

### Do I still need an FAQ section if FAQ rich results are gone?
It is still worth keeping for readers and AI answers that lift short question and answer pairs. Google stopped showing FAQ rich results in May 2026, so do not expect a search feature from it.

### Do I need special schema to appear in AI Overviews?
No. Google's AI features documentation says no special schema.org markup is needed; the page must be indexed and eligible for a snippet. Article schema is still useful for dates and authorship.

### How many headings should an article have?
Enough that each covers one question. As a house rule we aim for at least one H2 per 250 to 400 words, and never headings like "Overview" that say nothing.

## Sources

- [Google: Influencing your title links](https://developers.google.com/search/docs/appearance/title-link): title sources and "unique, descriptive, and concise" guidance, accessed 16 November 2026
- [Google: SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide): headings and paragraphs guidance, accessed 16 November 2026
- [Google: AI features and your website](https://developers.google.com/search/docs/appearance/ai-features): no special schema or files needed for AI Overviews and AI Mode, accessed 16 November 2026
- [Google: Influencing byline dates](https://developers.google.com/search/docs/appearance/publication-dates): visible "Last updated" date and matching structured data, accessed 16 November 2026
- [Google: Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content): warning about changing dates without substantial changes, accessed 16 November 2026
- [Google Search Central: documentation updates](https://developers.google.com/search/updates): FAQ rich result deprecation (May 2026) and documentation removal (June 2026), accessed 16 November 2026

## Related reading

- [SEO blog strategy: the whole plan on one page](/blog/seo-blog-strategy-guide)
- [How to write an SEO content brief](/blog/how-to-write-an-seo-content-brief)
- [SEO blog post checklist before you publish](/blog/seo-blog-post-checklist)
- [How long should a blog post be?](/blog/how-long-should-a-blog-post-be)
