Plan a readable website heading structure.

1. Write the page outline before styling

Identify the page’s main subject, its major sections, and any genuine subsections. W3C’s writing guidance recommends short, descriptive headings that group related content and make the outline understandable. Each heading should tell the reader something useful about what follows.

ATN suggests reading the outline on its own. Replace vague labels such as “More” with a description of the actual topic. If two neighboring sections repeat the same idea, consider combining them before adjusting fonts. The point is not to add a heading after every paragraph; it is to reveal the meaningful organization already needed by the page.

Sources: [2]

2. Assign levels according to relationships

W3C’s headings tutorial describes six heading ranks and recommends nesting them to reflect sections and subsections. Avoid jumping down into a deeper rank without the intervening structure where possible. Returning to a higher-level heading to start the next main section is a different, normal transition.

For an original ATN example, a page titled “Prepare a project handoff” could have major sections for Files, Instructions, and Verification, with subsections under Files for Source material and Delivery exports. Decide those relationships first. Do not choose a lower-level heading solely because its default font happens to be smaller; styling can be adjusted without misrepresenting the hierarchy.

Sources: [1]

3. Check that headings are actual headings

W3C explains that changing visual style alone does not supply the same structural information as semantic heading markup. Use the editor’s heading controls or the appropriate HTML heading elements rather than manually bolding an ordinary paragraph and assuming the result is equivalent.

Inspect the rendered page, especially when content passes through a template or a rich-text editor. A document can look correct in the editing interface while the published markup differs. ATN recommends checking the main content together with reusable components such as cards, sidebars, and footers, because their headings also contribute to the page a reader encounters.

Sources: [2]

4. Review the outline and visible layout together

Check whether the headings remain descriptive and whether the levels still match the intended relationships. W3C notes that heading structure can support in-page navigation, making the outline useful beyond a visual scan. Review with the project’s appropriate accessibility tools rather than relying only on font size.

Keep visual spacing consistent enough to show which heading belongs to which content, including when a title wraps onto several lines.

Sources: [1]

5. Recheck after substantial content edits

When adding or moving sections, review the whole outline rather than only the new paragraph. Update a table of contents or related anchor links if their targets changed. Avoid retaining an empty heading simply because it was present in an earlier template.

Record any remaining issue precisely, such as a card heading rendered at an unexpected level, and assign it to the relevant template or content source. This is a structure review, not a complete accessibility or search-performance assessment. Keeping the outline understandable makes future editing easier because the next maintainer can see how the page’s parts are meant to fit together.