Headings and Content Structure for Search

Concept

After the title, headings are the strongest structural signal on a page. They tell a crawler what the document is about, how it is divided, and which part answers which question.

They serve the reader the same way, which is why heading advice for SEO and heading advice for accessibility are identical.

The rules

One h1, describing this page

<h1>Design course fees for 2026</h1>

Not the site name. Not a tagline. The subject of this specific document.

No skipped levels

<!-- broken outline -->
<h1>Design course</h1>
<h4>Fees</h4>

<!-- correct -->
<h1>Design course</h1>
<h2>Fees</h2>

Headings describe the section beneath them

<!-- says nothing -->
<h2>More information</h2>
<h2>Details</h2>

<!-- says what follows -->
<h2>Fee structure by year</h2>
<h2>Documents required for admission</h2>

Real headings, not styled text

<!-- invisible to the outline -->
<div class="section-title">Fees</div>
<p><strong>Fees</strong></p>

<h2>Fees</h2>

Writing for featured snippets

A featured snippet is the answer box above the ordinary results. It is frequently assembled from a heading and the content immediately below it, which makes the format directly controllable.

Question as heading, answer immediately below

<h2>What documents do I need to apply?</h2>
<p>You need a photocopy of your identity card, two passport photographs and
   the original fee receipt. All three must be submitted together.</p>

The answer comes first, in one or two sentences, before any elaboration. A snippet is typically forty to sixty words - write the direct answer in that space and expand afterwards.

Lists for steps and sets

<h2>How to apply for a duplicate marksheet</h2>
<ol>
  <li>Fill in form D-2 at the examination office.</li>
  <li>Pay the fee at counter three and keep the receipt.</li>
  <li>Submit the form with the receipt attached.</li>
  <li>Collect the marksheet after ten working days.</li>
</ol>

Ordered lists under a how to heading are a common source of list snippets.

Tables for comparisons

<h2>Fee structure by course and year</h2>
<table>
  <caption>Annual fees in rupees, 2026 intake</caption>
  <thead>
    <tr><th scope="col">Course</th><th scope="col">Year 1</th><th scope="col">Year 2</th></tr>
  </thead>
  <tbody>
    <tr><th scope="row">Design</th><td>48,000</td><td>52,000</td></tr>
  </tbody>
</table>

Structuring a page around questions

Take the questions people actually ask about a subject and make each one a heading:

<h1>Design course at Riverside College</h1>

<h2>What does the design course cover?</h2>
<h2>How long is the course?</h2>
<h2>What are the fees?</h2>
<h2>Who can apply?</h2>
<h2>When do applications close?</h2>
<h2>What can I do after the course?</h2>

Each becomes a candidate for a snippet on its own query, and the page becomes genuinely easier to use. Sources for the questions: the People also ask box in search results, your own support enquiries, and the Search Console query report.

Content length

There is no target word count, and claims that longer pages rank better confuse correlation with cause. Thorough pages tend to be longer because thoroughness takes words - not the other way round.

The right length is the length that answers the question completely and stops. Padding a four hundred word answer to fifteen hundred makes the page worse.

Content the page needs regardless

• An author and a date. Both for readers and as a trust signal.
• An update date when the content changes materially, and honestly.
• Links to sources where claims need support.
• Internal links to related pages, in context.
• Specifics. Numbers, dates, names and examples separate a real page from a generic one.

<article>
  <header>
    <h1>How to read a bus timetable</h1>
    <p>By Meera Iyer</p>
    <p>Published <time datetime="2026-03-02">2 March 2026</time>,
       updated <time datetime="2026-08-11">11 August 2026</time></p>
  </header>
  ...
</article>

What to avoid

• Keyword stuffing. Repeating a phrase unnaturally is detected and discounted.
• Hidden text. Text hidden with CSS for crawlers is a policy violation.
• Thin pages. A page per keyword variation, each with two sentences, competes with itself.
• Duplicate content across pages. Consolidate into one good page.
• Headings chosen for size.

Important rules

• One h1, no skipped levels.
• Headings must be real heading elements.
• The direct answer goes immediately after the heading.
• Lists and tables are eligible for their own snippet formats.
• Word count is not a target.
• Say who wrote it and when.

Common mistakes

• Vague headings such as More information.
• Heading levels chosen by font size.
• Burying the answer three paragraphs below its heading.
• Padding content to hit a word count.
• Publishing a separate thin page for each keyword variation.
• Bold text standing in for headings.

Best practices

• Write the heading outline first; the content follows it.
• Phrase headings as the questions readers ask.
• Answer in the first two sentences, then elaborate.
• Use lists for steps and tables for comparisons.
• Read the headings alone and check they describe the page.
• Add author and date to every substantial page.

Practice

1. List ten questions people ask about a subject you know and turn each into a heading.
2. Take a section where the answer is buried and move it directly under the heading.
3. Convert a paragraph describing four steps into an ordered list.
4. Read the headings of one of your pages aloud. Do they describe the page?