Page Headings & the H1 Rule

Every page should have exactly one main heading — a single H1 — that describes what the whole page is about. Everything else is a subheading: H2 for sections, H3 and H4 for the levels nested under them, like the outline of a document.

Why only one H1?

• Search engines read the H1 as the page’s main topic. Two competing H1s blur that signal and can hurt how the page ranks.
• Screen readers let people jump through a page by heading level. One clear H1 tells them what the page is, and a clean H2–H4 outline lets them navigate it. Skipping levels or doubling up the top level makes that harder.

Think of it as a document outline: one title (H1), then sections (H2), subsections (H3), and so on — never two titles.

What you’ll see in the editor

In a rich-text field’s Heading dropdown:

• Fields meant to carry a page’s main heading (the page’s lead/intro content) offer H1–H4.
• Most other content fields offer H2–H4 only — on purpose. They’re for subheadings within the page, not a second page title.

So if a field won’t let you choose H1, that’s intentional. Use H2 for a section heading there.

The safety net

The site automatically enforces one H1 per page. When a page renders, it keeps the first H1 in the content and quietly changes any additional H1s to H2. So an accidental second H1 won’t damage your SEO.

That said — still author your headings correctly. The automatic fix simply keeps the first H1 it finds, which may not be the one you would have chosen as the page’s main heading.

Quick rules

1. One H1 per page — the page’s single main heading.
2. Use H2 for section headings, H3/H4 for subheadings nested beneath them.
3. Don’t skip levels for looks (for example H2 straight to H4). If a heading looks too big or too small, that’s a styling question for your developer — not a reason to change its level.
4. If a field only offers H2–H4, that’s by design — it isn’t the page’s main heading.