Heading analyzer.

What is a heading analyzer?

A heading analyzer audits the H1 to H6 structure of any web page and flags the structural problems that weaken SEO. Paste your page HTML above and the heading analyzer draws the full heading outline, then warns you about multiple H1 tags, skipped heading levels, and empty headings that confuse both search engines and screen readers.

Why heading structure matters for SEO

Headings are the table of contents of your page. Google's crawlers read the H1 to confirm the page topic, then follow the H2s and H3s to map how the content organizes itself. A clean hierarchy tells the algorithm exactly which sections cover which subtopics, which helps it match the page to specific queries and even pull sitelinks for branded searches. A chaotic hierarchy, three H1s here, an H4 appearing before any H2 there, forces Google to guess at the structure instead of reading it.

The accessibility angle matters just as much. Screen reader users navigate pages by jumping between headings, and a broken hierarchy turns that navigation into a maze. Google has woven accessibility signals into its quality evaluations, so the heading structure that serves blind users also serves your rankings. Our heading analyzer checks both dimensions at once: the SEO logic of one H1 with ordered subsections, and the accessibility logic of no gaps or empties.

The one H1 rule, explained

HTML5 technically allows multiple H1 tags, and Google has said it can handle them. Handle is not the same as prefer. A single H1 gives the page one unambiguous topic statement, which strengthens the relevance signal for your primary keyword. Multiple H1s dilute that signal and usually indicate a template problem, like the site logo or the blog title accidentally marked as H1 on every page. Run any page through the analyzer above. If it reports two or more H1s, demote the extras to H2 and watch the outline snap into focus.

How to use this heading analyzer

Get your page HTML by right clicking the page in your browser and choosing View page source, then copy the markup. For a focused check, use Inspect Element on the main content area and copy the outer HTML of the article container. Paste it into the analyzer and the tool instantly renders the heading outline with each level indented and color coded.

Read the outline like a table of contents. It should tell the story of the page in ten seconds. If you cannot follow the argument from the headings alone, neither can a search engine. Fix issues top down: establish the single H1 first, then repair skipped levels, then fill or remove empty headings. After restructuring, confirm your title tag still mirrors the H1 using our SERP preview tool, since title and H1 work as a pair.

Common heading mistakes and how to fix them

Skipped levels top the list. An H2 followed directly by an H4 happens when writers pick headings by visual size instead of logical depth, or when a CMS theme styles H3 to look bigger than H2. The fix is structural: make it an H3 and adjust the styling separately. Never choose a heading level for its looks. Choose it for its place in the outline, then style each level with CSS.

Empty headings come next, usually from page builders that render heading blocks with no text, or from JavaScript widgets that inject headings before their content loads. They are invisible to sighted users and baffling to screen readers. The analyzer flags every one. Either add the missing text or delete the tag. Keyword stuffed headings form the third classic: "SaaS SEO | Best SaaS SEO | SaaS SEO Agency" as an H2. Write headings for humans, include the keyword where it fits naturally, and move on.

Headings versus styled text

A frequent audit finding is the fake heading: bold large text in a paragraph or div that looks like a heading but carries no heading tag. Search engines and screen readers both miss it entirely. If text functions as a section title, mark it as one. Our analyzer only detects real H1 to H6 tags, which is precisely the point. If your visual headings do not appear in the outline, they are not headings to anyone but sighted readers.

Heading strategy for long form content

For articles over 1,500 words, plan the heading outline before writing a single paragraph. The H1 states the topic and carries the primary keyword. Each H2 covers one major subtopic and targets a secondary keyword where natural. H3s break complex H2 sections into digestible parts. This outline first approach produces better content and better SEO simultaneously, because a logical structure is easier to write and easier to rank.

Aim for an H2 every 200 to 300 words to keep long pages scannable. Readers decide within seconds whether a page deserves their time, and the heading outline is what they scan. Pages with descriptive, keyword aware headings earn longer dwell times, and dwell time feeds the engagement signals that support rankings. After drafting, paste the HTML into the analyzer and confirm the outline matches your plan. For keyword distribution across those headings, our keyword density checker completes the QA pass.

Headings and featured snippets

Clean heading structure directly feeds featured snippet wins. Google pulls list snippets and table snippets from well organized content, and the H2 or H3 immediately above the list often becomes the snippet's framing. Pages with a clear "How to X" H2 followed by a numbered list win these snippets far more often than pages where the steps hide inside paragraphs. Structure your how to content with the question as the heading and the answer directly beneath it.

The same principle applies to AI answers. Large language models extract concise, well bounded sections when citing sources, and heading tags define those boundaries. Content under a clear H2 like "What is a heading analyzer" is far easier for an AI system to quote accurately than the same information buried in an unmarked paragraph. Google's featured snippet documentation confirms that it cannot show snippets for every query type, but well structured pages qualify wherever snippets exist.

Heading hierarchy best practices: H1 to H6 done right

The best heading hierarchy is simple. One H1 states the page topic. H2 tags mark the major sections. H3 tags break those sections into parts. Deeper levels suit complex documents, not everyday pages.

Give each level a clear job. The H1 carries the primary keyword near the front and reads like a promise of what the page delivers. Each H2 should stand alone as a section title, which makes H2 tags the natural home for secondary keywords and question phrases.

The nesting rules that prevent most errors

Never skip a level going down. An H2 can hold H3 tags, but an H2 must never jump straight to H4. Keep headings under about 70 characters and front load the important words. Google's SEO starter guide recommends heading tags for organizing content hierarchy. Verify keyword balance with our keyword density checker and pair the H1 with your title tag in the SERP preview tool.

Headings and accessibility: the WCAG rules you must follow

Accessibility standards treat heading structure as essential, not optional. WCAG success criterion 1.3.1 requires programmatic structure to match visual structure, and criterion 2.4.6 requires headings that describe their topic or purpose. In plain terms: no skipped levels, no empty headings, and no text styled to look like a heading without the tag.

Screen reader users navigate by headings. In NVDA and JAWS the H key jumps between headings. Skipped levels force these users to guess where sections begin, and empty headings announce themselves as dead ends. WebAIM's 2024 analysis of the top one million home pages found detectable accessibility failures on 95.9 percent of them. Run the analyzer above and fix what it flags. If the audit surfaces template level problems, our technical SEO services handle the repair, and you can talk to us about a full site review.

Watch for headings hiding in template chrome. Menus, footers and sidebars often inject H2 or H3 tags around widget titles, which pollutes the outline of every page. Reserve real heading levels for main content and paste a complete page into the analyzer to catch these. W3C's guidance on headings and labels documents what compliant structure looks like.

Headings on B2B SaaS pages: patterns that work

SaaS marketing pages follow predictable heading patterns because buyers evaluate predictably. The H1 names the category and the outcome: "B2B SaaS SEO That Reports to Pipeline". H2s cover the evaluation criteria: services, process, proof, pricing, FAQs. H3s detail each criterion. This pattern works because it mirrors the buyer's mental checklist. Deviate from it and visitors work harder to evaluate you, which is the opposite of what a conversion page should do.

One SaaS specific trap is the H1 that names only the product. "Welcome to Acme" or just the logo as H1 wastes the strongest on page signal on a word nobody searches. Your H1 should contain the category keyword a buyer would type. Save the brand for the title tag suffix. When our team rebuilds SaaS sites, the H1 rewrite is a day one change, and our website and SEO services treat heading architecture as foundational, not cosmetic.

Auditing headings at site scale

One page is a spot check. Real heading problems hide across hundreds of pages, in templates that stamp the wrong H1 on every blog post or footers that inject heading tags site wide. Run the analyzer on your key templates, not just individual pages: the blog post template, the service page template, the homepage, and the landing page template. Template level issues multiply across every page that uses them, so one fix can repair hundreds of outlines at once.

For full site coverage, pair manual checks with a crawler. Tools like Screaming Frog extract every H1 and H2 on the site into a spreadsheet, where duplicates, missing H1s and overlong headings surface in minutes. Export the list, sort by issue type, and work through the templates first. Then spot check individual high value pages with our heading analyzer to see the full H1 to H6 outline in context. This two layer approach, crawler for breadth and the analyzer for depth, is exactly how our technical audits handle heading architecture.

Heading keyword placement: where your keywords belong

Put your primary keyword in the H1, a secondary keyword or question phrase in at least half of your H2 tags, and write every heading for the human reader first. The H1 deserves the exact primary keyword near its start because it is the strongest topical signal on the page. H2 tags are where secondary keywords and People Also Ask style questions belong, since those headings often anchor featured snippets and AI citations.

Never repeat the same keyword in every heading. A page where six H2 tags open with the identical phrase reads as manipulation to users and algorithms alike, and Google's helpful content systems target exactly this kind of mechanical optimization. Use natural variations, synonyms and related entities instead. Google treats "link building pricing" and "how much link building costs" as the same topic, so you gain coverage without repetition. Check the final distribution with our keyword density checker and read more keyword strategy on the blog. Moz's on page SEO guide reinforces the same principle: include keywords in headings where natural, never forced.

Heading structure in JavaScript frameworks and single page apps

Single page apps break heading structure in ways traditional sites never do. The most common failure is one static H1 in the app shell shared across all routes. Next comes content rendered by JavaScript after load, where headings exist in the browser but not in the HTML Google first fetches. Google documents that rendering happens separately from crawling, which can delay JavaScript injected headings by days.

Render one accurate H1 per route on the server or at build time, so the initial HTML already carries the correct outline. Then test what the crawler actually sees: copy the rendered DOM, not the raw source, and paste it into the analyzer above. If the outline differs between raw and rendered HTML, the framework is the problem, not the content. Google's JavaScript SEO documentation explains the two wave process in detail. For framework level fixes, our technical team handles implementation, and the blog documents common rendering pitfalls.