Heading Tags SEO: How to Use H1, H2, H3 Correctly
Heading tags — H1 through H6 — are among the most powerful on-page SEO signals you control directly. Google uses them to parse your page's topic hierarchy, identify sub-topics for featured snippets, and confirm that your content matches the search intent of your target keyword. Getting heading structure right takes minutes and pays dividends across both rankings and accessibility.
One H1 per page, always
Your H1 is the primary heading - it tells Google and users what the page is about. Use exactly one H1 per page. It should contain your primary keyword and match (or closely reflect) your title tag. In most CMS systems, the page or post title automatically becomes the H1. If your theme renders the title as a different heading level, fix it - an H1-less page wastes its strongest on-page keyword signal.
H2s structure your content sections
H2 headings divide your content into major sections. Each H2 should naturally contain keyword phrases related to the section topic. Google uses heading structure to understand content hierarchy and identify sub-topics on the page. For long-form content, H2s also become the chapters Google may display as jump links in featured snippets, significantly expanding your SERP real estate.
Never skip heading levels
Use headings in order: H1, then H2, then H3. Do not jump from H1 to H3. Skipped heading levels confuse both screen readers (accessibility) and search engine crawlers parsing your page structure. H3s appear inside H2 sections as sub-topics. In practice: your page has one H1, several H2s for major sections, and H3s within those sections for sub-points that need their own heading.
Include keywords in H2 subheadings naturally
H2 headings carry real keyword weight — Google scans them to identify what sub-topics a page covers. Each H2 is an opportunity to target a secondary keyword or a long-tail variation of your main term. Do not force keywords where they do not fit, but when a section genuinely covers a related term, write the H2 to reflect it. A page targeting 'on-page SEO' might have H2s like 'How heading tags affect rankings' or 'Heading tag best practices for 2025' — both signal depth and topical breadth.
Use only one H1, even in single-page apps
JavaScript-rendered apps and React frameworks sometimes inject multiple H1 tags — one from a layout component and one from the page component. Audit your rendered HTML (not your source code) using browser DevTools or a crawl tool. In Next.js, the page's H1 belongs inside the page component; the site name in the <title> tag is separate and does not create a second H1. Run a quick site audit to flag pages with zero H1s or multiple H1s.
Heading tags are not for styling — use CSS
A common mistake: using H3 or H4 for visual sub-labels because they look the right size, even when they are not logically sub-sections. This creates a broken heading hierarchy that misleads crawlers and screen readers. Style visual elements with CSS classes, not heading levels. Heading tag choice must always reflect the content hierarchy, not the desired font size. If something is not actually a subsection, use a <strong> or <p> tag and apply the visual style you need.
Heading structure helps featured snippet eligibility
Google's featured snippets — especially list-style and table-of-contents snippets — are often extracted from pages with clear heading structures. When your H2s map directly to the steps, points, or categories in your answer, Google can pull them as a structured list. For how-to content, step-by-step processes, and comparison articles, using numbered or action-verb H2s (e.g., 'Step 1: Audit your current headings') dramatically increases the chance of winning a list snippet.
Audit headings with browser DevTools or crawl tools
Do not assume your CMS renders headings correctly — check the actual DOM. Open DevTools, press Ctrl+F, and search for '<h1' to see how many appear. For a full-site audit, tools like Screaming Frog, Sitebulb, or a free crawler report flag pages with missing H1s, multiple H1s, and skipped heading levels across your entire site. Run this audit after any theme update or CMS migration since template changes frequently break heading hierarchies silently.