Semantic HTML elements: what the check tests and how to fix it

Looks for article, section, nav, main and aside on each crawled page. An average of 3 of 5 passes. Presence only: header, footer and figure are not scored.

Structured Data · Weight 0.5 in the w2agent Score

How common is it?

41% of 1223 measured sites where this check applied pass.

Latest audit of each site under rubric v3.1. Sites where the check did not apply or could not be measured (for example, no llms.txt for the llms.txt checks) are left out. A partial result does not count as a pass.

What this check tests

For every crawled page (the homepage plus a sample of same-site pages) the audit parses the served HTML and records which of these elements appear anywhere in it: article, section, nav, main, aside. Each page scores the share of those five it contains (0, 20, 40, 60, 80 or 100). The check averages that over all crawled pages and rounds.

  • Pass: the average is 60 or more, which is three of the five on a typical page.
  • Partial: above 0 but under 60.
  • Fail: 0, meaning none of the five on any page.

The parser also notes header, footer and figure, but they do not enter the score. Only presence counts. The check does not test that main appears once, that section has a heading, that nav holds links or that the elements are used for what they mean. A <section> wrapped around everything counts the same as a well-chosen one. The elements must be in the HTML the server returns; markup built by script in the browser is not seen.

Because it asks for five element types, a simple page can pass honestly with main, nav and section. A page with no article and no aside can reach at most 60, so it has no room to miss any of the other three. Treat the threshold as a heuristic.

Why it matters to agents

The semantic elements say what role a block plays. MDN describes main as behaving like a main landmark, says a document must not have more than one visible main, and says its content should be unique to the document rather than repeated navigation, sidebars or footers. nav marks a navigation section, article a self-contained composition that could be distributed on its own, aside content only indirectly related to the main content, and section a generic standalone section that should normally have a heading.

For a tool that wants the page's own content rather than its boilerplate, those boundaries are cheap to use. A page built only from div elements gives it nothing to separate on. No official source cited here says that AI assistants or search engines weigh these elements, so this is a structure check with weight 0.5, not a ranking lever. Landmarks are also what assistive technology uses to navigate, which is a reason to do it right regardless.

How to fix it

  1. Wrap the page's unique content in a single <main>. Keep the site header, the main navigation and the footer outside it.
  2. Put the primary links in <nav>. A page may have several nav elements; MDN suggests aria-labelledby to tell them apart.
  3. Use <article> for a self-contained item: a post, a product card, a doc page body. Use <aside> for a sidebar or call-out that is only indirectly related to the main content.
  4. Use <section> for a distinct chunk of a page and give each one a heading, as MDN advises. If a block has no heading, a div is probably the better element.
  5. Do not add elements just to raise the score. An empty <aside> helps no one.
  6. Confirm in the page source that the elements are in the served HTML and not created by script.

Headings give the same structure inside these blocks; see Heading hierarchy. If your content only exists after JavaScript runs, see Content accessible without JS.

Examples from measured sites

Up to 10 of the highest-scoring sites in each group, from recent audits. Failing includes partial results.

Passing

Failing or partial

Sources

Verified against these sources on

Does your site pass this check?

Check your own site →