Headings are the labeled signposts on a webpage — one H1 for the page's main topic, H2s for its major sections, H3s for the details underneath. Get that order right and both Google and your visitors can find their way around. Get it wrong and everyone, human or machine, has to work harder to understand your page.
A heading — H1, H2, H3, and so on down to H6 — marks a line of text as a title for the section that follows it. Visually, headings usually just look like larger or bolder text, but underneath the surface they carry meaning: they tell a browser, a screen reader, or a search engine "this is the start of a new topic, and here's how important it is relative to everything else on the page."
Google reads a page's headings the way a person skims it before reading closely, using their size and order to build a rough outline of what the page covers. When that outline is logical — one clear topic, broken into a handful of clean sub-topics — Google can match the page to the right searches with much less guesswork. When headings are missing, out of order, or don't describe what follows them, that outline falls apart and the page becomes harder to rank accurately.
Every page should have exactly one H1, and it should state, in plain language, what the page is about. Think of the H1 as the title of a chapter in a book — a book doesn't have three chapter titles competing for the same chapter, and a webpage shouldn't have three H1s competing to explain what the page is for.
Modern browsers don't throw an error over two or three H1s on a page, which is exactly why the mistake survives so long unnoticed — nothing visibly breaks. What breaks is clarity. When Google finds multiple H1s, it has to decide which one actually represents the page's primary topic, a guess it would rather not have to make. We see this most often on sites built with page-builder software, where the template inserts an H1 automatically and someone later added another by hand without realizing it.
When we audit a page's heading structure, we strip away everything except the headings and read them in order. If what's left reads like a sensible table of contents — a person could understand roughly what the page covers just from that list — the structure is working. If the list is repetitive, out of order, or missing obvious sections, it's costing that page ranking potential.
Take a plumbing company's emergency-services page for a New York town. The H2s carry the major sections a searcher and Google both care about — what counts as an emergency, the services offered, the areas served, the FAQ — while H3s only appear underneath an H2 whose topic needs to be broken into smaller pieces, such as separate emergency types nested under the services section. Every H3 sits beneath a parent H2, and the outline never jumps from an H1 straight to an H3, skipping the level in between.
That pattern — major sections carried by H2s, sub-topics carried by H3s, no skipped levels — is what we build into every page we touch, and it's what we fix first when we inherit a site where headings were added for visual styling instead of structure.
Templates that auto-generate a heading, plus a manually added one, or pages with no true H1 at all — just styled text pretending to be one.
Jumping from an H1 straight to an H3, or an H2 straight to an H5, because it "looked right" visually rather than following the logical order.
Bold, large text formatted to look like a heading but built as a plain paragraph — invisible to search engines and screen readers as a heading.
Heading structure isn't only an SEO issue — it's how a large number of real visitors navigate a site. People who use screen readers because of visual impairments often jump from heading to heading to scan a page, the same way a sighted visitor's eyes jump from headline to headline, letting someone skip straight to the section they need without listening to the whole page read aloud.
If your headings are missing, mislabeled, or out of order, that navigation breaks for those visitors the same way it breaks for search engines — for the same underlying reason: the code isn't telling the truth about the page's structure. Fixing heading structure is one of the more meaningful, low-cost accessibility improvements a small business site can make.
We start by pulling every heading on every important page into a single outline, so we can see the whole site's structure at a glance rather than page by page, then flag pages with multiple H1s, skipped levels, styled text pretending to be a heading, and sections that need to be split or combined.
Then we rewrite the outline so each page has one clear H1, a logical set of H2s covering its major sections, and H3s only where a section genuinely needs to be broken down further — the same structure we build into internal linking between your pages. We also make sure each heading works alongside the page's writing title tags and meta descriptions, since those elements together are what both Google and a visitor read first.
Straight answers to the questions we hear most about H1s, H2s, and H3s.
Heading structure is one piece of our on-page SEO service and our broader SEO and website optimization for New York businesses. For a fuller picture of common issues, see our website optimization checklist.
A clean heading outline across your site today doesn't guarantee a clean one next year. Every new page, every section rewritten, every template tweak is a fresh chance for headings to drift out of order or duplicate — nobody drafting a quick update is thinking about H2 hierarchy while they do it. One thorough pass fixes what exists right now; it doesn't keep the next fifty pages a site adds clean on its own. That's why heading structure is checked as part of an ongoing relationship, not a single cleanup. See our ongoing optimization packages.
We'll pull the heading structure from your key pages and show you exactly where it breaks down — free, no obligation, for New York businesses we work with.