Heading tags (H1 to H6) mark the title of a page and the titles of its sections. For SEO they help Google understand what the page covers and how it is organized; for readers and screen reader users they work as the page's table of contents. The rule that serves all three: one H1 that says what the page is, H2s for the main sections and H3s inside them. To see the heading outline of any page, paste its URL into our free heading checker.
This guide covers what headings actually do (and what they do not), how many H1 tags a page should have and what Google says about it, how the H1 differs from the title tag, two outline examples you can copy, and the mistakes we see most often on startup sites.
What heading tags are
HTML has six heading levels, <h1> to <h6>. The number is the level, not the font size: an H2 is a section of the page, an H3 is a subsection of that H2, and so on. Browsers style them larger by default, but you can make any heading look however you like with CSS.
<h1>Invoice Software for Freelancers</h1>
<h2>How it works</h2>
<h3>Create an invoice</h3>
<h3>Send automatic reminders</h3>
<h2>Pricing</h2>
The indentation above is only to show the structure; in real HTML, headings sit inside your normal markup. Most pages need three levels at most. H4 to H6 are for long documentation and legal pages.
What headings do for readers, assistive tech and Google
Readers skim headings first
Most people do not read a web page top to bottom. They scan the headings to find the part they came for. A heading that says "Pricing" or "How to cancel" lets them jump straight there; a heading that says "Our philosophy" does not. Clear headings also make long pages easier to finish, which is why our readability checker and heading checker are often used together.
Screen readers navigate by headings
Screen reader users can list all the headings on a page and jump between them, much as a sighted reader skims. WebAIM's long-running surveys of screen reader users have found that navigating by headings is the most common way they look for information on a long page. That only works if your headings are real heading elements, in a sensible order, with text that describes each section. Accessibility guidelines (WCAG) ask for exactly this: structure that is conveyed in the markup, and headings that describe their topic.
Google uses headings to understand the page
Google reads headings as strong hints about what each section of a page covers. They are not a ranking trick: a keyword in an H2 will not lift a weak page. But clear headings help Google match a section to a specific question, can feed the title link Google shows in results when your title tag is poor, and make it easier for Google and AI assistants to pull a passage that answers a query. Pages that win a featured snippet often have a heading that matches the question followed by a direct answer.
Google's own SEO Starter Guide says to break long content into sections with headings to help users navigate, says there is no ideal number of headings, and says heading order does not matter for Google Search even though semantic order is good for screen readers. In short: heading tags help SEO indirectly, by making the page clearer to both people and machines, not as a scoring factor you can game.
The H1 tag
The H1 tag is the main heading of the page: the headline a visitor sees first. It should say plainly what the page is about, in words the visitor would use.
- Homepage: what the product is and for whom. "Invoice software for freelancers", not "Welcome to Ledgerly".
- Product or feature page: the job the feature does. "Automatic payment reminders".
- Blog post: the title of the post, including the phrase people search.
- Tool page: the tool's name, often with "free" if it is.
There is no length limit for an H1, but long ones read badly. Most good H1s are under about 70 characters. Ledgerly, used in these examples, is an invented invoicing product.
H1 vs title tag
The H1 and the title tag are often confused because they usually say similar things. They are different elements with different jobs:
| Title tag | H1 tag | |
|---|---|---|
| Where it lives | In the head: <title> | In the body: <h1> |
| Where people see it | Search results, browser tab, bookmarks | On the page itself |
| Written for | Someone deciding whether to click | Someone who already clicked |
| Length | About 50 to 60 characters before Google cuts it | No limit; short is clearer |
| Brand name | Often added at the end | Usually left out |
| How many per page | Exactly one | One is clearest |
They should agree on the topic without having to match word for word. A title tag might be "Invoice Software for Freelancers, Free to Start | Ledgerly" while the H1 is "Invoice software that gets freelancers paid on time". If the two say very different things, Google is more likely to rewrite your title link using the heading. Our title tag guide covers title length and formulas in detail.
How many H1 tags should a page have?
One. Not because Google punishes more, but because one H1 is clearest for everyone.
Here is what is actually true:
- HTML allows several H1s. It is valid markup.
- Google says it copes. Google's John Mueller has said more than once that multiple H1s are fine for Google's systems, and the SEO Starter Guide says there is no magic number of headings.
- The old "outline algorithm" is gone. The idea that every
<section>could have its own H1, which would be demoted automatically, was never implemented by browsers or screen readers and was removed from the HTML specification in 2022. An H1 is an H1 wherever you put it. - People and tools expect one. A screen reader user who jumps to the H1 expects the page's title. Many SEO tools, including ours, flag several H1s because it usually means a template is marking up something (a logo, a sidebar title) as the main heading by mistake.
So the practical answer to "how many H1 tags" is one per page, describing the page. If you find several, check where they come from; it is almost always a theme or component, not a decision someone made.
Heading structure: H2 and H3 for SEO
Below the H1, headings form an outline. Good heading structure follows a few simple rules:
- H2s are the main sections. If someone read only your H2s, they should know what the page covers.
- H3s sit inside an H2 and break it into parts. Do not use an H3 for something that is not part of the H2 above it.
- Do not skip levels on the way down. Going from H2 straight to H4 does not break anything, but it usually means a heading was picked for its size, not its meaning. Going back up (from H3 to the next H2) is normal.
- Write headings as labels or questions people would search. "How much does it cost?" and "Pricing" both work; "The bottom line" tells nobody anything.
- Use your keywords where they describe the section, and nowhere else. One H2 with the main phrase is natural; eight is stuffing.
Outline example: SaaS landing page
H1 Invoice software that gets freelancers paid on time
H2 How Ledgerly works
H3 Create an invoice in a minute
H3 Reminders that send themselves
H3 Get paid by card or bank transfer
H2 Who uses Ledgerly
H2 Pricing
H2 Frequently asked questions
H3 Is there a free plan?
H3 Can I use my own logo?
H2 Start free for 30 days
Notice what is not a heading: the navigation, the logo, the testimonial quotes, the footer column titles. Those can be styled text or, for footer columns, a lower level that does not interrupt the main outline. Marketing pages often turn every bold line into an H2 because of the design system; that buries the real sections.
Outline example: blog post
H1 How to Get Paid Faster as a Freelancer
H2 Why invoices get paid late
H2 Seven ways to get paid faster
H3 1. Invoice the day the work is done
H3 2. Shorten your payment terms
H3 3. Send automatic reminders
H3 ...
H2 What to do when a client will not pay
H2 FAQ
H3 How long should payment terms be?
H3 Is it OK to charge a late fee?
This is the shape this guide uses, too. Numbered H3s for a list post make each item easy to find and easy for Google to quote. The FAQ section with each question as an H3 reads well and maps cleanly to FAQ markup.
Common heading mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| No H1 at all | The page has no stated topic for readers or tools | Add one H1 with the page's main subject |
| The logo is the H1 on every page | Every page has the same main heading | Make the logo an image or link; give each page its own H1 |
| Several H1s from a template | Confuses screen reader users and audits | Demote the extra ones to H2 or plain text |
| Headings chosen for size | The outline becomes meaningless | Pick the level by meaning, style it with CSS |
| Bold text instead of headings | Looks like a heading, but is not one to browsers, assistive tech or Google | Use a real h2 or h3 element |
| Empty headings | Screen readers announce a blank heading | Remove them or add text |
| Headings inside images | The text cannot be read by search engines or screen readers | Use live text, or at least good alt text |
| Keyword stuffed headings | Reads as spam and helps nothing | Write for the reader; use the phrase once where it fits |
| Headings only added by JavaScript | Crawlers that read the raw HTML see no structure | Render headings in the server HTML |
On the image point: if a hero banner has its headline baked into the picture, the page has effectively lost its H1. Use real text over the image instead, and see our alt text guide for describing the images you keep.
How to check your headings
With the heading checker
- Paste a page URL into the free heading checker.
- Read the outline: every heading, indented by level, in page order.
- Fix what it flags: a missing H1, more than one H1, empty headings and skipped levels.
The checker reads the HTML your server returns, the way many crawlers do. If your headings only appear after JavaScript runs, they will not show up, and that is worth knowing.
In the browser
Open developer tools and search the elements panel for h1, or run document.querySelectorAll('h1,h2,h3') in the console to list them. If you use a screen reader, open its headings list (the rotor in VoiceOver, for example) and try to find a section using only headings. It is a quick test of whether your structure makes sense.
Across the whole page
Headings are one part of on-page SEO. The on-page SEO checker audits headings together with the title, description, images, links, word count and schema, with a score and fixes. For the full per-page list, work through our on-page SEO checklist.
FAQ
Do heading tags help SEO?
Yes, indirectly. Headings help Google understand what each section of a page covers and help it match sections to specific questions. They also make pages easier to read and navigate, which helps people stay. A keyword in a heading will not rescue a weak page, though.
How many H1 tags should a page have?
One. HTML allows more and Google says it can handle them, but one H1 that states the page's topic is clearest for readers, screen reader users and SEO tools. Several H1s usually come from a template by mistake.
Should the H1 be the same as the title tag?
They should say the same thing without having to be identical. The title tag is written for the search result and often ends with your brand; the H1 is the on-page headline and usually leaves the brand out.
Can I skip heading levels, like H2 to H4?
It will not break anything for Google, which says heading order does not matter for Search. It does make the outline harder to follow for screen reader users, and it usually means a level was chosen for its size. Pick levels by meaning and style them with CSS.
Is bold text the same as a heading?
No. Only h1 to h6 elements are headings to browsers, assistive technology and search engines. Bold paragraph text may look like a heading, but it does not create structure.
Topics
Written by
Devvrat Hans
Founder
By subscribing, you agree to get our newsletter by email. Unsubscribe any time in one click. See our Privacy policy and Terms.
Related Articles
301 Redirect Generator Guide: 301 vs 302, and Redirect Code for Apache, Nginx, Next.js and Cloudflare
How to use a 301 redirect generator, and when a 301 is the right redirect at all: 301 vs 302 vs 307 vs 308, copy and paste code for .htaccess, Nginx, Next.js and Cloudflare, and how to avoid chains and loops in a migration.
Bulk Domain Authority Checker: How to Compare Many Domains at Once (Free)
When to check domain authority in bulk, how to compare up to 20 domains at once for free, how to read and sort the results, and a link prospecting workflow with spreadsheet formulas.
Canonical Checker Guide: What a Canonical Tag Does and How to Check Yours
How to use a canonical checker, and what it is checking for: what rel canonical means, HTML and HTTP header examples, when to use a canonical tag, the mistakes that drop pages from Google and how to read Search Console's canonical reports.