How Should H1, H2 and H3 Heading Tags Be Used for SEO?

Heading tags (H1-H6) are HTML elements that describe the outline of a page. The H1 states the main topic, H2s mark the main sections and H3s mark the sub-points within them. In SEO, the aim of using them correctly is not to stuff keywords but to let both readers and search engines grasp the page's structure at a glance.

Headings look like big, bold lines chosen to arrange a page, which is why they are among the most misused elements. But a heading tag is not a style; it is meaning. Below we cover how to build the hierarchy, the real situation behind the single-H1 debate, keyword placement and question format, accessibility and theme-related mistakes, in that order.

What are heading tags (H1-H6) and what are they for?

There are six heading levels from H1 to H6; the smaller the number, the higher the level. They work like the title, chapters and sub-chapters of a book. Headings make it easier for readers to scan a page, give screen reader users navigation points and tell search engines which topics the page covers.

In practice the first three levels are enough for most pages. H4-H6 may be needed in long technical documents or multi-layered guides. What matters is that levels nest in order: an H3 sits under an H2 and an H4 under an H3; jumping from an H2 straight to an H4 breaks the reading order.

How do you build a heading hierarchy?

The hierarchy should produce a meaningful outline when you extract the page's table of contents. The H1 describes the page as a whole, each H2 a main section and each H3 a sub-point of its H2. If someone who reads only the headings in a row can tell what the page is about, the hierarchy is built correctly.

• —H1: the main subject of the page; usually one, and at the top.
• —H2: main sections; each answers the page's topic from one angle.
• —H3: sub-headings of an H2; used only if the section has several sub-points.
• —H4 and below: only if needed in very detailed guides or technical documents.
• —Skipping levels: do not jump from H2 to H4; there should be an H3 first.
• —Equal level, equal weight: headings at the same level should be of similar scope.

A simple check: imagine deleting all the text on the page so only the headings remain. If what is left reads like a logical table of contents, the job is done.

Should a page have only one H1? Is using several H1s a problem?

HTML5 technically allows more than one H1, and there is no documentation saying Google penalises a page for having several; Google representatives have said repeatedly that it is not a problem. Still, the practical recommendation is to use a single H1, because it keeps the main topic clear, behaves consistently in accessibility tools and gives everyone on the team an easy rule.

The debate comes from the HTML5 “outline algorithm”. By that algorithm, each section can have its own H1 and the browser works out the level from context. But that algorithm was never actually implemented in any major browser or screen reader. In practice, browsers and assistive technology treat an H1 as an H1 and an H2 as an H2; there is no re-levelling by section. So a “one H1 per section” approach is not reliable.

• —Old myth: “Google penalises you when it sees multiple H1s.” There is no documented penalty.
• —The real risk: blurring the main topic and causing confusion in accessibility.
• —Practical rule: use one H1 per page; do not make the logo, menu or a promo bar the H1.
• —In a blog post the H1 is the post title; on a category page it is the category name.
• —On a one-page landing site the H1 carries the main promise of the offer; sub-sections become H2s.

How do you place keywords in headings?

The main keyword should appear naturally in the H1, while related sub-queries and synonyms should be spread across H2s and H3s in a way that fits the page's real content. Putting the same word in every heading is useless, tires the reader and looks like spam. Headings are written for people first, then for search engines.

• —H1: the phrase that carries the page's primary intent, for example “How do you set up a corporate website in Kocaeli?”.
• —H2: the sub-questions of the topic; use a different related phrase or question form in each.
• —H3: descriptive headings that split an H2 into examples, steps or options.
• —Natural language: do not line up “keyword + city” patterns that break sentence flow.
• —Synonyms and related terms: instead of repeating one word, use terms related to the topic.
• —Heading length: short enough to scan; avoid short slogan-style headings that do not give an answer.

Keyword choice is not the subject of this post; to decide which phrase belongs on which page, see the research step.

Why does writing headings as questions (AEO) work?

Headings written as questions match the user's real search one to one, so they make it easier to find the relevant section of the page in search results and in AI-assisted answer summaries. Writing a direct 40-60 word answer right under the heading creates a clean section that answer engines can quote.

This approach is called Answer Engine Optimization (AEO). The rule is simple: ask the question in the heading, give the answer in the first sentence, then add detail. You do not have to turn every heading into a question, though; natural headings such as “Cost items” or “Step-by-step implementation” are also fine. Forced questions annoy readers. And there is no guarantee: a well-structured section can raise the chance of being quoted but does not ensure it.

• —Make the heading a question phrased the way users type it: “What is a canonical tag?”
• —Put a clear 40-60 word answer right under it, starting with a definition or a decision sentence.
• —After the answer, add examples, step lists and exceptions.
• —Do not use two very similar question headings on one page.
• —If there is an FAQ section, do not repeat the main headings; choose complementary questions.

Why do headings matter for accessibility?

People who use screen readers often scan a page by jumping between headings; for them, headings are the table of contents. If the hierarchy is broken or headings were chosen for looks, that navigation fails. A correct heading structure is among the most basic parts of accessibility and it points in the same direction as SEO.

• —Do not skip levels; if an H4 follows an H2, a screen reader may announce it like an error.
• —Do not leave empty headings; empty H2/H3 tags used as spacing in a design create noise.
• —Make heading text meaningful on its own; avoid vague headings like “More” or “Details”.
• —Do not mark up navigation areas (menu, footer) with headings unless needed; use them for page content.
• —Test once with keyboard and a screen reader; it is the fastest way to see hierarchy mistakes.

What are the most common heading mistakes in themes and page builders?

The most common mistake is using a heading tag to make text look big and bold, and conversely leaving real headings as plain paragraphs. Themes and page builders also often output the logo, tagline area, widget titles and footer titles as heading tags without you noticing, so the H1s and H2s drift away from the page's real subject.

• —Heading for style: picking an H2/H3 so text looks big. Fix: choose the heading by meaning and set size with CSS.
• —Logo as H1: some themes make the logo the H1 on every page. Fix: do not make the logo an H1 outside the homepage; the page title should be the H1.
• —Widget and footer titles: if “Recent posts” or “Categories” in the sidebar or footer output as H2/H3, they disrupt the page outline. Fix: demote them or switch to a paragraph style.
• —Slider and hero: if every slide title is an H1, the page ends up with seven H1s. Fix: make only the main message the H1.
• —Bold paragraph: bold text that looks like a heading but has no tag. Fix: if it is really a section title, make it an H2/H3.
• —Skipped levels: jumping from H2 to H5 so it looks small in the design. Fix: keep the level and shrink it with CSS.
• —Duplicate headings: using the same heading in several sections. Fix: write each heading to fit its own section.

The easiest way to find these mistakes is to list the page's heading structure with browser developer tools or a crawler extension. If the list makes no sense, look at the theme settings or the template file.

What is the difference between a heading (H1) and a title tag?

The title tag is the page's name shown in the browser tab and in search results; the H1 is the main heading a visitor sees on the page. Both should describe the same subject, but they do not have to be identical. The title is written to win the click in results, and the H1 to reassure the person who arrives that they are in the right place.

• —Title: roughly 50-60 characters so it is not cut off in results; the brand name can go at the end.
• —H1: the main heading on the page, with no length limit but short and clear.
• —The same words can appear in both, but you do not have to copy the same sentence.
• —The title focuses on click appeal, the H1 on clarity on the page.
• —Google may use the page's H1 and other signals when showing a result title; if the title is weak, it may generate its own.

Writing titles and meta descriptions is a separate subject; see our meta title and description guide for details.

What does a sample heading skeleton look like?

A good skeleton can explain the whole page through its headings alone. Below is a simplified outline of a blog post titled “How do you set up a corporate website?” It is an illustration; adapt it to your own subject.

• —H1: How do you set up a corporate website?
• —H2: What is a corporate website and why is it needed?
• —H2: What decisions should be made before starting?
• —H3: Domain name and hosting
• —H3: Page structure and menu
• —H3: Content and images
• —H2: How does the step-by-step setup process work?
• —H2: Pre-launch checklist
• —H2: What are the common mistakes?
• —H2: What do cost and duration depend on?

In this skeleton, H2s sit directly under the H1, H3s appear only under an H2 with several sub-points, questions are written as questions and no level is skipped. Writing the outline first and then filling in the text prevents hierarchy problems from the start.

How much do headings affect rankings? What is a realistic expectation?

Heading tags are not a powerful ranking lever on their own; their effect is small next to content quality, links and overall page experience. Even so, a correct heading structure indirectly helps content comprehension, user satisfaction and answer quotations. A wrong structure loses that help and is often a sign of other problems too.

That is why it is right to treat headings as a clean-up step, not as a “trick”. Fixing heading structure is a cheap, low-risk improvement, but expecting a miracle in rankings leads to disappointment. The real gain is that on a page with a sound heading structure, the content and links work better.

A practical checklist for heading structure

Go through the items below in order before publishing a new page or when auditing an existing one. If all of them hold, the heading structure is usually trouble-free.

• —Is there one H1 that clearly describes the topic?
• —Is the H1 the real page title, not the logo, menu or a promo bar?
• —Do H2s describe main sections and H3s sub-points?
• —Are any levels skipped, for example H2 straight to H4?
• —Can someone who reads only the headings understand the page?
• —Are any headings duplicated, empty or chosen only for style?
• —Are the important questions written as headings with a short answer below?
• —Do widget, footer and slider headings pollute the page outline?
• —Do the title tag and the H1 describe the same subject but optimised separately for click appeal?

To run this check on your own site, start with your five highest-traffic pages. Even a few minutes per page often reveals systematic theme-related mistakes. In technical SEO audits at 404 Ajans we also review heading structure at theme level and trace the fix down to the template file; still, the list above is clear enough for your own team to apply.