Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

How should H2 and H3 headings organize a multi-stage instructional tutorial?

Give each stage of the work one H2, in the order the reader performs them, and use H3 only for what sits inside a stage: a variation, a condition, a check, or a fix. A reader who scans only the H2s should see the whole procedure from start to finish. A reader who opens one H2 should find, under its H3s, everything needed to complete that stage and nothing that belongs to another. Heading levels should descend without skipping, because readers using assistive technology navigate by them.

Identifying workflow stages

Before writing headings, list what the reader does.

  1. Write every action as a short verb phrase, in order.
  2. Group consecutive actions that produce one intermediate result. Each group is a stage.
  3. Name each stage by its result or its main action.
  4. Mark what happens before the first action (tools, materials, safety) and after the last (testing, cleanup). These are stages too.

A stage is the right size when the reader could stop at its end, walk away, and resume later without redoing anything.

A list of what the reader does is also the test of whether the piece is a tutorial at all. The difference between instructions and a description of a process is drawn in the guide to what separates an actionable how-to guide from an article that describes a process.

Using H2 for main steps

Each stage gets one H2. Three rules keep the H2s useful as a scanned list.

  • Start with a verb or number the stages, so the sequence is visible.
  • Name the specific action. Step 2 says nothing. Remove the old faucet says what happens.
  • Keep them parallel. If one is a verb phrase, all are.

Sections that are not steps, such as what you need and troubleshooting, are H2s as well, placed where the reader needs them: requirements before the first step, troubleshooting after the last.

Using H3 for conditions and details

Inside a stage, an H3 marks a branch or a supporting detail.

Use an H3 for Example under the H2 "Remove the old faucet"
A variation by type If the faucet has a single handle
A condition If the mounting nut is corroded
A check before moving on Confirm the supply lines are dry
A sub-procedure with several actions Disconnect the sprayer hose

Do not use an H3 for a single sentence, for emphasis, or to make text larger. Ordinary steps inside a stage belong in a numbered list, not in a run of H3s.

Checking for heading gaps

Here is a faulty outline for a tutorial on replacing a kitchen faucet, followed by its revision. Both were drafted for this guide.

Faulty outline:

H1  How to replace a kitchen faucet
H2    Introduction
H3      Tools
H2    Getting started
H4      Turn off the water
H2    Faucet replacement
H2    Faucet installation tips
H3      Old faucet removal
H2    Conclusion

Problems: the tools sit under an introduction where a scanner will not look for them. A level is skipped, from H2 to H4. Getting started and Faucet replacement do not say what happens. Removal appears after installation and under a tips heading. The sequence cannot be read from the H2s.

Revised outline:

H1  How to replace a kitchen faucet
H2    What you need
H2    1. Shut off the water and clear the cabinet
H2    2. Remove the old faucet
H3      If the mounting nut is corroded
H3      If the faucet has a separate sprayer
H2    3. Clean and inspect the sink deck
H2    4. Install the new faucet
H3      Single-hole installation
H3      Three-hole installation with a deck plate
H2    5. Connect the supply lines
H2    6. Test for leaks
H3      If a connection drips
H2    Troubleshooting after installation

Read the H2s alone: the full job is there in order. Each H3 is a branch that some readers need and others skip. No level is skipped.

Run four checks on any outline.

  1. The scan test. Read only the H2s. Is the procedure complete and in order?
  2. The gap test. Between each pair of consecutive H2s, is there an action the reader must take that has no heading and no step? A missing shut-off or a missing test is a gap.
  3. The level test. Does every H3 sit under an H2, with no level skipped anywhere?
  4. The ownership test. Does anything under one H2 belong to a different stage?

Two accessibility points belong in the same review. The W3C’s Web Content Accessibility Guidelines include criteria for headings that describe their topic and for structure that is conveyed in markup (W3C Web Content Accessibility Guidelines 2.2). In practice that means headings must be real heading elements at the correct level, not bold paragraphs, and heading text must make sense when read out of context in a list.

Headings organize the body. How the opening paragraph should deliver the answer before the steps begin is covered in the guide to writing an introduction that answers the core question without delay, and whether the finished tutorial needs a linked list of its sections is covered in the guide to when a long page benefits from a linked table of contents.

Build the outline in this order: list actions, group into stages, write H2s, add H3s for branches, then run the four checks before drafting a sentence.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *