My approximate guideline for writing a long blog article, which ranges from about 1,500-2,500 words, is to have between 6-10 H2 titles as your primary title along with 1-3 H3 titles underneath each H2 to provide a more detailed summary when required. This system works effectively since H2 headings define tight subtopics that can easily be found when searching Google, or simply scanning to locate what you're looking to read. If a subtopic can't be clearly summed up in one sentence, chances are you should not have an individual H2. H3 subheadings are used for organizing complex sections of your articles but are not used just to fill up space on the page (for example, webpages with 20 plus H2 and/or H3 headings stacked on top of one another as a matter of visual spacing usually rank poorly because the structure looks disjointed, and therefore, makes it difficult for the user to find relevant content to get what they are looking for). When looking through audit reports of the Long-Form content, the best performing long content matches what I call the "Clean Outline" method. You will have fewer sections, but they are all strong and logically nested, making it easier for you or your reader to scan through all of this long content. If you produce a set of H2 and H3 headings that resemble the Table of Contents of a Book, you will most likely have your heading ranges in check.
To be honest, I don't think there's a fixed rule of thumb for the "ideal" number of H2 and H3 tags. It really depends on how complex the topic is and how much you need to break things down for the reader. Many people believe in adding headings every few paragraphs, and I agree with the idea behind it, not for SEO first, but for readability. If a section starts to feel long or covers more than one idea, that's usually my cue to add another H2 or H3. My personal rule is: If someone is just skimming the article, they should still be able to understand the main points just by reading the headings. If the headings already tell a clear story, then the structure is probably doing its job. So instead of counting headings, try to focus more on making sure each section has a clear purpose and the content feels easy to scan and digest for both readers and search engines.
A simple rule of thumb is one H2 for every major idea and H3s only when a section needs clear sub-breakdowns. For a long-form blog (1,500-2,000 words), this usually means 5-7 H2s with 1-3 H3s under each, if needed. The goal isn't hitting a number, it's maintaining logical flow and scannability so both readers and search engines can easily understand the content structure.
When it comes to long form blogs, I focus on using between 2-4 H2 tags as per content's complexity other than a strict limit. The H2 tags work highlighter for major sections, on the other hand H3 tags are quite handy to delve into sub points under each H2. With this hierarchy we ensure clarity and enhance the reader's journey through the material. For posts over 1500 words, I usually consider adding H3 tags as they help in structuring. Make sure that there should be a single H1 tag on your post. Here the goal is not about meeting quotas, but it's about providing an easily navigable, engaging layout which keeps readers engaged. The clear organisation works as both user experience and SEO.
I don’t aim for a specific number of H2s or H3s. I focus on making the content easy to understand first. Each H2 should introduce a clear idea, not just fill space. In practice, I often structure H2s around real questions readers ask, such as who, what, why, and how, because that improves clarity for both people and AI systems. In most long-form articles, that naturally results in around 6 to 12 H2s, with H3s used only when a section genuinely needs extra detail. If a heading does not make the page easier to read or scan, it does not belong there. Good structure supports understanding, not a checklist.
My rule of thumb is to use as many H2s as you have distinct questions to answer, usually one H2 per core subtopic, then add H3s only when a section genuinely needs clear steps, options, or examples to stay scannable. I avoid forcing a number because structure should follow intent, not a template, and over-heading makes content feel padded. If a reader cannot find their answer in ten seconds, you need better headings, not more of them.
I use the "scroll test"--if I scroll through the post and see a header roughly every two full scrolls, I'm in the sweet spot. That usually breaks down to one H2 every 300-500 words for long-form content, and H3s only when an H2 section legitimately splits into multiple ideas that deserve their own callouts. The mistake most people make is stuffing headers everywhere because some SEO checklist told them to. But over-headered content reads like a PowerPoint deck, not a blog post. Readers tune out. At Gotham, we write long-form content about booking speakers and event strategy. Our rule: use headers to answer the questions readers are actually asking as they scroll, not to game algorithms. When we do that, engagement goes up and people actually finish reading. Headers are navigation, not decoration.
I aim for one H2 every 300 to 400 words and only add H3s when a section truly needs sub structure. Google tends to reward pages that are easy to scan and logically segmented rather than over segmented. For example, in long guides that exceed 2000 words, this usually results in six to eight strong H2s with two or three H3s under the most complex sections. When teams force an H3 under every H2, rankings often stall because the hierarchy stops reflecting how a human would actually read the page.
One simple rule of thumb I follow is one H2 for every 200-300 words, with 1-3 supporting H3s under each H2 when needed. This keeps long-form blogs well-structured without overloading the page with headings. H2s break the article into clear sections, while H3s add depth and clarity where a topic needs further explanation. The result is content that's easy to scan, easy to understand, and more engaging for readers, especially in longer posts.
One rule of thumb I use for a long form blog is to have one clear H2 for every main idea, and only add H3s when they genuinely help break that idea down. In practical terms, that usually means around one H2 for every 300 to 400 words, with zero to three H3s under each H2. From my experience, too many H2s make an article feel choppy and exhausting to scan. It starts to read like a checklist instead of a thoughtful piece. Too few H2s do the opposite. The content feels dense, intimidating, and hard to navigate, even if the writing itself is solid. That spacing sweet spot keeps the reader oriented without overwhelming them. For H3s, my rule is even stricter. I only use them when a section clearly contains multiple sub ideas that would benefit from quick scanning. If an H3 is just restating the H2 in different words, I remove it. Every H3 should answer a specific question or introduce a distinct angle, not just exist for structure's sake. I also think about reader behavior more than word count. I imagine someone skimming on a phone. If the headings alone tell a coherent story, I know the structure is working. If the headings feel repetitive or vague when read in isolation, I revise. So the rule is not about hitting a number. It is about pacing. H2s set the rhythm of the article, and H3s should only appear when they genuinely improve clarity and flow.