Headings

What it is

Headings are HTML elements identified by tags from <h1> to <h6>. They help organize page content into sections and subsections with a readable hierarchy.

In general:

• <h1>: represents the main page title or central topic;
• <h2>: identifies the primary sections of the text;
• <h3> through <h6>: introduce subsections and deeper levels of detail.

A common mistake is choosing a heading level only for visual effect. Font size, weight, and color should usually be controlled with CSS, while heading tags should describe the logical structure of the content.

Why it matters

Headings help make the page structure clearer for readers, maintainers, assistive technologies, and systems that parse the HTML. A clear H1 can help identify the main topic, while H2 and H3 tags break the content into sections that are easier to scan and understand.

A consistent hierarchy can bring practical benefits such as:

• Accessibility: it makes navigation easier for screen readers and other assistive technologies;
• Visual scanning: it helps readers orient themselves more quickly on longer pages;
• Maintenance: it makes it easier to see whether the content is organized logically.

A tidy heading structure does not guarantee ranking, indexing, or visibility. Missing or disordered headings are not always severe issues, but they can make a page harder to interpret. The scanner observes the declared HTML structure and does not evaluate the full editorial quality of the text.

How this is checked

The scanner analyzes the HTML structure of the page to observe how heading levels are distributed.

The current check verifies:

• whether the page contains at least one heading;
• whether an <h1> tag exists and whether more than one appears;
• whether there are empty headings, meaning tags without useful text inside;
• whether the hierarchy clearly skips levels, for example from <h1> to <h4>;
• whether some headings appear to be used only decoratively;
• the total count and sequential order of the detected headings.

The scanner does not measure copy quality and does not set absolute rules for how the text must be written. It observes the declared structure to help you decide whether technical review is worthwhile.

Possible findings

Each finding should be read as a review signal, not as an automatic penalty.

Missing H1

No <h1> tag was found on the page. In many cases, adding a clear H1 can be useful, especially on main pages.

Multiple H1s

Two or more <h1> tags were detected. This is not always a severe problem, but it can make the central topic less clear.

Empty headings

One or more heading tags are present in the code but do not contain visible or useful text.

Disordered heading hierarchy

The logical order of the headings does not follow a coherent sequence and may make the content harder to read.

Skipped heading level

The structure moves from one level to another that is much lower, such as H1 to H4, without intermediate levels.

No headings detected

The page contains no tags from <h1> to <h6>, so there is no declared section structure.

Potentially unclear structure

The overall distribution of headings suggests that the page may be difficult for people or automated systems to navigate or interpret.

Recommended action

1. Identify the main page topic: clarify what the content is primarily introducing.
2. Consider using a clear H1: this is often recommended, especially for main pages, but it should not be treated as a rigid rule.
3. Use H2s for major sections: break the main content into readable blocks.
4. Use H3s and lower levels only when they are useful: add real subsections, not decorative labels.
5. Remove empty or purely visual headings: use CSS or other components for styling instead.
6. Work gradually: review and improve your text structure first on the most important, longest, or most confusing pages, without chasing rigid rules or abstract schemes.
7. After each change: update a few elements at a time and run a new scan.

How to fix it

Static HTML

If you manage the HTML directly, organize the tags so they reflect the logical hierarchy of the text, and use CSS to control visual presentation.

Simple example:

<h1>Main page topic</h1>
<h2>Main section</h2>
<h3>Subsection</h3>

WordPress / Page builders

If you use WordPress or a page builder, heading levels are often managed from the visual editor.

• Select the heading block and set the correct level from the editor menu.
• Check that the post title, which the theme often exposes as H1, is not duplicated unnecessarily inside the body content.
• Review widgets, sidebars, footers, and global blocks so secondary elements are not marked up as H1 or H2 without a clear reason.

CMS / E-commerce

In ecommerce platforms and custom CMS setups, product and category titles are often generated by templates.

• Check that product names use a tag that matches the page context.
• Make sure filters, labels, and related blocks do not fragment the hierarchy with overly important headings.
• If the same issue repeats across many pages, start from the template instead of editing each page manually.

How it appears in the report

In the report, the Headings check shows the list and order of the headings detected on the page, highlighting levels from H1 to H6 and any skipped levels or inconsistencies.

The scanner does not enforce a perfect structure or judge the overall quality of the writing. It provides a practical map of the HTML so you can decide whether it is worth reviewing and improving your text structure.

When to run a new scan

Run a new scan after reorganizing text blocks, changing heading levels in the editor, or updating CMS templates. This helps you confirm that the revised hierarchy is being detected properly and that the structural signals are more consistent.