A heading is a structural label, not merely a large or bold sentence. Good headings help readers understand a page before reading every paragraph. Review the document outline and visual presentation together, especially when a page includes several services, instructions or complex comparisons.
Name the content that follows
Write headings that predict the section's answer. Replace vague labels such as 'More information' with the actual decision or subject. Keep wording useful without forcing the same target phrase into every heading. A reader scanning only the headings should still understand the route through the explanation.
Use levels to show relationships
Use a clear main heading and organise subordinate sections logically. Choose levels because of the content hierarchy rather than font size. Keep visual styling separate from document semantics where your platform allows it. Review repeated navigation and template headings so they do not obscure the main page structure.
Verify the published outline
Inspect the final HTML or an accessibility-oriented outline, not only the editing interface. Check whether components insert unexpected levels or use styled paragraphs instead of headings. Test a long page on mobile and consider whether headings help people return to the section they need without searching through decorative blocks.
Put the method to work
Illustrative correction: a guide uses several visually large statements as unrelated H1 elements and hides its actual steps in bold paragraphs. The editor establishes one clear page topic and uses subordinate headings for preparation, procedure and verification. The change improves structure without claiming an automatic ranking uplift.
Your next steps
- Write an outline before styling the page
- Make each heading describe its section
- Choose levels by relationship, not appearance
- Check component markup after publication
Questions & answers
Does every heading need a keyword?
No. Use relevant language naturally. The heading's first job is to identify the following content accurately and help users navigate it.
Can a heading audit prove accessibility?
No. Heading structure is one aspect of accessibility. Forms, keyboard operation, contrast, alternatives and other aspects also require appropriate review.
Documentation & further reading
- www.w3.org · › WAI › tutorials › page-structure › headings ›
- developers.google.com · › search › docs › appearance › title-link
- developers.google.com · › search › docs › fundamentals › seo-starter-guide
Explore the related in-depth guide ↗ · Build an action plan ↗