Most people don't read web pages from top to bottom. They scan headings, jump to the part they need, and leave if they can't find it quickly. Clear structure helps those readers, helps people using screen readers, and helps search engines understand what each part of a page covers. This lesson explains how to use headings properly, how to organise content, and which formats work best for different kinds of information.

How headings work in HTML

HTML has six heading levels, h1 to h6. They form an outline of the page, like a table of contents:

h1  Bathroom Renovations in Adelaide
  h2  What's included in a bathroom renovation
    h3  Demolition and waterproofing
    h3  Tiling, fixtures and finishing
  h2  How much does a bathroom renovation cost?
    h3  Small bathroom (under 5 m²)
    h3  Family bathroom
  h2  How long does it take?
  h2  Frequently asked questions

The H1

The H1 is the page's main heading. It should state clearly what the page is about and usually agree with the title element (it doesn't need to be identical). Most pages should have one H1. HTML technically allows more, and Google has said multiple H1s aren't a problem in themselves, but a single clear H1 is simpler for users and assistive technology.

H2s and H3s

  • H2s mark the main sections.
  • H3s divide an H2 section into sub-topics.
  • Go deeper (H4–H6) only when the content genuinely needs it, such as long technical documentation.
  • Don't skip levels for styling (jumping from H2 to H4 because it looks smaller). Use CSS to style headings and keep the levels logical.
  • Don't use headings just to make text big or for things like phone numbers in the header. That creates a confusing outline.

Write useful headings

A heading should tell readers what the section answers. Compare:

Weak Better
Pricing info How much a website audit costs
Section 2 What happens on the first visit
Overview Who needs a commercial building inspection
More details Do I need council approval for a deck in Victoria?

Good headings often come from real questions discovered in keyword research: People also ask boxes, Search Console queries, sales calls and support emails. Phrasing a heading as a question and answering it directly underneath helps readers and can help search engines extract a concise answer.

Accessibility: why structure matters beyond SEO

Screen reader users commonly navigate by jumping between headings, much like sighted users scanning. A logical heading outline makes a page usable; a broken one makes it frustrating. The Web Content Accessibility Guidelines (WCAG) require that headings and labels describe their topic or purpose and that structure is conveyed in the markup. In Australia, the Disability Discrimination Act applies to websites, and government sites follow WCAG 2.x; in the UK, public sector bodies have legal accessibility obligations; and in the US, the ADA is frequently applied to websites. Good structure is a legal and ethical issue as well as an SEO one.

Organising the page

Lead with the answer

Put the most important information first, sometimes called the inverted pyramid. If someone searches "how long does a bathroom renovation take", answer it in the first lines ("Most bathroom renovations in Adelaide take 3–5 weeks, depending on…"), then explain the detail. Don't make people scroll past a long introduction about your company history.

Match structure to intent

  • Service pages: what the service is, who it's for, what's included, price guidance, service area, process, proof (reviews, projects, accreditations), FAQs, a clear call to action.
  • Product pages: key benefits, specifications, sizing, delivery and returns, reviews.
  • Guides: a short answer, then steps or sections, examples, and next steps.
  • Comparisons: criteria, a comparison table, verdicts for different needs.

Look at what the top-ranking pages for your query include. It shows what searchers expect, though you should aim to cover it better, not copy it.

Use the right format for the information

  • Tables for data people compare: prices, specifications, plans, opening hours. Use real HTML tables, not images of tables, so the content is readable by search engines and screen readers.
  • Numbered lists for steps that happen in order.
  • Bulleted lists for unordered items such as features or requirements.
  • Short paragraphs (two to four sentences) for explanations.
  • Images, diagrams and video where they explain better than text, such as before-and-after photos or a wiring diagram, with descriptive alt text.

Long pages

For long guides, add a table of contents with jump links to each H2. It helps readers navigate, and Google sometimes shows these jump links in search results. Keep the page focused, though: length is not a ranking factor in itself. A page should be as long as it needs to be to fully meet the need, and no longer.

Avoid padding and repetition

A common mistake is writing to a target word count or repeating the same point with keyword variations ("Our Sydney plumbers are the best plumbers in Sydney for plumbing in Sydney"). This makes pages longer but worse. Google's guidance on helpful content asks whether content provides substantial value compared with other pages and whether it was written mainly to attract search visits. Cut anything that doesn't help the reader.

Worked example: restructuring a service page

A Hobart pest control company's "Termite Inspections" page was one 900-word block of text with an H1 of the company name and bold sentences instead of headings. The rewrite:

  • H1: "Termite Inspections in Hobart"
  • An opening paragraph with the price range, inspection time and report turnaround.
  • H2s: "What we check", "How much a termite inspection costs", "How often you should inspect" (citing the relevant Australian Standard, AS 3660), "What happens if we find termites", "Areas we service", "FAQs".
  • A table comparing standard and pre-purchase inspections.
  • A clear "Book an inspection" button after the pricing section and at the end.

The word count barely changed, but time on page and enquiries improved, and the page began ranking for several question queries it hadn't before.

Checking your structure

You don't need special software to check a page's outline:

  • Browser tools: free accessibility extensions such as WAVE or HeadingsMap display the heading outline of any page, highlighting skipped levels and empty headings.
  • Lighthouse in Chrome DevTools includes accessibility checks for heading order.
  • A crawler (Screaming Frog, Sitebulb or your SEO tool's site audit) lists missing or duplicate H1s across a whole site.
  • The "headings only" test: read just the headings of the page. If someone reading only those would understand what the page covers and find their answer, the structure works.

Common CMS pitfalls

Themes and page builders often cause structural problems that editors never see:

  • The logo or site name is wrapped in an H1 on every page, so every page has the same H1 plus its real one.
  • Widget titles in sidebars and footers ("Recent posts", "Contact us") are marked up as H2s or H3s, cluttering the outline.
  • Blog post titles in listing pages use H1s for every post.
  • Editors choose headings from a drop-down by appearance, picking "Heading 4" because it looks nice.

Fixing a theme template once corrects every page that uses it. In WordPress, Shopify and similar platforms, this is usually a small developer change, and it's worth doing early because it affects the entire site.

Key takeaways

  • Headings create an outline; use one clear H1 and logical H2/H3 levels.
  • Write headings that say what the section answers, often based on real questions.
  • Structure supports accessibility obligations as well as SEO.
  • Lead with the answer and match the page structure to intent.
  • Use tables, lists and short paragraphs for the right kinds of information.
  • Length isn't a goal; cut padding and repetition.