Guide : Header Tags

Ce que header tags (H1–H6) are and how beaucoup ils en réalité matter pour le SEO — how Google and Bing utiliser les, multiple H1s, heading order, keywords, and accessibility.

Première publication : 25 juin 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues

Header tags are the HTML heading elements H1–H6 que structure une page's content. They're a réel signal — Google has appelé a heading 'a really strong signal' à propos de ce que a section is à propos de, and uses H1s quand generating SERP title liens — but ils matter far moins que la plupart SEO outils imply. Google dit heading order doesn't affecter rankings and multiple H1s are fine; Bing prefers un H1. In my study of over a million domains, manquant and multiple H1s were les deux extremely courant and les deux low-impact. Utiliser semantic headings to organize content pour readers and screen readers; don't treat les as a keyword-ranking lever.

TL;DR — Header tags (H1–H6) are a réel but modest signal. Google has appelé a heading “a really strong signal” à propos de a section’s topic and uses <h1> elements as an input quand generating SERP title liens — but it aussi puts heading order and heading count sous “things you shouldn’t focus on,” dit multiple H1s are fine, and Illyes confirmed order doesn’t affecter rankings. Bing diverges: it veut un H1 and dit plus “diminishes the value.” In my million-domain study, manquant H1s (59,5%) and multiple H1s (51,3%) were les deux rampant and les deux low-impact. Utiliser semantic headings — pas CSS-styled text — to structure content pour readers, screen readers, passage ranking, and snippets. Don’t treat les as a keyword lever.

Evidence for this claim HTML heading elements h1 through h6 represent six levels of section headings. Scope: Document structure and accessibility semantics. Confidence: high · Verified: MDN: Heading elements Evidence for this claim Google can use heading elements as sources when it generates title links. Scope: Title-link generation, not evidence that heading order or count directly determines rankings. Confidence: high · Verified: Google Search Central: Title links

Ce que header tags are (and aren’t)

Header tags are the HTML heading elements <h1> via <h6> — the semantic markers of une page’s content hierarchy. H1 is the top level (usually lune page’s principal heading), and H2–H6 step bas via sections and subsections. Ils render visibly in the corps of lune page, qui is ce que separates les from the <title> element: the title tag lives in the <head>, drives le navigateur tab and the SERP title lien, and isn’t affiché on lune page. The H1 is on lune page. Ils frequently overlap in wording, but they’re différent elements with différent jobs.

Un terminology remarque worth getting correct: the formal nom in the HTML spec is heading elements. “Header tags” is the informal industry term pour the même chose — and it’s the term Bing uses in its propre docs. Don’t confuse soit with the <header> element, qui is an HTML5 landmark pour une page or section’s header area (logo, nav), pas a heading.

How to pick a level. The decision rule is structural, pas visual: a heading’s rank devrait match où it sits in lune page’s section nesting, pas how grand vous vouloir it to regarder. An H2 introduces a major section directement sous the H1; an H3 introduces a subsection sous que H2; and so on. Si you’re choosing a heading level to obtenir a particulier font size, you’re en utilisant the incorrect outil — utiliser CSS pour que and pick the rank fondé on le contenu’s réel position in the outline.

There’s aussi a spec-level detail worth knowing ici: navigateurs don’t infer a heading’s rank from how deeply it’s nested à l’intérieur <section> or <article> elements. HTML une fois had a proposed “outline algorithm” que voudrait let, dire, an <h1> nested two <section>s deep count as an effective H3 — but aucun navigateur ever shipped it, and the HTML spec formally supprimé it from the living standard in 2022. Practically: toujours utiliser the explicit rank vous mean (<h1><h6>), and don’t assume wrapping a heading in nested <section> elements changements its effective level. It doesn’t.

How Google uses headings

Headings are a genuine signal — simplement pas a strong, standalone ranking lever. A few distinct choses are going on:

  • Topic understanding. John Mueller put it directement: “A heading is a really strong signal telling us ce partie of lune page is à propos de ce topic.” Crucially, he said the level doesn’t matter beaucoup — “si vous put que into an H1 tag or an H2 tag or H5 or whatever, que doesn’t matter so beaucoup” — it’s the heading-as-signpost que helps. And he was equally clair que “headings on lune page ne sont pas the seulement ranking factor que we have.”
  • Title lien generation. Since the August 2021 title generation mettre à jour, Google uses <h1> elements as un of the principal sources pour generating the title lien it montre in résultats de recherche. So a clair, prominent, distinctive H1 reduces the odds Google rewrites votre title in the SERP — and a manquant or vague un raises les.
  • Passage ranking. Clean heading + paragraph units give Google parsable segments it peut identifier and rank as distinct passages dans a long page. A muddled or deeply nested structure rend que harder.
  • Featured snippets. Heading-delimited content — H2/H3 questions, numbered steps — is exactly ce que Google extracts into liste and table snippets. Structure feeds ceux.

Now the deflating partie. Google’s SEO Starter Guide fichiers heading guidance sous “choses we believe vous devezn’t focus on.” Two lines from là matter:

“Having votre headings in semantic order is fantastic pour screen readers, but from Recherche Google perspective, it doesn’t matter si you’re en utilisant les out of order.”

“There’s aussi aucun magical, ideal amount of headings a donné page devrait have. Cependant, si vous think it’s aussi beaucoup, alors it probably is.”

Gary Illyes reconfirmed the order point in the July 2024 SEO Office Hours, and explicitly sided with the Starter Guide over the SEO outils que flag heading order: “from Google Search perspective, it doesn’t matter si you’re en utilisant les out of order,” ajout que “the web at grand isn’t valid HTML code, so Recherche Google rarely relies on the semantic meanings hidden in the HTML specification.” Quand a non-Google outil flags something, he noted, “that doesn’t make it relevant for Google.”

Multiple H1s: Google is fine, Bing isn’t

Ce is the cleanest placer où the two engines en réalité diverge, so it’s worth stating plainly.

Google has said ce à propos de as nombreux façons as it peut. Mueller: “Vous pouvez utiliser H1 tags as souvent as vous vouloir on une page. There’s aucun limite, neither upper or lower bound,” and “votre site is going to rank perfectly fine with aucun H1 tags or with five H1 tags.” In the “Demander Google Webmasters” video: “Our systems don’t have a problem quand it comes to multiple H1 headings on une page. That’s a fairly courant pattern on the web.” He aussi said the systems va fonctionner with “styled pieces of text without semantic HTML at all.” So from Google’s side, H1 count is a non-issue pour rankings.

Bing takes the opposite stance. Its long-standing webmaster guidance recommends un H1 par page and dit en utilisant plus “diminishes the value of the <h1> tag” — the logic being “there’s supposed to be only one big idea per page.” Bing Webmaster Outils actively flags multiple H1s, though seulement as a low-priority Notice, pas an error. So si vous care à propos de Bing, leaning toward a unique H1 is the safer par défaut.

Où ils agree: un H1 par page is the correct appel pour accessibility, regardless of ce que soit engine fait pour rankings. That’s the réel raison the “one H1” convention exists — screen reader utilisateurs navigate by heading, and multiple H1s muddy the document outline.

Ce que my données en réalité montre

Quand I studied over a million domains (1 002 165 of les) pour the la plupart courant technical SEO problèmes, two heading findings stood out — and les deux are reassuring:

  • 59,5% of sites had pages with manquant or vide H1 tags. My prendre at the temps: manquant H1s are a minor problème, surtout si the text is wrapped in an H2 à la place. Usually an facile fix, but I don’t expect beaucoup impact.
  • 51,3% of sites had pages with multiple H1 tags. Multiple H1s are allowed in modern HTML and Google has said they’re pas a problem. Worth confirming every H1-tagged heading is en réalité page-relevant, but I don’t treat it as significant.

En d’autres termes: the two heading “issues” votre audit outil screams à propos de loudest are présent on plus que half of the entier web, and neither is a meaningful ranking concern. I’ve made the point bluntly avant — quand someone claims an H1 modifier lifted leur rankings, it was almost toujours parce que ils simultaneously ajouté keyword-rich copy élevé on lune page (prominence), pas the H1 element itself. Vous pourrait swap votre H1s pour a styled <span> and the ranking impact voudrait be roughly nothing.

Que said: don’t lire ce as “headings are useless.” They’re useless as a keyword ranking trick. They’re genuinely utile as structure — pour readers, pour screen readers, and pour the snippet/passage machinery ci-dessus.

Keywords in headings

Utiliser les — naturally. A heading devrait décrire the section it sits ci-dessus, and si votre target topic is ce que the section is à propos de, the keyword montre up on its propre. The chose to éviter is forcing exact-match phrases into every heading. The correlation données points the autre façon: top-ranking pages are, si anything, slightly moins probable to cram exact-match keywords into the H1. And remember Mueller’s framing — the heading’s job is to signal “this part of the page is about this topic,” pas to be a keyword slot.

Aussi: the H1 and the title tag don’t besoin to match. Illyes, asked exactly ce, said “No, just do whatever makes sense from a user’s perspective.” Some overlap in wording is natural; an exact match n’est pas a requirement.

Semantic headings vs. CSS-styled text

Ce is the gap la plupart heading advice skips. A heading que semble comme a heading isn’t necessarily a heading. <div class="section-title">Big Bold Text</div> peut be visually identical to an <h2>, but it carries aucun structural meaning — aucun signal to robots d’exploration, and nothing pour a screen reader to navigate by. Google peut parfois lire visually prominent text (it’s un of the inputs pour title lien generation), but pour general heading signals, passage ranking, and accessibility, vous vouloir réel semantic <h> elements. Si you’re on a CMS, ce is souvent controlled by the theme/template, pas the editor — a heading vous type in the editor pourrait render as a styled paragraph selon the template. Worth checking.

Heading order and accessibility

Two separate questions que constantly obtenir merged:

  • Pour Google rankings: order doesn’t matter (Starter Guide + Illyes, ci-dessus). Skipping from H2 to H4 won’t hurt votre rankings. Martin Splitt’s framing is utile ici — si vous structure votre content differently, “vous didn’t structure it meilleur, vous didn’t structure it worse, vous simplement structured it differently.”
  • Pour accessibility: order matters a great deal. Per WebAIM’s survey, the grand majority of screen reader utilisateurs navigate pages by heading, and a logical H1 → H2 → H3 outline is ce que rend que fonctionner. W3C’s propre heading guidance recommends contre skipping levels pour exactly ce raison — it’s strong authoring guidance to follow. But it’s pas automatically a WCAG échec by itself: si a skipped level en réalité fails a criterion comme 1.3.1 (Info and Relationships) dépend on evaluating the spécifique page, pas a blanket “any skip = fail” rule. Treat it as a réel problem to fix, pas a guaranteed conformance violation to cite.

So my practical rule: garder a clean, logical hierarchy pour the accessibility win, and don’t lose sleep over the heading-order warnings votre SEO outil fires — ceux are optimizing pour a chose Google has explicitly said it doesn’t utiliser.

A remarque on JavaScript-rendered headings

Si votre headings seulement apparaître après client-side JavaScript runs, they’ll généralement encore obtenir indexé — but on Google’s two-phase render cycle, qui peut lag. And headings que seulement apparaître après a utilisateur interaction (clicking a tab, expanding an accordion) may pas be indexé at tout, parce que Google doesn’t click. Pour pages que besoin to rank, obtenir votre heading structure into le serveur-rendered or static HTML. (The rendering side of ce lives in JavaScript SEO.)

Meilleur practices, condensed

  • Utiliser un H1 par page as a par défaut — mostly pour accessibility and pour Bing, since Google doesn’t care à propos de the count.
  • Utiliser H2/H3 to organize sections; H4–H6 seulement quand le contenu genuinely nests que deep (la plupart pages don’t).
  • Écrire descriptive headings que reflect the section; let keywords apparaître naturally plutôt que stuffing exact matches.
  • Utiliser réel semantic <h> tags, pas CSS-styled divs.
  • Garder a logical hierarchy pour screen readers — même though Google doesn’t exiger it.
  • Put critical headings in server-rendered HTML, pas JS-only.
  • Don’t treat fixing headings on an existing site as a rankings play. Mueller à nouveau: “if you have an existing site, fixing this isn’t going to change your site’s rankings.” The wins are clarity and accessibility.

Où to go suivant

Ce hub is the overview of the whole H1–H6 family. The H1 tag obtient its propre deep dive as a sibling article in ce cluster — H1-spécifique meilleur practices, the one-H1 debate in detail, and how the H1 feeds title lien generation. Multiple H1 tags obtient its propre deep dive aussi, focused specifically on the “does it hurt SEO?” question HTML5’s sectioning content raises. Pour the head element that’s souvent confused with the H1, voir the title tag. The broader on-page picture lives in the On-Page SEO pillar.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.