
Heading vs Subheading: Difference & Examples
A heading is the title of a page or section; a subheading is a smaller heading that splits that section into parts. On a web page the main heading is the H1, and subheadings are the H2s, H3s and lower levels beneath it. For example, a recipe page might use the heading "Banana Bread" (H1) with the subheadings "Ingredients" and "Method" (H2s).
For SEO, the heading vs subheading question is less about which tag ranks better and more about structure. Google's John Mueller has called headings "a really strong signal" for understanding what each part of a page is about, while saying the exact level, H1, H2 or H5, matters much less. That matters more now than it did five years ago, because Google's featured snippets and AI Overviews, along with tools like ChatGPT search, depend on parsing structure to lift out answers.
What "Heading vs Subheading" Means in HTML
A heading and a subheading aren't two different technologies. They are the same tag family (H1 through H6) used at different depths of the same outline. The H1 is your page's main heading; H2s are subheadings under it; H3s subdivide H2 sections, and so on down to H6.
Here is the banana bread page as an outline:
- H1: Banana Bread
- H2: Ingredients
- H2: Method
- H3: Mixing
- H3: Baking
In print and journalism, "subheading" can also mean the line under a headline that expands on it, sometimes called a deck or standfirst. That is closer to a subtitle. On web pages, a subheading usually means an H2 to H6 heading inside the body.
The H1: Usually One Per Page
Use one H1 per page as a clear convention. Google has said multiple H1s won't hurt rankings and that a site will rank fine with no H1 or with several, but a single H1 keeps the topic obvious for readers and screen readers. It states the primary topic and usually aligns closely with the page's search intent. Multiple H1s used to be debated when HTML5 proposed letting sectioning elements reset heading scope, but browsers never implemented that document outline and it was later removed from the HTML spec, which is why one H1 per page remains the accessible default.
H2 Through H6: The Nesting Rule
H2s break the page into its major sections. H3s sit inside an H2 to cover sub-points, H4s sit inside H3s, and so on. Skipping levels, for example jumping from an H2 straight to an H4, breaks the outline screen readers rely on. Google's SEO Starter Guide says heading order doesn't matter for Search, so this is about accessibility and clarity, not rankings.
Title Tag vs H1: Two Jobs, Often Confused
The title tag and the H1 are not the same thing: the title tag lives in the page's <head> and is one of the main sources Google uses for the title link in search results, while the H1 lives in the visible body content. Both should reflect the same topic, but the title tag is written for the search results page and the H1 for the person who already clicked through.
Does Adding More Subheadings Improve Rankings?

No. Adding subheadings without adding genuine content sections does nothing for rankings, and in some cases it hurts readability by fragmenting shallow ideas into artificial-looking sections. Subheadings help indirectly, by making content scannable and machine-parseable, not by existing in higher counts.
Some "SEO heading tips" articles imply more H2s and H3s equal more ranking signals, as if search engines count tags like keywords in 2009. They don't. Google's systems evaluate whether each section answers something a reader (or an AI model summarizing the page) would search for.
Why Structure Beats Volume
Featured snippets and AI Overviews extract short, self-contained chunks of text, often a paragraph or a list directly under a heading that phrases a question naturally. A page with five vague H2s like "More Information" or "Other Details" gives extraction systems nothing to grab. A page with an H2 phrased as "How Long Does a Roof Replacement Take?" followed immediately by a direct 40-word answer is far more extractable.
The Keyword-Stuffing Trap
Cramming your target keyword into every single subheading ("Best Widgets," "Cheap Widgets Near Me," "Widgets for Sale Today") reads unnatural and can suppress click-through even if it doesn't directly hurt rankings. Vary phrasing. Use the keyword where it's the clearest way to describe the section, not in every heading by rule.
Structuring Headings for AI Overviews and Featured Snippets
One of the most useful habits for content teams is matching heading phrasing to how people ask questions, then answering that question in the first sentence or two below it. This is what makes a chunk easy to lift for both Google's snippets and AI summaries.
- Phrase key H2s and H3s as questions or clear statements, not vague labels.
- Answer the question in the first 40–60 words directly under the heading.
- Use one heading per distinct sub-question; don't bury two answers under one heading.
- Keep H3s nested logically under their parent H2, never orphaned.
- Use numbered or bulleted lists under headings describing a process or ranking.
- Avoid duplicate heading text across the page, since it blurs which section maps to which query.
| Heading Type | Best Use | Extraction-Friendly? |
|---|---|---|
| H1 | Page topic, usually one per page | Not directly; sets context only |
| H2 (question-phrased) | Major sub-topic, direct answer follows | Yes, a primary snippet source |
| H2 (label-only) | Weak, vague sections ("More Info") | No |
| H3 | Nested detail under an H2 | Yes, if self-contained |
| H4–H6 | Deep nesting, rarely needed on blog content | Rarely relevant |
Headings and Accessibility

Screen readers navigate pages by heading level, letting users jump straight to an H2 or H3 without reading everything in between. If your hierarchy skips levels or uses headings purely for font size rather than structure, you're breaking navigation for anyone using assistive tech, which is an accessibility failure in its own right.
The same structure that helps a screen reader user also helps a sighted user scanning on a phone. Clear headings help people find their answer faster, which is the point: pages that satisfy readers tend to earn links, shares and return visits.
Getting this right across a full site, especially one publishing regularly, is mostly a discipline problem. DraftSEO applies this heading-and-answer pattern by default to the articles it writes; you can start for free and see current plans on the DraftSEO pricing page.
Frequently Asked Questions
What is an example of a heading and a subheading?
On a recipe page, "Banana Bread" is the heading (H1), and "Ingredients" and "Method" are subheadings (H2s). Under "Method," smaller subheadings such as "Mixing" and "Baking" would be H3s.
Is a subheading the same as a subtitle?
Not quite. A subtitle, or deck, is a line under a headline that expands on it, common in print and news. On web pages, a subheading is an H2 to H6 heading that divides the body into sections.
Does using H2 instead of H3 change how a page ranks?
No, not on its own. Ranking depends on whether the content beneath the heading directly answers a real query, not which specific tag number is used. Use the level that matches its place in the outline for clarity.
Can I use two H1 tags on one page for extra keyword weight?
It won't add keyword weight. Google says multiple H1s don't hurt rankings, but one H1 that states the page's subject is clearer for readers and assistive technology.
How many subheadings should a 1,000-word article have?
There's no fixed number; it depends on how many distinct sub-questions the topic has. A 1,000-word page with 4–6 well-phrased H2s is usually easier to read and extract from than one with 10 shallow, repetitive ones.


