H2 and H3 Subheadings: How to Write Them for SEO, Step by Step

H2 and H3 subheadings split a long article into sections that both readers and search engines can scan with ease. In this guide, Talha Aslan and team walk you through the method we use on client sites, step by step. We cover hierarchy, question headings, jump links, passage reading and writing without keyword stuffing. At the end, you will find a comparison table and a short checklist.

In short, a subheading is a road sign, not decoration. When readers open a page, they scan the headings first and decide where their answer is. If the headings make that choice easy, they stay. If not, they go back to the results. Therefore, we think about the reader's question first and the keyword second.

Headings also bring discipline to the writer. If you cannot write a section's heading in one sentence, that section probably carries more than one topic. In that case, splitting it in two helps both the reader and the text.

What is the difference between H1, H2 and H3 tags?

HTML defines six heading levels. H1 is the top level and H6 is the lowest. In practice, H1, H2 and H3 cover most needs in a blog post. The H1 is the page's main heading and usually states the same topic as the post title. H2 tags mark the main sections, while H3 tags mark the steps or examples inside those sections.

A book analogy makes this easy. The H1 is the book's title, the H2s are chapter titles and the H3s are the subheads within each chapter. So an H3 should not drift away from the topic of the H2 above it. If it opens an independent topic, it belongs at H2 level instead.

Whether a page may use more than one H1 is a separate debate. We cover it in detail in our post on whether a page can have multiple H1 tags. Here, our focus is the H2 and H3 layer in the body. In other words, the subheads readers see as they move through the article.

Does Google really care about heading order?

Google's official SEO Starter Guide is clear on this point. It says that keeping headings in semantic order is fantastic for screen readers. However, from a Google Search perspective, it does not matter if you use them out of order. The guide also states that there is no magical, ideal number of headings for a page.

It is easy to misread that sentence. Google will not penalize you for breaking the order, but that does not make headings unimportant. The same guide advises you to break long content into paragraphs and sections and to provide headings that help users navigate your pages.

That is why we still keep the order clean. A tidy hierarchy helps visitors who use screen readers. It also helps plugins that build a table of contents and editors who update the text later. Put simply, a clean order is not a ranking trick. Instead, it is the natural result of a well built page.

Where does Google use subheadings?

Subheadings matter in several places. First, Google's guide to ranking systems describes passage ranking as an AI system. According to that guide, the system identifies individual sections or passages of a web page to understand how relevant the page is to a search.

Second, Google looks at several sources when it generates the title link in search results. The title links documentation lists the title element, the main visual title on the page and heading elements such as H1 among those sources. As a result, consistency between your main heading and your title tag matters.

Third, search snippets, the short descriptions in results, come mostly from page content. A well defined section offers a short passage for a related question, which makes that process easier. Still, no heading layout guarantees a specific feature or ranking. Google decides the outcome with its own systems.

What makes a good H2 and H3 subheading?

The strong subheadings we see in the field share a few traits. You can use them as a checklist while you write:

• One topic: The heading covers a single question or a single step.
• Plain language: Readers can guess what the section holds before they read it.
• Short length: Most headings fit on one line and skip filler adjectives.
• Natural key phrase: The topic term appears where it fits and is never forced in.
• Honest tone: The heading never promises what the content does not deliver.
• Standalone meaning: The heading still makes sense when read alone in a table of contents.

The last point matters most. Google's helpful content guidance also asks whether the main heading gives a descriptive, helpful summary of the content and whether it avoids exaggeration. When you apply the same logic to subheads, empty lines like "The shocking truth" drop out on their own.

For example, "How much does a setup cost, and what drives the price?" is clearer and more honest than "Prices." Readers know up front that they will find the cost factors, not a fixed price tag.

When do question-style H2 and H3 subheadings work best?

Question headings work very well when they mirror the question already in the reader's mind. For instance, headings like "What is passage reading?" or "How many H2s should you use?" set up the expectation of a clear answer in the first sentence. That expectation also pushes the writer to answer short and direct.

That said, turning every heading into a question is not the right move. In a step-by-step process, action headings like "Step 1: list the target questions" read better. Likewise, a plain noun heading is enough for sections that hold a comparison table or a checklist.

We usually strike a balance. Informational sections use question form, and how-to steps use the imperative. That way, readers can tell from the headings alone where the "what" and the "how" are answered.

Do not guess the questions. Related questions in search results, customer emails, sales calls and Search Console queries give you a real question list. Building that list before drafting is a natural part of content planning. It also keeps the outline tied to real demand rather than to the writer's assumptions.

How do you build a subheading hierarchy step by step?

Drafting the heading skeleton before you write saves major edits later. Here is the order our team follows:

1. Pick one main question for the page and write the H1 and title tag around it.
2. List the follow-up questions readers ask along with that main question.
3. Group similar questions. Each group is a candidate for an H2.
4. Place the details, examples and steps of each group beneath it as H3s.
5. Order the H2s by the reader's needs: definition first, then method, then advanced topics.
6. Read the headings alone and check whether they tell the story of the article.
7. Merge headings that repeat each other or say the same thing.

Step six is the most valuable test. Imagine you delete the whole body and keep only the headings. If that list tells you what the article covers and in what order, the skeleton is solid. Otherwise, readers will get lost between the headings too.

Once the skeleton is ready, start writing. Each paragraph then serves the question of the heading it sits under. Moreover, if you share the skeleton with your editor first, the structure debate happens before drafting, not after, and revision rounds get much shorter.

Example scenario: what does a service article skeleton look like?

As an example scenario, imagine a home renovation site called example.com preparing an article on "how long does a bathroom remodel take?" In the first draft, the headings read "Introduction," "Details," "Other information" and "Conclusion." Those headings tell the reader nothing.

When we rebuild the same article, the skeleton turns into this:

• H2: How long does a bathroom remodel usually take?
  • H3: Light refresh versus full tear-out
  • H3: What stretches the timeline
• H2: What stages does a remodel include?
  • H3: Demolition and plumbing
  • H3: Waterproofing and drying time
  • H3: Tiling and installation
• H2: Can you use the bathroom during the remodel?
• H2: What should you prepare in advance to save time?

In the new skeleton, each H2 is a real reader question and each H3 is a part of that question. Also, a reader who only cares about drying time can jump straight to the right H3. We gave no duration figures in this example. In a real article, you should base any time range on your own field experience and add a clear "not a guarantee" note.

How long should subheadings be, and what wording should they use?

There is no fixed character limit. Still, the headings that work best in our experience usually fit on one line. Readers should grasp a heading at a glance. A heading that spills onto two lines often means you are cramming two ideas into one sentence.

For wording, we suggest using the reader's own words. For example, an industry might call a task "performance optimization," while customers search for "make my site faster." Use the reader's phrase in the heading and explain the technical term inside the paragraph. As a result, experts and beginners both benefit from the same heading.

Also, pick one consistent grammar pattern for your headings. If some headings address the reader directly and others use a vague impersonal style, the list looks messy. Sticking to one pattern makes the table of contents look tidier too.

Finally, settle on a capitalization rule. Sentence case, where you capitalize only the first word and proper nouns, often reads more easily. Title case also works. Whichever you choose, apply it across the whole site. Otherwise, readers will spot different writers' habits from the headings alone.

How many H2s and H3s should one article use?

The right number depends on how many subquestions the topic breaks into. Google's guide also says plainly that there is no ideal number of headings. So a rule like "one H2 every 300 words" can be a starting idea, but it should not be a target.

In the field, we use a few signals. If a section needs several scrolls on screen and holds two distinct topics, we consider adding an H3. On the other hand, splitting a two-paragraph section into three H3s does not help reading. It only chops the text into pieces.

Another signal is the table of contents. If the table shows only H2s and the list fills the whole screen, you should merge some H2s and move them down to H3 level. Meanwhile, a very short list may mean the article skips important questions.

In short, balance matters more than count. If readers learn something new at each heading, the number is right. If you see headings that repeat the same idea in different words, it is time to cut back.

How do you place keywords in subheadings without stuffing them?

Subheadings are one of the most common places for keyword stuffing. Google's spam policies define keyword stuffing as filling a web page with keywords or numbers in an attempt to manipulate rankings. Repeating the same words or phrases so often that it sounds unnatural is one of the listed examples.

In practice, we recommend a simple approach. Use the main key phrase in the first H2 and in the few headings where the topic truly needs it. In the other headings, prefer synonyms, the names of the subtopics and readers' natural questions. Then your heading list reads like a topic map rather than a keyword list.

After you write a heading, ask yourself one thing. Did I add this word for the reader or for the search engine? If the answer is the second, simplify the heading. For a broader view, see our posts on what keyword stuffing is and what keyword density should be. You can also run a draft through our keyword density tool to spot phrases you repeat too often.

How do you write a section that works for passage reading?

A section built for passage reading answers its heading's question directly in the first two or three sentences and then goes into detail. Even if a reader or a system reads only that section, it should still deliver a clear answer. For that reason, avoid opening lines that lean on other sections, such as "as we mentioned above."

We use a three-layer pattern. The first layer gives a short, clear answer. Next, the second layer explains the reason or the conditions behind it. The third layer adds an example, an exception or a practical step. This order serves the reader in a hurry as well as the reader who wants depth.

In addition, define terms briefly the first time they appear inside a section. Readers may land on the page directly at that section. They may not have seen the definitions in earlier sections. The formatting advice in our guide on how to win featured snippets follows the same logic.

Keep in mind that Google picks passages with its own systems. Your job is to make each section accurate and meaningful on its own.

How do jump links and a table of contents work with subheadings?

A table of contents lists the H2 and H3 subheadings on a page and links to each one. These links rely on IDs assigned to the headings. When a reader clicks an item, the page scrolls to that section and a hash fragment (#) appears in the address bar.

Google's snippet documentation mentions "Read more" deep links. According to that page, these are links within a snippet that lead users to a specific section of the page. The documentation also tells you not to use JavaScript that removes the hash fragment from the URL on load, because that breaks deep linking. Content should also be immediately visible to a human.

So we watch three points when we build a table of contents:

• Heading IDs should be short, readable and stable, and they should not change every time you edit the heading.
• Section content should be open by default, not hidden in collapsed tabs.
• The table should show only meaningful H2s and, where needed, H3s.

For the full details, read our post on table of contents SEO and Google jump links.

What happens when heading tags and visual style get mixed up?

On many sites, heading tags and font size are tangled together. For example, a theme might print the sidebar's "Recent posts" box as an H2. At the same time, it may render the real subheads in the body as bold paragraphs. On such a page, the visual structure and the HTML structure tell different stories.

This hurts visitors who use screen readers the most, because they navigate by jumping from heading to heading. A bold paragraph does not count as a heading, and sidebar headings mix with the main content. As a result, the reader struggles to find the main topic.

The fix is simple but needs care. Use heading tags only to mark content sections and control their look with CSS. If you want text to look big, give it a style class instead of making it an H2. Conversely, if you want a real section heading to look small, keep the tag and shrink it with styling.

Theme and layout issues like these tie directly to user experience. Our post on how to build a UX content structure is a good place to start for a wider view.

What separates a weak subheading from a strong one?

The table below compares the weak heading patterns we meet most often in audits with the stronger versions we suggest. The examples are generic, so adapt them to your own topic.

The common thread is simple. A strong heading makes the reader a promise before they read the section, and the section keeps it. A weak heading either says nothing or sets an expectation the content does not meet.

What are the most common subheading mistakes?

We see the same mistakes again and again on the sites we audit. Knowing them saves time when you check your own posts:

1. Generic headings: Labels like "Introduction," "Details" and "Conclusion" give readers no direction.
2. Repeated headings: The same question asked twice in different words.
3. Orphan H3s: Subheads with no link to the topic of the heading above.
4. Buried answers: A question heading whose answer hides in the third paragraph.
5. Bold text posing as a heading: Visual headings that stay paragraphs in the HTML.
6. Keyword piles: The same phrase added to every heading.
7. Overlong headings: Headings that run onto two lines and carry several ideas.

Most of these mistakes show up not during drafting but during later additions. For instance, as new sections get added to a post over the years, the hierarchy breaks down. That is why we suggest rereading the full heading list during every update.

How do you audit H2 and H3 subheadings on an existing post?

Older posts deserve as much heading care as new ones. We follow this order for an audit. First, we list the heading tags in the page source in order. Browser extensions or crawl tools pull that list out quickly. Then we compare the list with the headings we see visually on the page.

Next, we read the first paragraph under each heading. If a heading asks a question and the first paragraph does not answer it, we rework the section. Sometimes moving the answer up is enough. Other times, the heading itself needs to change to match what the section really covers.

After that, we check template parts such as the sidebar, footer and related posts boxes. If these areas carry needless H2 or H3 tags, we recommend fixing them at theme level. That way, a single fix reaches every page on the site.

Running this audit regularly takes time. Many of our clients hand heading and content structure audits to us as part of our SEO consulting work to lighten their content team's load. We find the issues, fix them and then track the change over time.

How do you improve subheadings with Search Console data?

Search Console shows which queries a page appears for. That data is the most honest source for improving subheadings. When you filter the Performance report by page and look at the queries list, you may notice the page showing up for questions you never planned for.

Example scenario: a guide on example.com earns impressions for queries about "drying time," but the page has no section on that topic. In this case, adding an H3 called "What does drying time depend on?" under an existing H2 makes the answer easy to find. Then you track clicks and impressions for the related queries over the next few weeks.

On the other hand, if a page appears for queries with very different intents, a new article may serve readers better than adding everything to one page. If you are new to the tool, start with our guide on what Google Search Console is and how to use it.

One more note: these changes are not a ranking promise. You need to keep watching the data and adjusting the page to what readers need.

Do subheadings make a difference in AI-powered search?

AI-powered search experiences also draw on page content. However, the details of which passages they use, and how, are not fully public. So it would be wrong to claim that a specific heading format will get you into AI answers.

Here is what we do know. A page split into clear sections, each answering its own question directly, is easier to understand for human readers. It is also easier for systems that evaluate content in parts. In other words, the good structure you build for classic search also works for newer search experiences without extra effort. Our post on how to write passages AI will quote covers this angle in more depth.

Rather than chasing a special "AI heading," we suggest going back to the basics: a clear question, a short answer, accurate facts and a source. Moreover, this approach stays valid even if search interfaces change, because the goal of the page stays the same.

When should you hand this work to an SEO team?

On a blog with a handful of posts, you can fix the heading structure yourself. However, the work grows on sites with hundreds of pages, template-driven heading issues or several writers with different habits. At that point, you need a system rather than one-off page fixes.

We usually build that system in three parts. First, we fix heading tags at theme and template level. Second, we write a heading guide for authors. Third, we set a regular update calendar based on Search Console data. As a result, new posts launch with the right structure from day one, and older posts get reworked in order of priority.

We can solve this kind of structure issue on your site and track the results together with you. To see the scope and how we work, send a quote request through our SEO consulting service page. We do not promise rankings, but we report clearly at every step what we change and why.

Quick checklist

Before you publish, answer these questions quickly:

• Does the flow of the article make sense when you read only the headings?
• Does each H2 cover a single question or step?
• Does each H3 belong to the topic of its H2?
• Do question headings get their answer in the first sentences of the section?
• Does the key phrase appear only in the headings that need it?
• Are visual headings also heading tags in the HTML?
• Do the table of contents links jump to the right section?

If you run this list on every new post and every major update, your heading structure will not decay over time. Then your readers and your content team work from the same map.

Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.