Heading levels in CMS-driven pages
Flexible page builders let editors drop “feature” blocks anywhere. Visually everything aligns; structurally you may jump from h2 to h4 because a promo component hard-codes a large title.
Lock heading rank per block type
We advise clients to store semantic level in the block schema—not let editors pick h1–h6 freely. The page title owns h1; repeating blocks use h2 or h3 based on nesting depth.
Preview with landmarks off
Ask editors to skim the page with CSS that exaggerates heading size per level. Skipped levels become obvious before publish.
Audit finding wording
When we log heading issues we cite the URL, the visible text, and the expected level. Developers fix faster than when reports only say “headings incorrect.”