This guide exists to fix that. Whether you’re a WordPress site owner managing your own content, or an agency building sites for dozens of clients, you’ll leave here knowing exactly how to auditer, diagnostiquer et r\u00e9soudre d\u00e9finitivement <\/a>le probl\u00e8me de l'ordre des titres dans WordPress.<\/p> An H1 tag (\uff1ch1>) is the top-level HTML heading element. In semantic HTML, it signals to browsers, search engines, and assistive technologies: “This is the primary topic of this page.”<\/strong><\/p> Consid\u00e9rez les balises de titre comme un plan de document :<\/p> Skip a level — jumping from H2 to H4 — and you break the outline. Use two H1s and you create structural ambiguity. Use H3 tags for visual styling and you introduce ghost headings that confuse crawlers.<\/p> In WordPress specifically, this gets complicated fast. Unlike a static HTML page where you write every tag manually, WordPress generates heading markup from at least four different sources simultaneously: the theme’s header template, the post title, the editor content, and any widgets or page builder modules you’ve added.<\/p> Let’s settle the d\u00e9bat sur le classement<\/a> d\u00e8s maintenant.<\/p> In July 2026, Google’s Gary Illyes addressed this directly during the SEO Office Hours podcast: arranging headings in semantic order is genuinely helpful for accessibility (especially screen reader users), but it doesn’t significantly impact Google’s ranking algorithms. John Mueller has also stated that multiple H1 tags on a page don’t confuse crawlers and have zero direct SEO impact.<\/p> Alors, est-ce que tout cela a de l'importance ?<\/p> Yes — but not for the reason most SEO guides say.<\/p> Les vraies raisons de se soucier de la structure des titres dans WordPress sont :<\/p> Comprendre pourquoi<\/em> la structure des titres WordPress est rompue n\u00e9cessite de comprendre les quatre endroits d'o\u00f9 ils sont g\u00e9n\u00e9r\u00e9s.<\/p> Most WordPress themes output the site title in the header area. Older and poorly coded themes wrap this in an \uff1ch1> tag — on every single page. This means every page on your site starts with the same H1: your brand name.<\/p> Ensuite, lorsque le titre de la page ou de l'article s'affiche (ce qui devrait<\/em> \u00eatre le H1), il devient soit un second H1, soit est r\u00e9trograd\u00e9 en H2.<\/p> Here’s what this looks like in a broken theme’s php<\/p> d'un th\u00e8me d\u00e9fectueux. \u00c0 quoi cela devrait ressembler :<\/p> php<\/p> This is one of the most common WordPress H1 issues and it’s entirely invisible unless you inspect the page source. You can have an SEO plugin, a green readability score, and un contenu parfait<\/a> — and still be outputting duplicate H1s on every page.<\/p> The WordPress block editor introduced deliberate changes to H1 behavior. By default, Gutenberg de-emphasizes the H1 option in the Heading block — the assumption is that the post title is already rendering as H1, so content-area headings should start at H2.<\/p> En pratique, cela cr\u00e9e deux probl\u00e8mes :<\/p> Probl\u00e8me A :<\/strong> Certains th\u00e8mes ne pas<\/em> output the post title as H1. If your theme renders the title in a \uff1cdiv> or \uff1ch2> for stylistic reasons, and Gutenberg has hidden H1 from the heading block options, you end up with zero H1 tags on the page.<\/p> This is exactly the situation flagged in a long-running GitHub issue in the Gutenberg repository — users requesting the ability to remove the H1 option entirely for enterprise and agency setups where the H1 is controlled at the template level. The issue highlights real confusion: the editor’s default behavior and the theme’s template need to be explicitly coordinated, but WordPress provides no automated check for this.<\/p> Probl\u00e8me B :<\/strong> Content editors can still select H1 in the block editor by changing the heading level. If your theme already outputs the post title as H1, an editor adding another H1 block inside the content area creates a duplicate — and no warning appears.<\/p> Les constructeurs de pages sont la plus grande source de chaos dans la hi\u00e9rarchie des titres sous WordPress.<\/p> Here’s why: page builders give you granular visual control. You can drag a text element anywhere, style it any way, and assign any heading level. This is powerful for design. It’s disastrous for structure.<\/p> Le probl\u00e8me de titre typique avec un constructeur de page ressemble \u00e0 ceci :<\/p> The result is a heading structure that’s visually coherent but semantically meaningless. Screen readers and crawlers parsing this get a content outline that jumps around like a broken table of contents.<\/p> InspectWP’s documentation identifies this pattern explicitly: authors and page builder users choose heading levels based on how they apparence<\/em> rather than their logical meaning — if H3 is the right visual size, they select H3, even with no H2 above it.<\/p> WordPress widget areas — sidebars, footers, header modules — often output their own headings. A “Recent Posts” widget might render as H2. A promotional banner built into the theme might use H3. None of these are part of the content outline, but they appear in the page’s heading structure.<\/p> This creates heading “noise” that inflates the apparent complexity of the outline and can push content headings out of their correct hierarchical position.<\/p> \u00c0 quoi cela ressemble :<\/strong> Every page on your site has two H1s — your site name and your post title.<\/p> Qui est concern\u00e9 :<\/strong> Sites using older themes, poorly built premium themes, or any theme where the developer used \uff1ch1> for the site branding.<\/p> Comment le d\u00e9tecter :<\/strong> Right-click any page → Inspect → search for \uff1ch1 in the Elements panel. If you see your site name wrapped in H1 in the \uff1cheader> section, you have this problem.<\/p> Comment le corriger :<\/strong><\/p> Option 1 : Modification du th\u00e8me enfant (approche d\u00e9veloppeur)<\/em> In your child theme’s php<\/p> Option 2 : CSS + aria-label (solution sans code)<\/em> If you can’t edit theme files, use CSS to reset the H1 styling on the site title:<\/p> css<\/p> Remarque : cela masque le probl\u00e8me visuel<\/em> H1 problem but doesn’t fix the structural issue. The H1 tag remains in the markup.<\/p> Option 3 : Passer \u00e0 un th\u00e8me bien structur\u00e9<\/em> Themes following WordPress coding standards (Twenty Twenty-Four, Kadence, GeneratePress, Astra) handle this correctly out of the box. If your current theme has this issue and you’re not a developer, switching is often the most reliable fix.<\/p> \u00c0 quoi cela ressemble :<\/strong> Your homepage has zero H1 tags. SEO plugins report “No H1 found.”<\/p> Qui est concern\u00e9 :<\/strong> Sites that use a logo image for branding (hiding the site title), sites using a static front page with no title visible, or sites where the theme’s homepage template doesn’t call This is a real and recurring issue in the WordPress support forums. The cause is typically this sequence: the site title is set to display in the header, but the user hides it (or replaces it with a logo), removing the only H1 from the page. Since the homepage often doesn’t have a “post title” in the way a blog post does, there’s no automatic H1 generated.<\/p> Comment le corriger :<\/strong><\/p> Pour la page d'accueil sp\u00e9cifiquement :<\/em> Ajoutez un H1 \u00e0 votre section hero ou \u00e0 votre mod\u00e8le de page. Cela peut \u00eatre :<\/p> Dans Gutenberg :<\/em> Ajoutez un bloc En-t\u00eate en haut du contenu de votre page d'accueil, r\u00e9glez-le sur H1 et int\u00e9grez-le \u00e0 votre message principal.<\/p> \u00c0 quoi cela ressemble :<\/strong> La structure du contenu passe directement de H2 \u00e0 H4, ou de H1 directement \u00e0 H3.<\/p> Qui est concern\u00e9 :<\/strong> Toute personne r\u00e9digeant du contenu long qui utilise les en-t\u00eates pour le style visuel plut\u00f4t que pour la structure s\u00e9mantique.<\/p> Pourquoi est-ce important :<\/strong> As InspectWP notes, skipping heading levels happens when authors choose levels based on appearance — the H3 looks right, so they use H3, regardless of whether an H2 precedes it.<\/p> Comment le d\u00e9tecter dans Gutenberg :<\/strong> Cliquez sur l'ic\u00f4ne d'information (\u24d8) dans la barre d'outils sup\u00e9rieure de l'\u00e9diteur de blocs. Le panneau Plan du document affiche chaque en-t\u00eate dans l'ordre et signale les niveaux saut\u00e9s avec un avertissement.<\/p> Comment le corriger :<\/strong><\/p> \u00c0 quoi cela ressemble :<\/strong> A page built with Elementor or Divi has three or four H1 tags because each major section has its own hero-style “H1” headline.<\/p> Comment le corriger :<\/strong><\/p> In Elementor: Edit each heading widget → check the HTML Tag setting → set only the primary page title to H1, and change all others to H2 or H3 as appropriate.<\/p> In Divi: Edit heading modules → under Advanced → HTML Tag → change to the correct semantic level.<\/p> In Beaver Builder: Each heading module has a “Heading Tag” setting in the Style tab. Audit each one.<\/p> \u00c0 quoi cela ressemble :<\/strong> Your theme doesn’t output the post title as H1, and Gutenberg has hidden the H1 option in the Heading block. Your pages have no H1.<\/p> Comment le corriger :<\/strong><\/p> For developers managing a site where the H1 must be placed inside the content area, you can restore the H1 option using a filter in your theme’s php<\/p> Alternatively, switch to the “Edit as HTML” view for the Heading block and manually set \uff1ch1> in the markup.<\/p> Pour les configurations d'agence o\u00f9 vous souhaitez emp\u00eacher<\/em> les \u00e9diteurs d'ajouter des H1 (car le mod\u00e8le les contr\u00f4le), utilisez le Utilisez le plugin SkySEOManager <\/a>et son analyseur SEO int\u00e9gr\u00e9 pour trouver tous les probl\u00e8mes li\u00e9s aux titres.<\/p> Lisez notre guide complet : comment auditer votre site WordPress en utilisant SkySEOManager pour tous les probl\u00e8mes de r\u00e9f\u00e9rencement<\/a><\/p>Qu'est-ce qu'une balise H1 et pourquoi est-ce important dans WordPress ?<\/h2>
H1 – Main page title (only one per page)\n \u251c\u2500\u2500 H2 – First major section\n \u2502 \u251c\u2500\u2500 H3 – Subsection\n \u2502 \u2514\u2500\u2500 H3 – Another subsection\n \u251c\u2500\u2500 H2 – Second major section\n \u2502 \u251c\u2500\u2500 H3 – Subsection\n \u2502 \u2502 \u2514\u2500\u2500 H4 – Detail within subsection\n \u2514\u2500\u2500 H2 – Third major section<\/code><\/pre>Ce que Google dit r\u00e9ellement sur les balises H1<\/h3>
\n
Comment WordPress g\u00e9n\u00e8re les balises de titre : Les quatre sources de conflit<\/h2>
Source 1: The Theme’s Header Template<\/h3>
header.php<\/code>:<\/p>\/\/ Broken — site title as H1 on every page\n\uff1ch1\uff1e\uff1c?php bloginfo('name'); ?\uff1e\uff1c\/h1\uff1e\n\uff1ch2\uff1e\uff1c?php the_title(); ?\uff1e\uff1c\/h2\uff1e \/\/ Post title wrongly demoted<\/code><\/pre>\/\/ Correct — site title is a link or span, post title is H1\n\uff1cp class=\"site-title\"\uff1e\uff1ca href=\"\uff1c?php echo home_url(); ?\uff1e\"\uff1e\uff1c?php bloginfo('name'); ?\uff1e<\/strong>\uff1c\/a\uff1e\uff1c\/p\uff1e\n\uff1ch1\uff1e\uff1c?php the_title(); ?\uff1e\uff1c\/h1\uff1e<\/code><\/pre>Source 2 : L'\u00e9diteur de blocs Gutenberg<\/h3>
Source 3 : Constructeurs de pages (Elementor, Divi, Beaver Builder)<\/h3>
\n
Source 4 : Widgets et composants de th\u00e8me<\/h3>
Les 5 probl\u00e8mes les plus courants de hi\u00e9rarchie H1 et d'en-t\u00eates dans WordPress<\/h2>
Probl\u00e8me 1 : Le titre du site est envelopp\u00e9 dans un H1 sur chaque page<\/h3>
header.php<\/code>, find the site title output and change it from \uff1ch1> to \uff1cp> or \uff1cspan> with appropriate classes:<\/p>\uff1cp class=\"site-title\"\uff1e\n \uff1ca href=\"\uff1c?php echo esc_url(home_url('\/')); ?\uff1e\" rel=\"home\"\uff1e\n \uff1c?php bloginfo('name'); ?\uff1e<\/strong>\n \uff1c\/a\uff1e\n\uff1c\/p\uff1e<\/code><\/pre>.site-header h1.site-title {\n font-size: inherit;\n font-weight: inherit;\n margin: 0;\n}<\/code><\/pre>Probl\u00e8me 2 : Absence de H1 sur la page d'accueil<\/h3>
the_title()<\/code>.<\/p>\n
position: absolute; clip: rect(0 0 0 0);<\/code>) qui fournit le marqueur s\u00e9mantique sans perturber la conception visuelle<\/li>\n<\/ul>Probl\u00e8me 3 : Niveaux d'en-t\u00eate saut\u00e9s dans le contenu<\/h3>
\n
Probl\u00e8me 4 : Plusieurs balises H1 provenant des constructeurs de pages<\/h3>
Probl\u00e8me 5 : Le probl\u00e8me de visibilit\u00e9 du H1 dans Gutenberg<\/h3>
functions.php<\/code>:<\/p>\/\/ Allow H1 in the Heading block\nadd_filter( 'allowed_block_types_all', function( $allowed_blocks ) {\n return $allowed_blocks;\n});<\/code><\/pre>block_editor_settings_all<\/code> filtre pour restreindre les niveaux de titre dans l'\u00e9diteur.<\/p>Comment auditer la structure des titres de votre site WordPress (\u00e9tape par \u00e9tape)<\/h2>
M\u00e9thode 1 : Plugin gratuit SkySEOManager<\/h3>
M\u00e9thode 2 : Utilisez l'analyseur SEO gratuit de Siteskyline<\/h3>
<\/figure>