How to Check HTML Heading Structure: A Practical H1-H6 Workflow

Start with the content outline

A heading is useful because it names a section, not because it contains a target phrase or looks large on screen. Before changing a level, read the page's actual sections. Write down the main topic, the major questions, and any genuine subtopics. Then compare that outline with the H1-H6 elements delivered in the HTML.

The W3C WAI headings tutorial describes headings as a way to communicate content organization and recommends nesting ranks to reflect the hierarchy. It also notes that a rank skip can be confusing but is not automatically wrong when a new higher-level section closes a previous subsection.

<h1>Beginner bicycle maintenance</h1>\n<h2>Before you start</h2>\n<h2>Clean the drivetrain</h2>\n<h3>Choose a degreaser</h3>\n<h3>Dry and lubricate the chain</h3>\n<h2>When to visit a mechanic</h2>

This outline gives the reader one page topic, three peer sections, and two details inside the drivetrain section. An H4 directly after the H1 would need a closer look because no H2 or H3 explains its parent section. The right fix depends on the content; never change a heading only to satisfy a score.

Check the H1-H6 outline in six steps

• Choose one exact public URL and decide whether you are checking returned source or the browser's current DOM.
• Run the URL through Heading Checker and read the list from top to bottom, not only the totals.
• Identify the page's main topic. Check whether the H1, or another clear page heading, names it accurately.
• For every H2-H6, ask which section it starts and whether the following content belongs under that heading.
• Review empty headings, repeated generic labels, and downward level skips in their surrounding markup.
• Open View Source or browser DevTools when a heading is duplicated, hidden, inserted after load, or otherwise surprising.

The checker works from headings available in the public page response. Its report is a starting point for editorial and structural review, not a claim about what every browser, crawler, or assistive technology experiences.

Diagnose the common heading problems

The page has no clear main topic

A missing H1 or a heading such as “Welcome” can leave the page purpose unclear. Write a concise main heading that names the actual content. Do not add a second visible heading merely to insert a phrase; improve the existing page structure.

A heading is empty

An empty heading creates a section label with no usable name. Remove it, supply a real label when the section is genuine, or investigate the component if the text is supposed to be populated dynamically. A source report cannot decide which of those fixes is correct without the page context.

Headings are being used for visual styling

If text only needs to look large or bold, use CSS. Reserve heading elements for section labels. This keeps the outline meaningful for people scanning the page and for assistive technologies that provide heading navigation.

The labels are repeated or generic

Repeated labels such as “More,” “Details,” or “Information” provide little context when a reader jumps between headings. Name the actual subject of each section, such as “Shipping costs” or “Compare repair options,” when that is what the content is about.

The outline skips a level

A downward jump, such as H2 to H4, is a review signal. If the H4 is a real subsection of the H2, use H3 or add the missing section only when the content supports it. A jump back to a higher level can simply mean the previous subsection has ended.

The report does not contain a visible heading

The heading may be inserted after JavaScript runs, represented by styled text rather than an H element, or absent from the returned HTML. Compare View Source with the live DOM and record which view contains the heading before changing the page.

Understand H1 rules without turning them into myths

A clear primary heading is a practical way to tell readers what a page is about. That does not mean a heading checker can prove that a page must contain exactly one H1 to rank, or that multiple H1 elements automatically make it invalid. Review the page's actual information architecture and whether the main topic is understandable.

• One clear H1 is a useful editorial default for a page with one dominant topic.
• Multiple H1 elements require context: they may be accidental duplicates, component headings, or a sign that the page's structure needs clarification.
• A skipped rank is worth examining, but changing it mechanically can make the outline less truthful.
• Heading text should describe the section's content; repeating a keyword does not create a useful hierarchy.
• The HTML Standard defines H1-H6 as heading elements; the surrounding content determines how well they communicate the document.

The WHATWG HTML Standard's sections guidance is the primary reference for heading elements and sectioning content. Use standards to understand what the elements mean, then use the page itself to decide whether the hierarchy is clear.

Source order versus the live DOM

SolViewer's Heading Checker reads headings available in the public HTML response. It does not execute the site's JavaScript, test keyboard navigation, decide whether a heading is visually hidden, or determine what every crawler receives. A heading inserted after load can be absent from the report; a heading present in source can be hidden or replaced later.

• Source result: evidence that the heading element was delivered in this response.
• Live DOM result: evidence that the browser currently has the element after parsing and runtime changes.
• Visual result: evidence about what is visible in a particular browser session.
• Accessibility result: evidence that still needs keyboard and assistive-technology testing.

When these views disagree, do not report “the heading is missing” without a scope. Say “the heading was not found in the returned HTML” or “the live DOM contains a heading that the source check did not show.”

Use the outline to make a focused fix

• Rewrite an unclear label so it names the section's real question or task.
• Remove an empty heading or fix the component that should provide its text.
• Change a heading rank when the content hierarchy genuinely calls for it, not because the number looks unusual.
• Use a paragraph or styled text when the content is not a section label.
• Check nearby landmarks and section elements so the heading has a meaningful parent.
• Read the page again from the user's perspective after the markup change.

For a wider review of landmarks and native elements, read Semantic HTML for SEO and Accessibility. For the full relationship between <head>, <body>, and sectioning elements, use the HTML document structure guide.

Frequently asked questions

Is an H1 required for SEO?

A clear main heading is useful for readers and for a logical document structure. A checker can report whether an H1 is present, but that report is editorial evidence, not a ranking prediction or a guarantee that a page will be indexed.

Are multiple H1 tags always bad?

No. Multiple H1 elements are not automatically proof of an SEO failure. Review whether the page still has an understandable primary topic and whether the headings reflect genuine content regions or accidental duplication.

Is skipping from H2 to H4 always wrong?

Not automatically. The skip is a prompt to inspect the relationship between sections. If the H4 is a direct subsection of the H2, the hierarchy may be clearer with an H3; if the previous subsection has ended, a higher-level heading may be appropriate.

What does Paste text check?

Paste text reviews one supplied H1 value for wording guidance. It does not parse pasted HTML or create an H1-H6 outline. Use a public URL for the source-order heading report.

Why are some visible headings missing from the report?

They may be created after JavaScript runs, styled without heading elements, or unavailable in the returned HTML. Compare the result with original page source and the live DOM before deciding what to change.

Sources

• WHATWG HTML Standard: Sections and headings — heading elements and sectioning content.
• W3C WAI: Headings — heading ranks, organization, and navigation.
• W3C WAI-ARIA Authoring Practices: Landmark Regions — headings and landmarks as related navigation structures.