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.

Follow a strict hierarchical nesting: one H1 per page as the main page title (most important keyword); H2 for major sections (comparable to chapters); H3 for subsections within H2 sections; H4–H6 for progressively deeper nesting. Never skip levels — don't jump from H1 to H3 without an H2. Think of it like an outline: H1 is the title, H2s are the main points, H3s are supporting points. This hierarchy helps search engines understand your content structure and helps screen reader users navigate efficiently.

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, both for search engines and for users. Having a clear, single H1 that matches user intent and includes the primary keyword is a best practice regardless of whether multiple H1s are technically allowed.

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. Headers with natural, question-based phrasing (matching "People Also Ask" queries) are more likely to win featured snippets. Google uses headings as signals for what the content covers, not just for rankings.

Screen readers (like JAWS and NVDA) allow users to navigate a page entirely by heading structure — pressing H to jump between headings or 1–6 to jump to specific heading levels. A well-structured heading hierarchy lets visually impaired users quickly scan page structure and jump to the section they need, without reading everything. Poor heading structure (missing H1, skipped levels, non-semantic heading styling) creates a confusing experience. WCAG 2.1 Success Criterion 2.4.6 requires headings to be descriptive, and proper heading nesting is a WCAG best practice.

There is no strict character limit for heading tags, but best practices suggest: H1 should be 20–70 characters — long enough to be descriptive and include your primary keyword, short enough to display clearly on all screen sizes and in breadcrumb trails. H2 headings should be 40–70 characters — clear enough to stand alone as a meaningful section title. Avoid vague headings like "Introduction" or "Overview" without additional context. H3 and below can be shorter and more specific. Long headings are not penalized by Google, but they can hurt user experience on mobile.

Search engines use headings to build a semantic map of your page's topic structure. The H1 signals the primary subject; H2s signal the main subtopics; H3s signal details within subtopics. This hierarchy helps Google understand entity relationships on the page and match it to a wider range of search queries beyond the exact keyword. Well-structured headings also increase the chance of featured snippets — Google often pulls a heading and the following paragraph text as a direct answer. Additionally, headings are weighted more heavily than body text in relevance scoring, so keyword placement in headings has a real, measurable SEO effect.

About This Heading Extractor

This free heading extractor fetches any public URL 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 (headings signal content structure to crawlers) and accessibility (screen reader users navigate by heading level). This tool reveals missing H1s, skipped heading levels, or over-use of certain tags.

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

How It Works

Paste HTML

Paste the HTML source of any page. Use Ctrl+U (or Cmd+U) in your browser to view the page source, then copy and paste.

Heading Extraction

JavaScript parses the HTML with DOMParser and queries all H1–H6 elements in document order, preserving the natural reading sequence.

Visual Hierarchy

Headings are displayed as an indented tree with color-coded levels. Issues (missing H1, multiple H1s, skipped levels) are flagged with alerts.

Common Use Cases

On-Page SEO Audit

Verify that every page has exactly one H1, that it contains the target keyword, and that H2s cover the main subtopics you want to rank for.

Accessibility Review

Check that heading levels are not skipped, which is a WCAG 2.1 accessibility requirement that benefits screen reader users who navigate by headings.

Content Structure Planning

After writing a page, use this tool to visualize the content outline and ensure it follows a logical hierarchy that matches user intent and search query structure.

Competitor Content Analysis

Extract the heading structure of top-ranking competitor pages to understand how they organize their content and which subtopics they cover in their H2s and H3s.

Writer Guidelines

Use the extracted heading tree as a content brief or outline template for writers, ensuring they follow the correct structure and cover all required subtopics.

Featured Snippet Optimization

Check that your H2 subheadings directly answer common "People Also Ask" questions for the target keyword to increase your chances of winning featured snippets.

Related SEO Tools

Link Extractor
Image Alt Checker
Keyword Density
SEO Checklist

Related Articles

View all articles
Why Question-Formatted H2 Headings Win Featured Snippets — And What FAQ Schema's Decline Changes

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.

Jul 10, 2026
Why So Many Sites Have the Wrong H1 — CMS Template Issues, Multiple H1s, and What Good Looks Like

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.

Jun 23, 2026
Why a Page Can Look Perfectly Structured and Have an Empty Heading Hierarchy Underneath

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.

Jun 18, 2026
Heading Structure for AI Extraction: How Question-Formatted Sections Get Surfaced in Snippets and AI Answers

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.

Jun 16, 2026
Heading Structure and Accessibility: WCAG, Screen Readers, and Why It Also Affects SEO

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.

Jun 10, 2026