Audit heading hierarchy on long-form content
Review rendered heading levels, labels, and document structure so long-form content works visually and with assistive technology.
Long-form content can look organized while remaining difficult to navigate. Large bold text may create a visual break, but assistive technology needs real heading markup and a logical hierarchy.
W3C guidance explains that well-structured content supports screen-reader navigation, keyboard use, cognitive accessibility, reader modes, and clearer orientation for many readers.
Read the article as an outline
Before checking font sizes, extract only the headings. The sequence should communicate the article’s argument without the paragraphs.
A heading should describe the topic or purpose of the section. Labels such as “More,” “Next,” or “Details” make little sense when heard outside the visual layout.
The hierarchy should reflect relationships. An H3 belongs under the relevant H2. A heading level should not be chosen because its default style looks better.
Separate document title from article sections
Most web pages have one primary title that becomes the H1. The CMS may render it outside the Markdown body, which is why a body-only article can begin with H2 sections.
Confirm the final page, not only the editor. A CMS can accidentally render the article title as a paragraph or add a second H1 through the theme.
Use headings for sections, not for pull quotes, buttons, or decorative labels. Style those components with classes rather than borrowing semantic levels.
Fix skipped levels with meaning
A jump from H2 to H4 often signals one of two problems. Either the H4 is really a visual label and should not be a heading, or a missing parent idea has not been written.
Do not insert an empty H3 only to satisfy a checker. Rename and restructure the content so the relationship becomes real.
Likewise, avoid flattening every section to H2. Nested headings can make a detailed guide easier to scan when the subsections genuinely belong together.
Test two navigation modes
First, scan visually. Can a reader find the answer they need without reading the whole page
Second, use a browser accessibility tree or screen-reader heading list. Do the same labels and levels make sense without layout cues
The two views should tell one coherent story. A visual card title that disappears from the heading outline may still be fine if the card is supporting material. A major section absent from the outline is a defect.
Give editors a small rule set
An effective editorial guide can stay short.
Use the CMS title as the only H1
Use H2 for major article sections
Use H3 for true subsections
Write headings that name the section’s job
Never choose a heading level for appearance
Review the rendered page after publication
Add examples from your own CMS because editor controls and theme behavior vary.
Make the check part of publishing
Heading QA belongs beside link and image checks. It is easier to correct before a page is published and reused in newsletters, lead magnets, or AI summaries.
The goal is not a perfectly symmetrical outline. It is a structure that communicates relationships and lets different readers move through the article efficiently.
Source guidance comes from the W3C page structure tutorial and W3C guidance on headings and labels.
