AI systems read HTML the way assistive technologies do: they look for semantic landmarks (

,

,

,

, ), then extract the smallest self-contained chunk that answers the user's question. Pages built with a clean heading hierarchy, real list and table elements, and minimal

-soup get extracted and cited more reliably than visually-equivalent pages built from generic containers.

TL;DR

Use one

, ordered

/

headings phrased as questions or direct answers, real

/
/

lists, properly headered

elements with /

, and HTML5 landmarks ( , , ). Skip nested soup. The result is a page an LLM can chunk into clean, self-contained answers. Why semantic HTML matters for AI LLMs and AI search systems consume raw HTML, not the rendered visual page. As one news-SEO analysis puts it, "it's much simpler for ChatGPT to parse a few dozen semantic HTML tags rather than several hundred (or even thousand) nested tags to find a webpage's main content." Microsoft Advertising's own optimization guide names title, description, and the H1 tag as "important signals AI systems use to interpret purpose and scope." Research on LLM HTML understanding finds that fine-tuned models are measurably more accurate at semantic classification when they see well-structured HTML. Translation: the cleaner the markup, the smaller the chunk an LLM needs in context to extract the right answer. Heading hierarchy Rules Exactly one per page. It should match (or closely reflect) the page title and the canonical question the page answers. Don't skip levels. → → only. Never jump → . Phrase H2/H3 as questions or direct answers when the section is meant to be extractable. Generic labels like "Why it matters" are fine for narrative flow; question-shaped headings (e.g., "What is answer extraction?") win extraction races. Never use a heading purely for visual styling. If you want big bold text, use CSS — not an . Anti-patterns Multiple tags per page (confuses both Google news ranking and LLM chunkers). used as a decoration above a sentence that isn't a section header. "Welcome to our homepage" as an H1 — says nothing about the page's topic. Lists Use the right list type for the right semantic relationship: Element Use when Example Order does not matter Feature bullets, requirements Order matters (steps, ranking) Tutorial steps, top-10 list Term/definition pairs Glossary, API parameter reference The W3C accessibility guidance explicitly notes "description lists are groups of related terms and descriptions which are connected programmatically." AI extractors use the / pairing as a strong signal that the is a defined term. Anti-patterns A series of paragraphs that visually look like a list but carry no semantic grouping. A whose items are unrelated multi-paragraph essays — lists imply parallelism; if items aren't parallel, use sub-headings instead. A definition list rendered as a styled two-column grid — the term/definition pairing is invisible to AI. Definition patterns For reference and definition pages, two patterns extract reliably: Pattern A: H2 question + immediate answer paragraph ("answer target"). As eSEOspace describes it, "an answer target is a concise, standalone paragraph designed specifically to directly answer a targeted query. It usually sits immediately below an H2 or H3 heading." Copy <h2>What is semantic HTML?</h2> <p>Semantic HTML is the practice of using HTML elements according to their intended meaning rather than for visual appearance.</p> Pattern B: with term and definition. Copy <dl> <dt>Semantic HTML</dt> <dd>HTML markup whose tags convey meaning and structure, not just visual presentation.</dd> </dl> Mix them: use Pattern A for the canonical first answer on the page, and Pattern B for additional terms in a glossary block at the bottom. Tables Real elements (not grids) carry structural meaning AI extractors use to align rows and columns. Rules Wrap header cells in with . Wrap row labels in when the first column is a label. Use for a one-line summary of what the table shows. AI extractors and screen readers both pick this up. Keep one logical concept per table. Two unrelated comparisons → two tables. Anti-patterns A used purely for layout (use CSS Grid or Flexbox). Headerless tables (no ) — AI cannot reliably tell which row is the header. Merged cells used decoratively. Merge only when the data semantically warrants it. Document landmarks (HTML5) Wrap the page in HTML5 landmarks so AI systems can ignore boilerplate and zoom in on the article content: Copy <header>…site nav…</header> <main> <article> <h1>…page title…</h1> …answer-first content… </article> <aside>…related links…</aside> </main> <footer>…</footer> The and pair is the strongest single "the answer is in here" signal for LLM extractors. Without them, an AI parser must guess which block is the article — and often guesses wrong on -soup pages. Answer-first chunking LLM-driven AI search retrieves passage-level chunks, not whole pages. To make each chunk self-contained: Put the direct answer in the first 1-2 sentences after the H2 or H3. Do not bury it after a long preamble. Repeat the entity name in each section. Avoid pronouns like "it" or "this" as the section opener — a chunk extracted out of context loses the antecedent. Keep paragraphs short. Two to four sentences each, so the chunker can pick up clean boundaries. Use bold sparingly. Bold the term being defined, not whole sentences — over-bolding flattens the signal. Quick reference: do / don't / Concern Do Don't Headings Single , ordered / Multiple s, skipped levels Lists Real , , blocks styled to look like lists Tables with / grid masquerading as a table Landmarks , , Generic everywhere Definitions H2 question + answer paragraph or Bolded term in middle of a paragraph Bold/italic Emphasize the entity term Bold whole paragraphs Pronouns Repeat entity name per section "It..." / "This..." as section opener Common mistakes Building the page in a visual editor that emits soup. Audit the source HTML; if you don't see real headings, lists, and landmarks, rebuild the template. Using as a style hook for any large bold text. Style with CSS classes; reserve heading tags for actual section breaks. Treating as deprecated. It isn't — it remains the correct semantic for term/definition pairs and is well supported by AI extractors. Rendering content client-side without server-side fallback. Many AI crawlers do not execute JavaScript; if the article body is rendered only by JS, the AI sees an empty page. Validation checklist [ ] Exactly one , matching (or closely reflecting) the page title. [ ] No skipped heading levels. [ ] H2/H3 phrased as questions or direct answers where extraction matters. [ ] Lists use / / , never simulated with blocks. [ ] Tables use and (when helpful) . [ ] Page wrapped in and HTML5 landmarks. [ ] Article content present in the initial server-rendered HTML. [ ] Each section opens by repeating the entity name, not a pronoun. [ ] Answer paragraphs sit immediately under their H2/H3 heading. FAQ Q: Does it matter to AI whether I use vs ? Yes. and carry semantic meaning that AI extractors use to identify the page's main content. A is generic and provides no structural cue. Use for thematic groupings inside an article and for the article itself. Q: Should every H2 be phrased as a question? No, but every H2 that is supposed to be extractable as a direct answer should be. Mix question-shaped H2s for canonical Q&A sections with descriptive H2s for narrative or workflow sections. A 100% question-only outline reads awkwardly to humans and gives diminishing returns. Q: Are description lists ( ) really used by AI systems? Yes. The / pairing is a strong, machine-readable signal that the element is a term being defined. Glossaries, parameter references, and FAQ-style term lists extract more reliably from than from styled blocks. Q: What about ARIA roles — do they help AI? They can. ARIA roles like role="main" or role="article" reinforce semantic intent when you cannot use the corresponding HTML5 element. Prefer the native HTML5 element first; use ARIA only when the native element is impractical for layout or framework reasons. Q: How do I check whether my page is AI-readable? View the raw HTML source (not the rendered DOM). Confirm: one , ordered / , real lists and tables, / wrappers, and the article body present in the server response. A simple curl check (curl -sL | grep -E ' : Barry Adams, "Why Semantic HTML matters for SEO and AI." https://www.seoforgooglenews.com/p/why-semantic-html-matters-for-seo : Microsoft Advertising, "Optimizing Your Content for Inclusion in AI Search Answers" (October 2025). https://about.ads.microsoft.com/en/blog/post/october-2025/optimizing-your-content-for-inclusion-in-ai-search-answers : Gur, Furuta et al., "Understanding HTML with Large Language Models," arXiv:2210.03945. https://arxiv.org/abs/2210.03945 : r/SEO, "Headings in the age of AI crawlers." https://www.reddit.com/r/SEO/comments/1opffly/headings_in_the_age_of_ai_crawlers/ : W3C Web Accessibility Initiative, "Content Structure." https://www.w3.org/WAI/tutorials/page-structure/content/ : eSEOspace, "How to Structure a Page So AI Can Extract Answers Instantly." https://eseospace.com/blog/ai-content-structure-extraction/ : Franco Folini, "The Curious Case of the Vanishing Definition List: Why DL Deserves Your Love" (March 2026). https://francofolini.com/2026/03/15/the-curious-case-of-the-vanishing-definition-list-why-dl-deserves-your-love/ Related Articles checklist Direct answer optimization: patterns for getting picked as the answer Checklist of direct answer patterns — definition-first openings, answer boxes, constraints, and evidence — to get picked as the cited source by AI engines. specification Agent Knowledge Base Specification: Structure, Refresh, and Versioning Production specification for AI agent knowledge bases: document model, chunking strategies, metadata enrichment, refresh cadence, version pinning, and rollback. guide AI search ranking signals: what likely matters (and how to test) What likely matters for AI search ranking in 2026 — retrieval, authority, freshness, and structure — plus a reproducible way to test each signal instead of guessing. Topics #geo#source-selection Stay Updated GEO & AI Search Insights New articles, framework updates, and industry analysis. No spam, unsubscribe anytime. Subscribe