Headings and Content Structure

Headings and content structure is a topic where the checklist rules sound stricter than they are. Google does not publish rules about the order or the number of headings, but it does document how it uses a page's prominent text for the title link, and it mentions headings as a means of navigation. The rest is the HTML standard and accessibility guidance. This lesson separates three things: what Google says, what W3C and MDN say, and what remains habit.

It rests on the title links documentation, the W3C headings guide and the MDN reference on heading elements.

What headings are for, per the documentation

In Google's starter guide headings are a tool for the reader: break up long content into paragraphs and sections, and provide headings to help users navigate your pages. It also says content should be well written, easy to follow, and free of spelling and grammatical mistakes. That is the only direct purpose the guide gives headings; it assigns them no weight or "signal strength".

There is a second, indirect one: headings are among several sources Google composes the title link from, alongside the main visual title and other large, prominent text. That affects what a user sees in the results — see the lesson on titles and meta descriptions.

How many H1s: three different answers

"How many H1s should a page have" gets a single number, although three sources say different things.

The honest and unglamorous conclusion: one H1 is a sensible choice, because it spares Google from choosing and matches practice, but the claim that "a second H1 is an error Google reads as nonsense" is not in the documentation. It is neither a penalty nor a violation.

Levels without gaps

This one is clearer, and the basis is accessibility, not search. W3C: nest headings by rank; skipping heading ranks can be confusing and should be avoided where possible — an h2 should not be followed directly by an h4. The exception is closing a subsection: an h2 beginning a new section can follow an h4. MDN explains why: a common technique among screen reader users is to jump quickly from heading to heading to work out the content of the page, and a skipped level may leave the person wondering where the missing heading is.

The same page has a second rule that is often broken: do not use heading elements to resize text — use the CSS font-size property for that. A heading is structure, not style.

Prominence and markup must agree

The one place where Google's documentation links appearance and meaning directly is the title link, which takes into account the main visual title, heading elements and other large, prominent text. The practical conclusion for layout: what looks like the main heading to a reader should be the main heading in the markup. If large text is set as a div while the real h1 is hidden or small, Google and the reader see different things, and the title link may be replaced. The test is simple: what is the largest and first thing on the page, and is it a heading.

Semantic tags: what is known

The claim that "article, section, nav and main give Google additional context" does not appear in Google Search documentation. MDN, for its part, points to a piece called "there is no document outline algorithm": nested sections do not recompute heading levels, so the headings themselves set the structure. Semantic tags are useful for accessibility and for maintaining the markup; as a search signal they are not described. They are worth using, without promising yourself rankings.

The structure of readable text

What of structure is confirmed by the documentation, and in what role:

• Paragraphs and sections with headings. They help users navigate.
• A distinguishable main content. Among the page experience self-assessment questions is whether visitors can easily distinguish the main content from other content on the page. Headings are the main way to ensure that.
• Completeness and usefulness. The documentation asks whether a piece provides original information, research or analysis and a substantial, complete description of the topic. Structure helps show that completeness but does not replace it.
• Lists and tables. Their value for a scanning eye is practice; in the Google guidance reviewed they are not described as a signal.

Principles of the text are in the lesson on SEO writing, and word placement in the lesson on keyword targeting. What to do about uniqueness is covered in the next lessons: content uniqueness and duplicate content. In brief, the line: Google names as abuse republishing content from other sites without adding any original content or value.

How to audit a page's structure

1. List all the headings in order. Page analysis shows the H1–H3 outline of one page and itself flags multiple H1s; the site crawler collects the H1 of every page, so pages with no H1 or with repeated ones show up.
2. Read only the headings. If they convey the topic and the logic of the text, the structure works. If not, the problem is the content, not the tags.
3. Check the levels. Look for jumps such as h2 → h4 and headings used only for font size.
4. Compare the main heading with the title. They need not match but must not contradict, or the title link may be replaced.
5. Check readability. Readability, text quality and spelling.

What is not in Google's documentation

These widespread claims do not appear in the documentation, so they cannot be presented as rules:

• "two H1s — the structure is broken, Google reads it as nonsense": Google describes only that with several equally prominent headings it may use the first;
• "H2s are for LSI keywords" and "H1 once with the main keyword" as ranking mechanics;
• "semantic tags give Google additional context";
• "Google reads CSS and understands the visual hierarchy": what is documented is only that prominent text takes part in building the title link;
• the case "we fixed the hierarchy — the page began to tell its topic clearly" as proof.

That does not mean the opposite is true. It means a tidy structure is first of all convenience for the reader and accessibility, not a ranking lever.

Checklist

1. The page has one clear main heading, distinctive and the most prominent.
2. Levels are nested by rank, with no gaps such as h2 → h4.
3. Headings are not used for font size.
4. The text reads like a table of contents through its headings.
5. The main heading is consistent with the title.
6. Long text is broken into paragraphs and sections.
7. Spelling and readability checked.

Mistakes

• Large text in a div instead of a heading, with the real h1 small or hidden.
• h3–h4 used only for font size.
• Level jumps that confuse screen reader users.
• Several equally prominent large headings with no clear main one.
• Expecting a rise in position from semantic tags.
• Treating structure as a substitute for content.

What comes next

The next lesson is about content uniqueness: content uniqueness.