Heading Tags for SEO: H1 to H6 Rules for 2026

Administrator in Search Engine Optimization Oct 02 / 2 weeks ago

Google's SEO Starter Guide puts it bluntly: "Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn't matter if you're using them out of order." MDN Web Docs, the reference Mozilla runs for web developers, points the other way, telling authors "Do not skip heading levels" and adding that a page should generally have a single H1. So which rulebook is right?

Both are right because they protect different readers: Google's line covers its own crawler, while MDN's rules protect a person using a screen reader who jumps from heading to heading. Write heading tags for people first, because people are the audience these rules really protect, while Google reads headings for a narrower job than most SEO checklists suggest.

If you write, edit or template web pages, here is what heading tags are, what each rulebook says, and how to audit a page.

What are heading tags, and what do H1 to H6 mean?

Heading tags are the HTML elements H1 to H6, which MDN Web Docs describes as six levels of section headings. H1 is the highest section level, and H6 is the lowest. Browsers and screen readers can use these levels to build a table of contents or a list of every heading on the page.

MDN's reference page for heading elements uses a page about beetles as its example. The H1 is Beetles, H2 sections cover topics like Etymology and Evolution, and an H3 called Head holds an H4 called Mouthparts. I think of headings as the outline of the page, not as font sizes, so read alone they should tell a stranger what the page covers.

What does Google Search say about heading order?

Google says heading order does not matter to Google Search, and its SEO Starter Guide lists "Number and order of headings" under things it believes you should not focus on. It says semantic order is great for screen readers and that there is no ideal number of headings, yet it still tells site owners to use headings to help users navigate.

The passage sits under "Things we believe you shouldn't focus on" in Google Search Central's SEO Starter Guide. Its reason is blunt: "The web in general is not valid HTML, so Google Search can rarely depend on semantic meanings hidden in the HTML specification." Put simply, so many sites break the rules that Google can rarely lean on them. The same list says there is "no magical word count target," and our guide explains why word count is not a ranking factor either.

Where does Google actually use your headings?

Google uses headings to help pick the title link, the clickable headline of a search result, and its title link page lists nine sources, with heading elements such as H1 elements among them. If a page has several large headings that look equally important, Google may use the first one, so "Google ignores headings" is wrong too.

The same page flags a common issue called "No clear main title," when two or more headings look the same. Our post on why Google rewrites title tags covers that trigger, and one of Google's own suggestions is to put the title text in the first visible H1 on the page. Changes show up only after a recrawl, "which may take a few days to a few weeks," Google says.

The list also includes og:title, which social previews use, as our guide to Open Graph tags explains. For site names, Google also considers heading elements on a home page, but it says "WebSite structured data is most important, if you want to specify a preference," as our guide to Google site names and favicons shows.

Should a page have one H1 or several?

MDN Web Docs notes that the HTML standard allows more than one H1, but says a page should generally have a single one. Google says there is no ideal number of headings. My advice is one H1 per page that matches its topic, because it also gives Google one clear main title to pick.

That one H1 rule is good practice for readers, even though Google does not require it, so do not panic if a template adds a second one. For example, a Denver, Colorado, HVAC company might find that its theme wraps the logo text in an H1 on every page, so confirm the first H1 holds the real title.

Every cell comes from the publisher's own documentation, saved on October 2, 2026.

Is it ever fine to skip a heading level?

MDN Web Docs says do not skip heading levels. The W3C tutorial agrees that an H2 should not be followed directly by an H4, but says it is fine to skip ranks when closing a subsection. Google Search does not care about order either way, but I would still follow MDN and W3C, because it costs nothing.

Closing a subsection is easy to picture, since a section can go H2, H3, then H4 before a new H2 starts the next topic, and that jump back up is normal. Skipping down is the real problem, because MDN warns that a listener "may be left wondering where the missing heading is."

Why should you not use headings to resize text?

MDN Web Docs says plainly, "Do not use heading elements to resize text," and size belongs in CSS instead, because a level chosen for its look breaks the outline. The reverse also hurts, since big bold text that is not tagged as a heading looks like a title but never shows up in a screen reader's list of headings.

For example, an accounting firm in Dublin, Ireland, might tag a small footer note as an H4 only because the H4 style looks small. Make it a paragraph styled with CSS instead, and see our guide on how Wix separates text styles from heading tags for the opposite case.

Why do screen reader users depend on heading tags?

WebAIM's 2024 screen reader survey asked what people do first to find information on a long page, and "Navigate through the headings on the page" was the top answer at 71.6%. For many readers who cannot see the page, headings are the table of contents, which is why I think this is the strongest reason to care.

WebAIM's Screen Reader User Survey had 1,539 valid responses, gathered in December 2023 and January 2024. WebAIM found that people with advanced screen reader skills were much more likely to use headings (78%) than beginners (47%). Heading levels earn their keep too, since 88.8% of WebAIM's respondents found them very or somewhat useful, and "Missing or improper headings" ranked eighth of twelve on the survey's list of the most problematic items.

What does WCAG ask of headings?

WCAG 2.2 Success Criterion 2.4.6, Headings and Labels, sits at Level AA, and its rule is short: "Headings and labels describe topic or purpose." It does not require headings at all, only that the headings you do use are descriptive, while correct markup is a separate test, Success Criterion 1.3.1 at Level A.

The W3C's Understanding page notes that a page can pass 2.4.6 but fail 1.3.1 if its headings are not marked up, and the reverse can happen too. The W3C lists 2.4.10 Section Headings at Level AAA, and it adds that descriptive headings especially help people whose disabilities make reading slow and people with limited short term memory. Our guide to web accessibility and SEO covers which laws point to Level AA.

How do you write heading text that people can use?

Describe the section in the words your readers use, and keep it short, since the W3C says "A word, or even a single character, may suffice" if it helps people find their way. Skip vague labels such as More info, and never stuff keywords, which Google's SEO Starter Guide says is against its spam policies.

Google adds that its "language matching systems are sophisticated," so you do not need every variant of a phrase in your headings. Start from keyword research that finds the words searchers really use, and match each heading to the search intent behind the query. I like question headings on guides, but that is taste, not a rule, and our post on how featured snippets and People Also Ask work goes deeper. Link text follows the same rule, as our internal linking guide explains.

Which language should headings use on a multilingual site?

Write each heading in the same language as the page it sits on, a rule Google's title link page gives for the title element, warning that a mismatch may lead Google to pick other text. Extending it to headings is my own advice, but it carries little risk and it helps every reader.

For example, a seafood exporter in Busan, South Korea, might run Korean and English versions of its product pages, so the Korean page needs a Korean H1 and the English page needs an English one. Our guide to hreflang and international SEO shows how to connect those versions, and for Korean search itself, see our guide to Naver SEO and ranking in Korean search.

What did the HTML standard change about H1 styling?

MDN Web Docs says that "Before May 2025," the HTML standard told browsers to shrink an H1 placed inside a section, article, aside or nav element, so it rendered like an H2. MDN says this special default style "has now been removed," and that nesting several H1 elements inside these sections no longer conforms to the HTML standard.

My reading: if older pages relied on that default shrinking, those headings may now look oversized, so check them.

How do you audit heading tags on a page, and what should you fix first?

List the headings in order, then check four things. You want one clear main heading that matches the title, no skipped level on the way down, a heading that describes each section, and no heading used only for styling. Fix a missing or vague main heading first, since that one also feeds the title link.

1. Use the browser's developer tools or a screen reader's headings list to see every heading in order.
2. Confirm the first H1 holds the real page title.
3. Flag any jump down, such as an H2 followed directly by an H4.
4. Spot big text that is not a heading, and headings used only for looks.

Add these checks to our on page SEO checklist, and take template problems into a technical SEO audit your developers will ship. If a script adds headings after load, my reading is that Google sees them only after rendering, a step our guide to how Google renders JavaScript explains. Keep your heading tags honest about what each section holds, and recheck after every template change.

Frequently asked questions about headings

Are heading tags a Google ranking factor?

None of the Google sources in this guide call heading tags a ranking factor, and Google's SEO Starter Guide says heading order does not matter for Google Search. Google does read headings when it builds title links and site names, so they can shape how your result looks. My advice is to treat headings as a reader feature first, not a ranking lever. Clear sections help people find what they came for, and that alone is reason enough to get them right.

What is the difference between the title element and the H1?

The title element sits in the page code, and it is the first source Google lists for title links. Google's SEO Starter Guide says the title text can also be used for the title shown in browsers and bookmarks, while the H1 is the main heading readers see on the page itself. MDN Web Docs says a single H1 should describe the content of the page, much like the title element. My advice is to keep the two close in meaning, even if the wording differs.

Is it a problem if a page has no H1 at all?

The Google pages cited here never call a missing H1 a problem, and Google's title link page lists nine sources, with heading elements just one of them. Readers are a different story, because MDN Web Docs says a page should generally have a single H1 that describes its content. Screen reader users often jump through headings first, so a long page without them is hard to use. My advice is to give every real page one clear H1 that names its main topic.

How many H2 headings should a page have?

There is no fixed number, since Google's SEO Starter Guide says there is "no magical, ideal amount of headings" and adds that if you think it is too much, it probably is. I think one H2 per main question or task is a sensible start, so a short post might need only a few while a long guide needs more. If two H2 sections say the same thing, merge them, and if one section runs very long, split it with H3s so readers can skim.

Can navigation headings come before the H1?

Yes, and the W3C Web Accessibility Initiative tutorial shows two valid patterns. In the first, the main heading leads, and every other heading, including the navigation menu, sits one rank lower. In the second, the main heading comes after the navigation, and it is the content heading, not the site name. Only the second pattern gives the H1 to the page topic, so my advice is to pick that one for your theme and use it on every page so readers always know where to look.

Do headings in sidebars and footers count?

If they are marked up as headings, screen readers list them like any other heading. The W3C tutorial says heading ranks in fixed sections, such as sidebars, should not change with the ranks in the content area, because there consistency across pages is more important. For Google, its title link page warns that several equally prominent headings can blur which text is the main title. My advice is to keep them small and plain so the H1 stands out on every page.

How long should a heading be?

Short enough to scan, long enough to be clear. The W3C's page on Success Criterion 2.4.6 says headings do not need to be lengthy, as long as they give a clear cue for finding and navigating content. The Google pages cited here set no length rule for headings, and I think most section headings work best as a plain phrase or a short question that a reader could say out loud. If a heading needs a comma, it may be two sections.

How soon does Google notice a heading change?

Not right away. Google's title link page says Google has to recrawl and reprocess a page to notice updates to its sources, which may take a few days to a few weeks. Heading elements are one of those sources, so a new H1 is unlikely to change a title link the same day. My advice is to make the change, note the date and wait a few weeks before judging it, while screen reader users get the fix on their next visit.

Do headings help AI tools quote a page?

None of the sources behind this guide say how AI answer tools use headings, so treat what follows as opinion. I think clean sections with a clear heading and a direct first sentence are easier for any reader or program to quote. A heading that names the question, followed by a short answer, gives a skimmer and a machine the same shortcut. Still, write for the person scanning the heading list, because that reader is real and you can actually help them.

Should you rewrite old posts just to fix heading order?

Not for rankings alone, because Google's SEO Starter Guide says heading order does not matter for Google Search, so do not expect a jump from reordering heading tags. Do it for readers instead, starting with the pages people visit most. Fix a missing or vague H1 first, then skipped levels, then fake headings made of bold text. Batch the work by template where you can, because one theme fix can clean up every page that uses it, then recheck a sample of pages.