Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Read headings without surrounding copy
- 02Mark vague verbs and category clichés
- 03Check whether each section heading advances the argument
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Use nouns and outcomes specific to the product
- 02Let headings summarize the section’s claim
- 03Keep clever language subordinate to comprehension
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Run the page as a headings-only outline
- 02Ask users what they expect below each heading
- 03Compare search intent with the title and H1
Common pitfall
A shortcut to avoid
Forcing a keyword into every heading can make useful information repetitive and unnatural.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.