Semantic HTML Structure

What this parameter measures

HTML5 semantic elements describe the role of each region instead of leaning on generic containers, and this parameter checks whether your page uses them. friendly4AI scans the raw HTML for six landmark tags (<main>, <article>, <section>, <header>, <footer>, and <nav>) and counts how many distinct ones appear. The more of these landmarks present, the more clearly the document communicates its structure. The check is case-insensitive and reads the server-provided HTML, so it rewards markup that ships in the initial response.

Why it matters for AI-readiness

Semantic elements tell AI systems which part of the page is the main content, which is navigation, and which is page chrome. When your primary content sits inside <main> and <article>, crawlers and answer engines like ChatGPT, Gemini, and Perplexity can isolate the substance from the boilerplate and quote it accurately. A page built entirely from <div> and <span> forces machines to guess at boundaries, which lowers extraction quality and the odds your content is surfaced correctly.

How we score it

Under the v4.4 methodology, this Content Structure parameter is a gradient driven by how many of the six landmark tags appear. The processor computes a coverage ratio (distinct tags found / 6) and maps it to a score. A page passes (100) when five or six landmarks are present — score >= 80 — signalling widespread, consistent semantic usage. It earns a partial when two to four landmarks are present (roughly 33 to 67), meaning some structure exists but is applied unevenly. It fails (0) when at most one landmark is found and the layout is essentially <div>/<span>-only. Note: the published "partial" rubric maps to the processor's middle band rather than a fixed 50, because the score is proportional to tag count.

How to fix common issues

• Wrap your primary content in <main> and use <article> for standalone, self-contained content blocks.
• Use <header> and <footer> for page chrome and <nav> for every navigation region, including secondary menus beyond the top bar.
• Group thematic content into <section> elements with a heading, instead of nesting more <div> wrappers.
• Apply the elements consistently across the layout — partial, scattered usage only reaches the middle band.
• Re-scan after refactoring to confirm five or more landmarks are detected in the initial HTML.