Tonight, my friend Henrik Blicher Hansen brought up the HTML <hgroup> Tag during our Treasure Map Google Meet, and it sparked a debate. Many people still aren’t sure what this tag does or whether it matters anymore. The conversation got me thinking about what <hgroup> was supposed to do, why it flopped, and what it means for SEO today.
TL;DR:
<hgroup>is an old HTML5 idea for grouping a heading and a subtitle.- It works in browsers but does nothing special.
- The W3C removed it from its spec, but the WHATWG standard still includes it.
- It has no SEO benefit and no accessibility gain.
- Use
<header>and a<p>for subtitles instead.
What hgroup was supposed to do
The people who made HTML5 thought, “People love putting a subtitle under a main title. Why not make a tag for that?” That’s where <hgroup> came from. The idea: you have a main heading, like <h1>, then a subtitle or tagline under it, all wrapped in an <hgroup>. It works like a movie poster:
<hgroup>
<h1>Dr. Strangelove</h1>
<h2>Or: How I Learned to Stop Worrying and Love the Bomb</h2>
</hgroup>
The second line, the subtitle, goes with the title and does not start a new section. <hgroup> told your browser that the two lines form one big heading.
Don’t expect <hgroup> to throw sparkles on your page or make your SEO skyrocket. It does nothing visually. It’s a quiet container that groups content, like a <div> with better manners.
How hgroup was supposed to work
When HTML5 was still finding its feet, <hgroup> sounded like a great idea. The plan: the browser counts only the first heading inside it as the main title, and everything else acts as support text. With an auto-generated table of contents, the subtitle wouldn’t get its own bullet point.
That sounds tidy.
The web world didn’t agree on what to do with it. The W3C, the group that writes the rulebook, officially dropped <hgroup> from the spec in 2013. It was too confusing for too little payoff, like a diet that lets you eat only soup and sadness.
The WHATWG, the other group that runs the “living” HTML standard, kept it but changed the rules. Now <hgroup> must contain one real heading (<h1> to <h6>) and can include extra content, such as a paragraph for a tagline.
Depending on who you ask, <hgroup> is dead, undead, or a ghost that refuses to move on.
Browser support for hgroup
No. Modern browsers, including Chrome, Firefox, Safari, and Edge, all recognize <hgroup>. They don’t care about it and treat it as a regular block-level container.
If you still use Internet Explorer 8, you have bigger problems than HTML semantics. That browser doesn’t know <hgroup> from a ham sandwich.
Your site won’t explode if you use <hgroup>, but it won’t win any awards for innovation either.
The SEO angle
<hgroup> does not help with SEO, but the reasons are worth a look.
In theory, grouping your title and subtitle helps search engines see them as one unit. If your main title says “Best BBQ Joints in Texas” and your subtitle says “Where to Get Ribs That’ll Change Your Life,” you might expect Google to read the combination and conclude, “This person knows barbecue.”
Search engines don’t read <hgroup> that way. Google doesn’t care about the tag itself and reads the words. Whether your subtitle sits in <hgroup>, <div>, or scribbled on a napkin, the text matters more than the wrapping paper.
<hgroup> adds no SEO value, positive or negative. Its effect is neutral.
Accessibility and machine-readability
Screen readers, the tools that help users who are blind or have low vision navigate sites, don’t treat <hgroup> in any special way. It might confuse them because the hierarchy of headings becomes fuzzy.
If you care about accessibility, use a <header> element and a plain <p> for your tagline, as in the following example:
<header>
<h1>My Company</h1>
<p>Established 1893</p>
</header>
The result is clean and readable for everybody, including Google and your users.
Example for when you must use hgroup
If you want to use <hgroup>, use this structure:
<hgroup>
<h1>My Company</h1>
<p>Established 1893</p>
</hgroup>
That structure is valid under the WHATWG rules. Using it is like bringing a pager to a smartphone party. It technically works, but people might give you funny looks.
Implications for semantic SEO and content hierarchy
For SEO and semantic content structure, <hgroup> represents an interesting idea. In theory, grouping a title and subtitle gives search engines a clearer view of your content hierarchy. The following point shows how it relates to SEO.
Content hierarchy: Using <hgroup> ties a tagline or subheading to the main heading, showing that the two belong together. In a perfect world, that helps search engines see that your subtitle isn’t starting a new topic. Even without <hgroup>, logical headings and smart keyword placement go a long way. To see where keywords matter most in headings, read SEO Keyword Placement: The 4 Critical Spots That Actually Matter.
Entity relevance
From an SEO perspective, subtitles often add keywords or context for your main heading. Grouping them can signal that the two are semantically connected, like one big descriptive phrase. Most search engines don’t treat <hgroup> specially. They care about the content and context.
To see how this kind of structure fits modern SEO thinking, where Google connects concepts instead of counting words, read Step-by-Step: How To Implement Entity SEO. It walks through how entities and relationships shape how search engines understand your page.
Final thoughts
The <hgroup> tag was a noble idea that didn’t stick. It tried to make the web’s structure more semantic, but the world moved on. The idea behind it, organizing your headings and subtitles logically, remains valuable.
I wrote another piece on how semantic markup ties into structured data and schema, the technology that helps Google really understand your content, and how meaning and markup work together to give your content extra clarity under the hood: Semantic Triples and Schema for Local Service Pages.
The result is simple and clean, and your HTML won’t look like it came from 2012.