The Short Answer and Why the Nuance Matters

Yes, in almost every case the visible blog post title should be marked up as the H1, and there should be exactly one H1 on the page. That is the answer most people are looking for. But treating it as a rule to obey rather than a principle to understand leads to two common errors: teams that religiously match their H1 to their title tag character for character and lose click through rate, and teams that assume heading tags are purely decorative and end up with pages whose structure is incomprehensible to both crawlers and screen readers. Understanding what each element does lets you make good decisions in the edge cases where the simple rule does not fit.

How AAMAX.CO Handles On Page Structure

Heading hierarchy is one of those details that seems trivial in isolation and compounds enormously across hundreds of pages. At AAMAX.CO we are a full service digital marketing company providing web development, digital marketing and SEO worldwide, and because we build sites as well as optimise them, we frequently find heading structure broken at the template level rather than the content level. A theme that wraps the site logo in an H1, a widget that outputs H3 headings before any H2 exists, or a hero section that duplicates the post title as a second H1 will affect every page at once. Our search engine optimization audits check structure at the template layer first, then fix it once rather than page by page, which is both cheaper and more reliable.

H1 Versus Title Tag: Two Different Jobs

The title tag lives in the document head and is not visible on the page. Its primary audience is the search results page and the browser tab, so its job is to earn a click from a list of competing options. The H1 lives in the page body and is the first thing a visitor reads after arriving. Its job is to confirm that they landed in the right place and to introduce the content. Because the contexts differ, the optimal wording sometimes differs too. Title tags face a practical display limit of roughly sixty characters before truncation and often benefit from a brand suffix or a compelling qualifier. H1s have no length constraint and can be more expansive or more conversational. Search engines read both and use them as strong topical signals, but they are not interchangeable.

When They Should Match and When They Should Not

Keeping them identical is a perfectly good default, especially for informational content where the search query, the title and the page purpose all align neatly. Divergence is justified in a few situations. If your ideal on page headline runs long, you may need a shortened title tag that survives truncation. If you want to test click through rate variations, changing the title tag without disturbing the reading experience is the low risk way to do it. If the page targets a slightly different query set than its editorial headline suggests, the title tag can lean toward search language while the H1 stays natural for readers. Ecommerce and local pages frequently diverge deliberately, with a title tag carrying qualifiers and location while the H1 remains a clean product or service name. What you should never do is write two unrelated headings, because a mismatch between what a searcher clicked and what they see on arrival increases bounce and undermines both signals.

How Many H1s Should a Page Have

The HTML5 specification permits multiple H1 elements when they are scoped inside sectioning elements, and search engines have confirmed they can handle more than one without penalty. Despite that, one H1 per page remains the better practice for three reasons. It expresses a single unambiguous topic, which is exactly what you want a crawler to extract. It matches how assistive technology users navigate, since screen reader users often jump by heading level and expect one top level heading. And it prevents the sloppiness that multiple H1s usually indicate, because in practice a page with three H1s is rarely a deliberate sectioning decision, it is a template accident. The outline algorithm that was supposed to make nested H1s work was never implemented by browsers or assistive technology, so relying on it is a mistake.

Getting the Rest of the Hierarchy Right

Headings form an outline, and the outline should be logical. H1 states the page topic. H2 marks major sections. H3 marks subsections within an H2, and so on. Do not skip levels on the way down, meaning an H3 should not appear before any H2 has been established. Do not choose heading levels based on how large the text looks, which is what happens when writers use headings as styling shortcuts. Do not use headings for pull quotes, captions or calls to action that are not actually section titles. If you want smaller heading text, change the CSS rather than the tag. A well formed outline should let someone read only your headings and understand the shape of the argument, which is close to how both crawlers and skim readers process a page.

Writing an H1 That Works

Include the primary topic naturally, because the H1 is a genuine relevance signal, but write it for a human first. Avoid stuffing multiple keyword variants into one heading, which reads badly and adds nothing. Keep it specific enough that a reader immediately knows what the page delivers. Make it consistent with the promise of the title tag that brought them there. And use it to frame the value, particularly on how to and question style content where the H1 can state the outcome the reader will achieve.

CMS Traps That Break Structure

Many themes wrap the site name or logo in an H1 on every page, which means your blog post title becomes an H2 and the page's actual top level heading is your brand name. Some hero or featured image modules output the post title a second time, creating duplicate H1s. Sidebar widgets and related post blocks often emit H3 or H4 headings that interleave with your article outline in the source order even though they look separate visually. Page builders frequently default new text blocks to heading tags for styling reasons. The only reliable way to catch these is to inspect the rendered heading outline of a real page rather than trusting the editor view, and to check one page from every template type on the site.

What This Is Worth

Fixing heading structure is not a growth hack, and nobody should expect a traffic surge from changing an H2 to an H1. It is foundational hygiene: it clarifies topic for crawlers, improves accessibility for real users, makes content skimmable and prevents the compounding confusion that comes from hundreds of structurally broken pages. Do it once at the template level, write your headings as a genuine outline, and then spend your energy on the content itself. If you would like an audit that catches these structural issues across your whole site, our digital marketing team can run one, and we can also assess how well your content structure supports extraction and citation by AI systems through our GEO services, where clean headings matter more than ever.