01
Step-by-step
- 01
Use one clear page heading
The H1 should identify the primary subject or task.
- 02
Create a logical hierarchy
Use H2 sections for major parts and H3 subsections within them.
- 03
Write descriptive text
A heading should communicate what follows.
- 04
Do not choose levels for size
Style headings with CSS rather than skipping levels.
- 05
Review the outline
Read the headings alone; they should form a coherent summary.
02
Verification
- The visible page matches the intended topic and audience.
- The page can be crawled, rendered, and indexed when intended.
- Claims, examples, code, and links have been checked.
- The page has a measurable next action or outcome.
- A future reviewer can understand what changed and why.
03
Before you change the website
- Define the purpose and expected result of headings.
- Capture the current state using audience task, search intent, factual support, page purpose, structure, examples, links, calls to action, and maintenance ownership.
- Identify the source template, component, plugin, content owner, and release path that controls the output.
- Prepare a test case, approval path, backup or rollback method, and post-release verification plan.
04
Quality-control checks for headings
- Review the page against its intended task, validate claims and links, and measure whether users reach the next useful action.
- Check representative page types and edge cases instead of confirming only the example used during implementation.
- Confirm the change did not create optimizing wording before defining the page purpose and evidence.
- Record the implementation date, owner, release reference, evidence, and next review trigger.
Next useful action
Turn headings into an accountable record.
A tested implementation of headings with deployment notes, rollback context, and retained verification.