One Page, One H1: Why This Simple Rule Still Trips People Up

The rule is simple enough to state in one sentence: every page should have exactly one H1, and it should describe what the page is about. In practice, it's one of the most frequently broken conventions on real websites — not because people don't know the rule, but because page builders and themes quietly violate it by default.

The three ways this usually breaks

No H1 at all. Some page builders style a hero section's headline as a styled <div> or <span> instead of a real heading tag, because it was easier to hit a specific font size that way. The page looks fine. Search engines and screen readers see a page with no heading structure to anchor on.

Multiple H1s. A common pattern on templated pages: the site logo or header uses an H1 (because an early theme decision made it the "biggest, most important text on the page" by that logic), and then the actual page content has its own H1 further down. Now there are two competing signals for what this page is "about."

An H1 chosen for visual weight, not meaning. A page titled with something generic like "Welcome" as its H1, when the actual subject of the page — the product, the service, the article topic — is what should be carrying that signal.

Why it's worth fixing even though it's "just structure"

The H1 is one of the strongest on-page signals for topical relevance, and it's also the first heading a screen reader user hears when navigating a page by headings — a genuinely common navigation pattern for anyone using assistive tech. Getting it right serves both audiences with the same fix, which is rare enough in SEO work to be worth doing properly rather than patching around.

A quick audit: view a page's outline (most browser dev tools have an accessibility or heading-structure panel), count the H1s, and check whether the one that exists actually names the page's subject in plain language.