How to Use H1, H2, and H3 Headings on a Business Website

Headings are labels for sections, not text styling

An H1, H2, or H3 element gives text a structural meaning in HTML. The number states the heading's level: H1 for a top-level section, H2 for a subsection, H3 for a sub-subsection, and so on. A designer can make any of them large, small, bold, light, or visually hidden with CSS, but changing the appearance does not change the semantic level. Pick the element that describes the content relationship, then style it.

W3C accessibility guidance says headings communicate content organization and can support in-page navigation in browsers, plug-ins, and assistive technologies. Clear labels are helpful for people who scan visually, navigate with a screen reader's heading list, have limited short-term memory, or simply want the answer quickly. That user value is the main reason to build a sound outline. Explore the SEO and AI-search article library for related guidance on titles, internal links, schema, and site structure.

Give each level a defined job

Most small-business pages need only H1 through H3. That is not a search rule; it is a sign that the content probably does not require a six-level document outline. Long policies, technical documentation, or research may justifiably go deeper. If a service page repeatedly needs H4 and H5, consider whether one section deserves its own page or whether the writing can be simplified. The SEO services team can review heading structure alongside page purpose, metadata, accessibility, and internal pathways rather than isolating it as a keyword exercise.

Use one clear content H1 as a convention, not a myth

The HTML standard defines H1 as a top-level heading, and valid documents can contain more than one top-level section. That does not make every repeated H1 helpful. For a typical business web page, one prominent H1 for the main content gives editors, designers, accessibility reviewers, and search systems an unambiguous page title. Use that as a maintainable house rule. Multiple H1 elements are not evidence of a penalty by themselves, but accidental H1s in a logo, modal, card grid, and footer can make the outline noisy and the main topic less obvious.

The title tag and H1 may use slightly different wording. A title might add a concise brand, while the H1 reads naturally on the page. They should still describe the same destination. Google's title-link documentation says its systems may use the title element, main visual title, heading elements, and other prominent text. Several contradictory, equally prominent titles make that source material less clear. The separate guide to writing title tags and meta descriptions explains how those two labels work together.

Build H2 sections around buyer decisions

H2 headings should divide the main topic into the parts a reader needs to understand or act. On a service page, those parts are rarely a string of keyword variations. They are usually fit, scope, method, proof, price factors, timing, risk, service area, and next steps. Write the section first in question form if that helps—What does the inspection include?—then decide whether the question or a direct label serves the page better.

The outline does not need a heading above every paragraph. Two or three short paragraphs can live under one clear section. Add a subheading when it identifies a meaningful new part, supports navigation, or makes a long passage easier to scan. Do not add headings merely to repeat a query. A section titled Roof Repair Services followed by H3s called Best Roof Repair, Affordable Roof Repair, and Local Roof Repair creates no useful conceptual relationship.

Nest H3 headings only when the H2 needs subdivisions

• An H3 names a part of the H2 topic, not a separate major page topic
• Sibling H3 headings use parallel wording when they perform the same role
• A new H2 closes the earlier H3 subsection and starts a new major section
• Heading ranks normally move one level deeper at a time: H2 to H3, not H2 to H4
• Moving back up can skip levels because the deeper subsection has ended—for example, H4 back to H2
• A short section with no meaningful subdivisions does not need an H3
• Visual size is controlled in CSS so semantic level does not become a design compromise

W3C's page-structure tutorial advises nesting by rank and avoiding skipped levels where possible because skips can be confusing. The same guidance notes that a higher-level heading can follow a deeper one when it closes those subsections. In other words, H2 → H3 → H4 → H2 can be coherent, while H2 → H4 without an H3 usually hides a missing relationship. Automated accessibility checks can flag suspected skips, but a person should review whether the written outline makes sense.

Write headings that remain useful outside the layout

WCAG 2.2 Success Criterion 2.4.6 requires headings and labels, when provided, to describe topic or purpose. They do not have to be long. Specific wording helps a person scanning visually and a screen-reader user choosing from a heading list. It also forces the writer to notice thin or duplicate sections. Avoid putting the same exact phrase in every heading; natural synonyms are fine when they clarify distinct ideas, but the outline should not read like a bag of keywords.

Audit the rendered page, not just the editor