How to Write H1 Tags for SEO
The H1 tag is the main heading of a web page. It tells both users and search engines what the page is about. Getting your H1 right is one of the most important on-page SEO tasks — it is worth up to 12 points in the RankNibbler scoring system.
H1 Tag Best Practices
| Rule | Why |
|---|---|
| Exactly one H1 per page | Multiple H1s confuse search engines about the main topic |
| Include primary keyword | Signals relevance for your target search query |
| Different from the title tag | H1 can be longer and more descriptive than the title |
| Descriptive and specific | "15 SEO Tips for Small Businesses" beats "SEO Tips" |
| Front-load the keyword | Words at the start carry more weight |
| Keep it under 70 characters | Long H1s lose impact and can look messy |
H1 vs Title Tag
The title tag appears in search results and browser tabs. The H1 appears on the page itself. They should be related but do not need to be identical. The H1 can be more detailed since it is not constrained by pixel width limits.
Common H1 Mistakes
- No H1 at all — some themes or templates miss it entirely
- Multiple H1 tags — often caused by logos or widgets wrapped in H1
- H1 is just the brand name — the H1 should describe the page content, not just your brand
- Using H1 for styling — use CSS for font size, not heading tags
- H1 hidden with CSS — search engines may see this as deceptive
Check your H1 tags with the heading structure checker.
Last updated: March 2026
The H1 Rules That Actually Matter
Rule 1: One H1 Per Page
Modern HTML5 technically allows multiple H1s (one per section element). In practice, Google and SEO tooling treat pages as having a single primary H1. Stick to one. Multiple H1s dilute the topic signal and confuse screen readers.
Rule 2: Match Title Intent
Your H1 and title tag should cover the same topic from different angles. Title targets the SERP click; H1 confirms to the visitor they're in the right place. They don't need to be identical, but they must be consistent.
Example:
- Title: "Free HTML Minifier — Minify & Compress HTML Online (No Signup)"
- H1: "Free HTML Minifier — Compress HTML Code Instantly"
Rule 3: Include the Primary Keyword
H1 is a strong topical signal. Include the primary keyword naturally — not forced. "SEO Tips for 2026" beats "The Complete Professional Guide to Search Engine Optimization Best Practices in 2026" on clarity and keyword focus both.
Rule 4: Keep It Under 70 Characters
Long H1s look cluttered on mobile and dilute focus. Aim for 40–60 characters. Longer H1s can still work, but test mobile rendering.
Rule 5: Make It Descriptive, Not Clickbait
The H1 is seen AFTER the click. Clickbait H1s that don't match the actual content create high bounce rates, which feed negative user signals to Google. Promise what you deliver.
Rule 6: Avoid Keyword Stuffing
"SEO Tools | Free SEO Tools | Best SEO Tools 2026" stuffs the keyword three times. Natural usage always wins. Google's algorithms penalise obvious stuffing.
H1 Formulas That Work
For Tool Pages
- "[Tool Name]: [Action] on [Scope] (Free)"
- "Free [Tool Name]: [Specific Outcome]"
- "[Tool Name] — [Unique Differentiator]"
Example: "Readability Checker: Flesch Score, Grade Level & SEO Analysis"
For Guide / How-To Content
- "How to [Achieve Outcome] in [Year/Timeframe]"
- "How to [Action] (With Examples)"
- "The Complete Guide to [Topic] for [Audience]"
Example: "How to Write SEO Content That Ranks in 2026"
For Blog Posts
- "[Number] [Adjective] [Topic] You Should [Action]"
- "[Topic]: What It Is, Why It Matters, How to [Action]"
- "[Question]? [Specific Answer]"
Example: "12 Schema Types That Actually Unlock Google Rich Results"
For Product / Service Pages
- "[Product Name]: [Core Benefit]"
- "[Service] in [Location] — [Unique Selling Point]"
Example: "Cosmetic Dentist in Birmingham — Private Smile Design"
For Comparison Pages
- "[Product A] vs [Product B]: [Year] Comparison"
- "[Alternatives] Compared: [Differentiator]"
Example: "RankNibbler vs Screaming Frog: 2026 Free Tool Comparison"
Common H1 Mistakes
The "Welcome to Our Website" H1
Zero keyword value, zero user value. Tells Google nothing about what the page is. Instant loss of a critical SEO signal.
Multiple H1s From Theme or CMS Defaults
Some themes wrap both site title and page title in H1 tags. Inspect the HTML — if you see two H1s rendered, fix the template to demote the site title to a <span> or similar non-heading element.
H1 Hidden via CSS
Developers sometimes hide the H1 visually with display:none or off-screen positioning. Google's rendering system generally still reads hidden H1s, but the user experience is inconsistent. Show the H1.
Image-Only H1
Using an image as the H1 without accompanying text means the alt text becomes the heading. If alt text is missing or weak, you've effectively lost the H1 entirely. Use text, or ensure alt text is rich and keyword-appropriate.
H1 Using the Wrong Case
TITLE CASE or lowercase are both fine in moderation. ALL CAPS looks like shouting to readers and older screen reader implementations read them letter-by-letter. Use sentence case or title case.
Duplicate H1 Across Every Page
Many CMSs default to using the site name as H1 on every page. That's useless — every page has the same primary topic signal. Fix the template to use page-specific H1s.
H1 and Heading Hierarchy
H1 is the top of a hierarchy that includes H2, H3, H4, H5, H6. The rules for the broader hierarchy:
- H1 is the page title; one per page.
- H2 marks major sections.
- H3 marks subsections within H2 content.
- H4–H6 rarely needed; avoid unless content genuinely has 4+ levels of depth.
- Never skip levels (don't go H2 → H4 directly).
- Order heading levels sequentially in the DOM.
Use the heading extractor to audit your hierarchy.
How to Fix H1 Problems
- Run the heading structure checker to identify issues.
- Count H1 tags on each page. Zero H1s or multiple H1s both break.
- Check template vs content H1s. CMS templates often add H1s you didn't intend.
- Rewrite weak H1s. Prioritise homepage, service pages, and top traffic pages.
- Align H1 with title tag. Consistent messaging across both.
- Verify mobile rendering. Long H1s break mobile layouts.
- Re-audit. Confirm fixes are live.