Heading & Content Structure
Heading structure organizes content into a hierarchy that helps both users and search engines understand the page's main topics and subtopics. A clear heading structure improves readability, accessibility, and SEO.
This lesson covers the seven structure areas (leaves 4.2.1–4.2.7): H1 optimization, H2 and H3 structure, intro paragraph optimization, section hierarchy, content scannability, table of contents and jump links, and query-answer alignment.
After this lesson you can organize page content with a clear heading hierarchy, write scannable content, and align sections with user queries to improve readability, accessibility, and SEO.
Why This Matters
- Headings provide the outline of your page content. Search engines use them to understand what each section covers.
- Well-structured content is more scannable, improving user engagement and time on page.
- Clear section hierarchy makes it easier for Google to pull relevant sections for featured snippets.
H1 Optimization
The H1 heading is the main title of the page. Every page should have exactly one H1.
H1 best practices:
| Practice | Recommendation |
|---|---|
| One H1 per page | Only one H1; all other headings use H2-H6 |
| Include primary keyword | Ideally near the beginning |
| Match or closely relate to the title tag | Consistency between <title> and H1 |
| Descriptive, not generic | "How to Reduce Cart Abandonment" not "Article" |
| Front-loaded with key term | Primary concept early in the H1 |
| Unique per page | Every page should have a distinct H1 |
Common H1 mistakes:
| Mistake | Example | Fix |
|---|---|---|
| Multiple H1s | Two or more <h1> elements | Use a single H1, downgrade others to H2 |
| Missing H1 | No <h1> on the page | Add an H1 that describes the page purpose |
| H1 in logo | Logo image with H1 tag | Use H1 for the page title, not the logo |
| H1 hidden off-screen | CSS-hidden H1 for "SEO purposes" | H1 should be visible and useful |
| H1 too long | Over 70 characters | Keep H1 descriptive but concise |
H2 and H3 Structure
H2 and H3 headings organize the page into logical sections and subsections.
Heading hierarchy rules:
H1: Page Title
├── H2: Main Section 1
│ ├── H3: Subsection 1.1
│ ├── H3: Subsection 1.2
├── H2: Main Section 2
│ ├── H3: Subsection 2.1
│ └── H3: Subsection 2.2
└── H2: Main Section 3
Heading hierarchy organizes content so users and search engines can understand the page's main topics and subtopics. Never skip levels (H1 → H3 without H2) as it creates confusing structure and hurts accessibility.
H2/H3 best practices:
| Practice | Recommendation |
|---|---|
| Semantic hierarchy | Do not skip levels (H1 → H3 without H2) |
| Descriptive text | Each heading should tell the reader what the section covers |
| Include related keywords | Use variations and semantic terms in headings |
| Scannable | A user should understand the page content by reading only the headings |
| Consistent formatting | Use the same heading style for similar-level headings |
| Question format | Use question format for FAQ sections or sections that answer queries |
How many headings to use:
- Short content (300-500 words): 2-3 H2s, optional H3s.
- Medium content (500-1,500 words): 3-5 H2s, 2-3 H3s per H2.
- Long content (1,500+ words): 5-10 H2s, 3-5 H3s per H2.
Intro Paragraph Optimization
The first paragraph (or opening section) should immediately confirm to the user that the page answers their query.
Intro paragraph best practices:
| Practice | Recommendation |
|---|---|
| Answer the query early | The first 1-2 sentences should directly address the search intent |
| Include primary keyword | Naturally, in the first 100 words |
| Front-load value | State the solution, answer, or value proposition first |
| Summary approach | Give the reader a quick answer before diving into details |
| Use bold or bullet format (optional) | Highlight the key takeaway |
Intro paragraph length:
- Short: 1-2 sentences for simple queries.
- Medium: 2-4 sentences for most queries.
- Long: A paragraph or two for complex queries.
Example:
Query: "How to reduce cart abandonment" Strong intro: "Cart abandonment affects an average of 70% of online shopping carts. Reducing it requires a combination of UX improvements, trust signals, and strategic email follow-ups. Here are 10 proven strategies to recover lost sales."
Section Hierarchy
Section hierarchy organizes the page into a logical flow of topics.
Section hierarchy principles:
| Principle | Implementation |
|---|---|
| Logical ordering | Sections should flow from broad to specific, or problem to solution |
| Progressive disclosure | Start with the most important information, then add detail |
| Clear transitions | Each section should naturally follow from the previous |
| Consistent depth | All sections of the same level should have similar depth |
| No orphan sections | Every section should belong to a parent section |
Common section ordering:
| Content Type | Section Order |
|---|---|
| How-to guides | What you need → Steps → Tips → FAQ |
| Comparison pages | Intro → Product A → Product B → Features Comparison → Verdict |
| Informational articles | Definition → Why it matters → How it works → Best practices → Examples → FAQ |
| Product pages | Problem → Solution → Features → Benefits → Pricing → Reviews |
Content Scannability
Scannable content lets users quickly find the information they need.
Scannability techniques:
| Technique | Implementation |
|---|---|
| Descriptive headings | Headings should clearly indicate what each section covers |
| Short paragraphs | 2-4 sentences per paragraph; avoid walls of text |
| Bullet points and numbered lists | Break complex information into readable items |
| Bold key terms | Highlight important terms (sparingly) |
| Short sentences | Average 15-20 words per sentence |
| White space | Adequate spacing between sections |
| Visual elements | Images, charts, pull quotes break up text |
How to test scannability:
- Read only the headings, first sentence of each section, and bold text. Can you understand the page's key points?
- Use readability tools (Hemingway, Readable) to assess reading level.
Table of Contents and Jump Links
A table of contents (ToC) with jump links improves navigation for users scanning the page.
ToC best practices:
| Practice | Recommendation |
|---|---|
| Place at the top | ToC should appear before the main content |
| Link to H2 (and occasionally H3) sections | Too many links make the ToC less scannable |
| Use anchor IDs on headings | id="section-name" on each H2 for jump links |
| Sticky ToC (optional) | A fixed ToC that follows the user on scroll |
| CSS smooth scrolling | scroll-behavior: smooth for smooth jump navigation |
When to include a ToC:
- Content longer than 1,000 words.
- Content with 4+ distinct sections.
- Guides, tutorials, and comprehensive articles.
Query-Answer Alignment
Query-answer alignment ensures each section of the page directly addresses a query the user may have.
How to align content with queries:
- Identify the primary query for the page (from keyword research).
- Break the primary query into sub-questions (what, why, how, when, where).
- Structure content sections to answer those sub-questions.
- Use question-formatted H2s where appropriate.
- Ensure the answer appears near the top of each section.
Query-answer alignment example:
Primary query: "What is email deliverability?" Sub-questions: "Why is email deliverability important?", "How is email deliverability measured?", "What affects email deliverability?", "How to improve email deliverability" Section headings: H2: What is Email Deliverability? → H2: Why It Matters → H2: How Deliverability Is Measured → H2: Common Factors Affecting Deliverability → H2: How to Improve Your Deliverability
Workflow
- Define page purpose: For each page, identify the primary query and key sub-questions.
- Design heading hierarchy: Create a heading outline before writing content.
- Write content: Follow the heading structure, ensuring each section addresses its assigned query.
- Review scannability: Read through headings and first sentences — the key message should be clear.
- Add ToC: Include a table of contents for pages over 1,000 words.
- Validate: Use a heading analyzer tool (Screaming Frog, browser extension) to check heading structure.
Common Mistakes
- Multiple H1s: Dilutes the main topic signal.
- Heading level skipping: Jumping from H1 to H3 without an H2 creates confusing structure.
Heading level skipping (H1 → H3 without H2) creates gaps in the content outline that confuse both search engine crawlers and screen readers. Always maintain a logical, sequential hierarchy.
- Headings that do not describe content: Misleading headings hurt user experience and may increase bounce rate.
- No headings at all: Long blocks of unbroken text are difficult to scan and may be treated as lower quality.
- Over-optimizing headings with keywords: Heading text must be descriptive and readable, not keyword-stuffed.
Checklist
- Every page has exactly one H1.
- H1 includes the primary keyword and matches the page title.
- H2-H3 hierarchy is logical (no skipped levels).
- Headings describe the content of each section.
- Intro paragraph answers the primary query.
- Content is scannable (short paragraphs, bullet lists, bold terms).
- Table of contents is included for long-form content.
- Each section aligns with a user query or sub-question.
- Heading structure is validated with a crawler tool.