H1 and H2 Headings: A Practical Structure Check
Website intelligenceH1 and H2 Headings: A Practical Structure Check
Headings help readers understand a page and help systems interpret its structure. A page can look visually polished while the underlying heading markup is missing, duplicated or arranged in a confusing order.
Make the primary heading describe the page
A clear H1 should identify the main subject of the page. Avoid using a generic heading that could describe every page on the site. For a long article or service page, H2 headings can divide the content into meaningful sections.
Do not choose headings only because they look large. Visual styling and semantic heading tags are separate decisions in the page builder or frontend code.
Review heading counts in SiteBoost
SiteBoost reports H1 and H2 counts from the page it scans. Use those values as a prompt to inspect the published HTML and confirm that the main content has an understandable hierarchy.
A count alone does not prove that the content is useful. Read the headings in order and check whether they describe the sections that follow. If a repeated component adds a heading unexpectedly, review that component.
- Confirm the primary page heading is present.
- Check that H2s divide real sections.
- Avoid using headings only for visual size.
- Inspect shared headers and reusable blocks.
Retest after layout or content changes
Rescan the same URL after changing the page builder or layout. Confirm the heading counts changed as expected and that no global component introduced duplicate headings.
Also review the page visually on mobile so the hierarchy makes sense to a real reader, not just to the document structure.
