A reader scanning a long blog post should understand the structure before reading every paragraph. Clear headings help them find what they need, while a logical heading hierarchy makes the document easier to navigate for assistive technology.
This guide explains the difference between H1, H2, and H3 headings in blog posts, shows a practical outline, and explains how to write headings for readers without repeating the same keyword in every section.
What do H1, H2 and H3 mean?
HTML headings describe levels of importance in the document structure:
- H1: The main subject or top-level title of a document or section context.
- H2: A major section under the main article topic.
- H3: A subsection that belongs under a relevant H2.
Additional heading levels exist, but most practical tutorials do not need many nested levels. A heading is not simply big or bold text; it communicates structure.
How headings work in a Blogger post
Most Blogger themes display the post title prominently and may mark it up as the page's H1. Before inserting another H1 inside the editor, inspect your live theme or page source. In many cases, the article body should begin with a paragraph and use H2 for the main sections.
Do not assume every template uses identical HTML. Blogger's visual editor and theme can also apply different styles to Heading and Subheading options, so check the output rather than relying only on the appearance in the editor.
A practical heading structure for a tutorial
Imagine a post titled “How to Create a Table of Contents in Blogger.” A sensible outline could be:
<h1>How to Create a Table of Contents in Blogger</h1>
<h2>What a table of contents does</h2>
<h2>Step 1: Add jump links</h2>
<h3>Choose link labels</h3>
<h3>Add section IDs</h3>
<h2>Step 2: Test mobile navigation</h2>
<h2>Common problems</h2>The H1 line represents the page title in this example. When using Blogger, don't paste a duplicate H1 into the body if your template already outputs the post title that way.
How to write a useful H2 heading
An H2 should make a promise about the next section. Compare these examples:
- Vague: “More Information”
- Clear: “Why a Blogger custom domain fails verification”
- Vague: “Tips and Tricks”
- Clear: “How to test a contact form before publishing”
Specific headings help readers decide what to read next. They can also naturally include words people use when searching, but do not force an exact keyword into every H2.
When should you add an H3?
Use H3 when an H2 section contains several related subtopics that benefit from separate labels. For example, under “Common problems,” you might have “Form doesn't send,” “Page missing from menu,” and “Mobile button doesn't work.”
If a section contains only one short paragraph, a new H3 may be unnecessary. Too many tiny headings can make the article feel fragmented.
Why heading hierarchy matters for accessibility
People using screen readers may navigate by headings to understand the page's organization. The W3C Web Accessibility Initiative's heading tutorial recommends using headings to communicate structure and nesting.
Try not to jump from H2 straight to H5 only because the theme's H5 text looks smaller. If you need a different visual size, change the styling without misrepresenting the structure.
Headings and SEO: what not to assume
Google's SEO Starter Guide encourages organized, easy-to-read content. It does not promise a special ranking bonus from putting a keyword in every heading or making every page follow an exact heading count.
A descriptive heading is useful because it helps readers and search systems understand what the following section covers. It cannot rescue irrelevant or inaccurate content.
Common mistakes in blog headings
- Repeating the full page title in every H2.
- Using headings only to make text look larger.
- Skipping levels without a structural reason.
- Writing vague labels such as “Introduction,” “More,” and “Conclusion” for every post.
- Adding an H3 that has no parent section.
- Using one giant H2 to contain the entire article.
- Changing heading labels without updating a manually built table of contents.
A five-minute heading audit
- Read only the page title and headings. Do they outline the article coherently?
- Can a visitor locate the main answer without reading all paragraphs?
- Does every H3 belong under a meaningful H2?
- Are keywords used naturally instead of repeated mechanically?
- Does the mobile page show headings with readable spacing and contrast?
If the heading-only outline feels confusing, reorganize the article before adjusting font sizes. When reviewing an older post, use the content refresh checklist to consider the headings alongside accuracy, links, and mobile readability.
Frequently asked questions
Can a web page have more than one H1?
HTML can contain multiple H1 elements in some structures, but a straightforward blog post usually benefits from a clear primary title. Do not add duplicate H1s to manipulate SEO.
Does every H2 need the main keyword?
No. Headings should describe the section accurately and in natural language. Keyword stuffing makes them harder to read.
Should I use H4 in a blog post?
Only if the content genuinely needs another nested subsection level. Most short and medium tutorials can stay clear with H2 and H3.
Are bold paragraphs the same as headings?
No. Bold changes emphasis, while HTML heading elements provide semantic structure for readers and assistive technology.
Final rule
Write headings as an outline of the reader's journey through the article. Use the right hierarchy, specific wording, and natural terms. The content beneath each heading must then deliver on its promise.