Yoast's single title check and the one H1 convention

What the check can see

Yoast analyzes the content you write in the editor. In most WordPress themes, the post title is printed as an H1 by the theme template, outside that content. That has a consequence worth knowing:

• Two H1 blocks in the content: red, as expected.
• One H1 block in the content: green, even though the published page now has two H1s, the theme's title and yours.
• No H1 in the content: green, and usually correct, because the theme supplies the title.

So the check catches the obvious case but not the most common one. If you add a Heading block and leave it set to H1 because it looks right, the check stays green while the page gains a second H1. View the page source, or use your browser's accessibility tools, to see the real heading outline of the published page.

Where the one H1 rule comes from

Early SEO advice treated the H1 as the most heavily weighted heading, so the idea spread that there must be exactly one and that it should contain the keyword. Around the same time, the HTML5 draft described an outline algorithm under which every section could have its own H1 and browsers would work out the levels. Browsers and screen readers never implemented that outline, and it was eventually removed from the HTML specification. In practice, heading levels are read as written.

That left a convention that still makes sense for a different reason: people using screen readers often list a page's headings or jump between them, and a single H1 tells them where the page's main title is. WCAG does not forbid multiple H1s, but a clear, logical heading structure is part of making content accessible.

Does Google care?

Not much. Google's representatives have said publicly that its systems handle multiple H1 headings fine, and that headings are one of many ways Google understands a page's structure. A page with two H1s will not be penalized, and fixing it will not produce a ranking jump.

That makes this check a low-priority fix for rankings and a reasonable one for quality. If you are cleaning up a template, a page builder layout or a batch of imported posts, fixing the heading levels is worth doing. If a single post has a stray H1, change it when you next edit.

Fixing extra H1s in the editor and in builders

In the block editor, select the heading, open the block toolbar and change the level from H1 to H2. Subsections below it become H3. Style headings with your theme or block settings rather than choosing a level for its size.

Page builders are where extra H1s usually come from, because every heading element has its own tag setting. Hydrogen SEO's Elementor guide and Divi guide both recommend choosing tags for structure (one H1, then H2s and H3s in order) and using the design settings for the visual size.

Two related problems to check while you are there: a page with no H1 at all, which happens when a theme or builder layout hides the title, and heading levels that jump from H2 straight to H4. Both are covered in missing H1 tag and heading hierarchy skipped.

Hydrogen SEO does not run a per-post H1 check in its SEO score. The Content structure area of its site health score looks at heading hierarchies across your site instead.

Patterns deserve a look too. If a synced pattern you insert into many posts starts with an H1 heading, every one of those posts carries the extra H1. Change the heading level in the pattern once and every post that uses it updates.