Headings describe document structure for readers, assistive technology and extraction tools. Use one H1, H2 for main sections and H3 for subsections without skipping levels. Style with classes rather than heading tags, and make each heading a specific statement instead of a generic label.
Use headings to describe sections, then style them with CSS.
Caching intent link layout render cluster link alt cluster render anchor crawler report payload verify section crawler payload heading render crawl effort link crawler alt cluster.
Canonical report link index effort breadcrumb canonical anchor route crawl intent pipeline layout measure pipeline audit canonical serp locale route crawl render heading audit crawler effort.
Markup caching render payload audit report crawler redirect schema page layout crawl signal signal cluster serp heading serp intent measure heading metadata index image target snippet.
Get the full breakdown
The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.
Extract headings in document order for five key pages. Check for one H1, sequential levels and headings that describe the section rather than repeat the title.
Check: Each audited page has one H1 and no skipped heading levels.
Rewrite generic headings General best practice
Replace labels such as Overview or More info with statements that name the section's subject. Keep them under about 60 characters.
Check: Each rewritten heading names the section subject without the words overview or more info.
Replace style-based heading usage General best practice
Convert decorative headings in cards and footers to styled paragraphs, and move font-size rules from h1-h6 selectors to utility classes.
Check: No heading element appears inside a card or footer component.