Can a page have more than one H1? The two honest answers
The spec answer: HTML5 introduced sectioning elements — <article>, <section>, <nav>, <aside> — and an outline algorithm under which each section could carry its own H1 and the document outline would nest correctly. Google's own guidance has for years said multiple H1s are fine and won't cause a problem.
The practical answer: that HTML5 outline algorithm was never implemented by any browser or screen reader. The W3C eventually dropped it from the spec guidance. So a page with five H1s produces a flat outline in assistive technology, where the user hears five top-level headings and no structure at all.
Which leaves a simple rule. Multiple H1s won't get you penalised. One H1 will get you understood. Use one, put it above the fold, and make it the plain-language answer to "what is this page".
H1 versus title tag — the same page, two different readers
These two elements get confused constantly because on badly built sites they're identical. They shouldn't be. Their readers are in completely different states of mind.
Someone reading your title tag is scanning ten results and hasn't committed to anything. That title has to carry the query wording and survive pixel truncation. Someone reading your H1 has already clicked; they want confirmation they've landed in the right place, in language that reads like a page rather than a search phrase.
Practically: share the core noun phrase, differ in everything around it. If the title is "Technical SEO Services in India — Audit in 10 Days", the H1 can be "Technical SEO services". The overlap is enough for relevance; the difference gives you a second natural phrasing on the page.
A heading outline for a 1,500-word page
Headings are structure, not decoration. Build the outline before you write the prose and the article usually writes itself — and the sections end up the right size, which is the part most drafts get wrong.
- Never skip a level. H1 → H3 with no H2 between them breaks the outline for screen reader users and reads as sloppy markup to a crawler.
- Headings are questions or stages, never "Introduction" or "Conclusion". A heading that carries no information is a wasted structural signal.
- Roughly one heading every 200–300 words on a page this long. Denser than that and the headings are labelling paragraphs, not sections.
| Level | Example heading | What it does |
|---|---|---|
| H1 | How much SEO costs in India | Names the page. One per page. Matches the reader's question in plain words. |
| H2 | The short answer, with real numbers | The snippet candidate. Direct answer, no preamble, roughly 150 words. |
| H2 | What changes the price | The main body section, ~500 words, broken by H3s. |
| H3 | Site size and technical debt | One idea, 150–200 words. Never an H3 with 40 words under it. |
| H3 | How competitive your keywords are | Sibling of the above. Same weight, same depth. |
| H2 | What you get at each budget | Table section. Tables under a clear H2 earn snippets. |
| H2 | How to check you're not overpaying | The practical close. Numbered steps, no summary section. |
Accessibility first, snippets second
Screen reader users navigate long pages by pulling up a list of headings and jumping — the same way you'd scan a page visually. That's the primary function of heading markup, and it's covered by WCAG's requirement that information and relationships conveyed visually are also available programmatically. A page where the headings are <div>s with big font sizes is unusable that way.
The SEO benefit follows from the same thing. Google lifts featured snippets from blocks that sit directly beneath a heading matching the query — a paragraph, a list, a table. If you want a section to be snippet-eligible, phrase the heading as the question and put the tight answer immediately under it. There is no markup trick here; the featured snippet goes to whoever formatted the answer most clearly.
Headings also do quiet work for internal linking, because a well-structured page generates jump-links and gives you obvious anchor points for links from elsewhere on the site.