Heading Extractor

Paste HTML to extract and visualize all heading tags (H1–H6) as an indented hierarchy. Identify missing H1s, multiple H1s, and skipped heading levels instantly.

Heading Structure
Paste HTML above to see heading structure.

Frequently Asked Questions

Best practice and Google's general guidance is to have one H1 per page. The H1 should clearly state the main topic of the page and ideally include the primary keyword. Having multiple H1s is not a direct ranking penalty, but it can dilute the topical focus signal and confuse both users and search engines about the page's primary subject.
Skipped heading levels occur when you jump from H1 to H3 without an H2, or from H2 to H4. This is a WCAG accessibility violation that confuses screen reader users who navigate by headings. While Google does not penalize for this, it reflects poor content structure. Logical heading hierarchy (H1 → H2 → H3) helps both users and search engine crawlers understand content organization.
They should be similar but don't need to be identical. The title tag (shown in search results) is often optimized for click-through rate and includes the brand name. The H1 is shown to the user on the page and should clearly state the topic. Using the same primary keyword in both reinforces topical relevance.
Heading tags are a moderate on-page SEO factor. They signal content structure and keyword relevance. H1 carries the most weight, followed by H2, H3, etc. Using target keywords in H2 subheadings that match common search queries can help those sections appear in Google's featured snippets and "People Also Ask" boxes.
Google has stated that multiple H1 tags are not a direct ranking penalty — John Mueller confirmed in 2020 that HTML5 allows multiple H1s within sectioned content. However, in practice, having multiple H1s often signals confused document structure and dilutes the topical focus signal. Most SEO professionals still recommend a single H1 per page for clarity.
Place your primary keyword naturally in the H1 — ideally near the beginning of the text. For H2 headings, include secondary and related keywords that represent the main questions or subtopics users search for. H3 headings can include long-tail variations. Avoid keyword stuffing — write headings that are genuinely useful for users first.

About This Heading Extractor

This free heading extractor parses HTML and lists all heading tags (H1–H6) in the order they appear on the page, making it easy to audit heading hierarchy and content structure. A clear, logical heading hierarchy improves both SEO and accessibility.

When to use this tool

  • Auditing heading hierarchy for SEO and WCAG accessibility
  • Checking that a page has exactly one H1 tag
  • Finding heading levels that are skipped in the document outline
  • Comparing heading structure across competitor pages

Standards & References

Related Articles

In-depth guides and technical articles.

View all →
Why Question-Formatted H2 Headings Win Featured Snippets — And What FAQ Schema's Decline Changes
Paragraph featured snippets are typically pulled from content immediately following a heading that matches the query — the heading provides the question context that the following paragraph answers. Here's how table snippets use headings for context, why FAQ schema's reduced eligibility makes heading-structured Q&A more important, why H2 level is most likely to generate snippets, and what a heading extractor reveals about competitor pages that rank for snippets.
Why So Many Sites Have the Wrong H1 — CMS Template Issues, Multiple H1s, and What Good Looks Like
Many sites have multiple H1s, no H1, or H1s that say "Home" because a CMS template set it up that way. Here's what H1 should represent (page's primary topic heading), why HTML5's multiple-H1 sectioning model was abandoned in practice, the common implementation failures audits consistently find (generic "Home" or "Blog" headings, H1 below H2 in visual hierarchy), and how heading extractors reveal template-level H1 issues across a whole site.
Why a Page Can Look Perfectly Structured and Have an Empty Heading Hierarchy Underneath
A page can have visually-perfect headings — right size, right boldness, right spacing — while having a completely empty semantic heading structure underneath, because CSS can style any element to "look like" a heading regardless of what HTML element it actually is. Here's why "div soup" headings happen with visual page builders, why a sparse heading-extraction result for a competitor's visually-organized page is genuinely meaningful (not misleading), and how to check whether your own visual headings are actually marked up correctly.
Heading Structure for AI Extraction: How Question-Formatted Sections Get Surfaced in Snippets and AI Answers
AI systems that summarize or answer questions from web content rely heavily on heading structure to identify which section of a page addresses a specific question. Here's how question-formatted headings align with featured snippets and AI extraction, why self-contained sections matter, and how heading hierarchy communicates topic/subtopic relationships to extraction systems.
Heading Structure and Accessibility: WCAG, Screen Readers, and Why It Also Affects SEO
Screen reader users navigate pages primarily through headings — 67% according to WebAIM surveys. Here's how WCAG requires proper heading structure, the rules for hierarchy and H1 usage, accessibility failures that also hurt SEO, and tools for auditing heading structure.