Website & Development
Semantic HTML: how to make your pages readable for AI
Copy for AI
Semantic HTML means using the right tag for the right content.
An <h2> says “section heading”, a <ul> says “list”, a <table> says “data in rows and columns”.
So a crawler reads the meaning of your page instead of guessing it.
The verdict: if you want ChatGPT, Google AI Overviews or Perplexity to understand and cite your pages, clean semantic markup is the foundation. It isn’t an AI trick, it’s good craftsmanship that also helps accessibility and SEO.
Below: what it is, why AI reads code rather than styling, and which choices make content extractable.
What is semantic HTML exactly?
It’s HTML where every tag describes what the content is, not what it looks like.
Those tags carry meaning.
And that meaning is exactly what a machine needs to understand your page.
Meaning versus appearance
The opposite is markup that only controls appearance.
Think of a title that’s really a plain <div> with a large, bold font. Or a “list” made of separate lines with dashes in front.
To a human, both look identical to the real thing. To a machine, the difference is enormous:
- Semantic: each piece states its role explicitly
- Styled only: everything stays one undifferentiated block of text
The same content, two ways
Here’s an example of the same section built twice:
<!-- Styled only: the machine sees boxes -->
<div class="big-bold">What does a B2B website cost?</div>
<div>- Design</div>
<div>- Development</div>
<!-- Semantic: the machine sees a heading and a list -->
<h2>What does a B2B website cost?</h2>
<ul>
<li>Design</li>
<li>Development</li>
</ul>
In a browser, CSS can make both look the same.
In the code, only the second one says “heading” and “list”.
Rule of thumb: semantic HTML makes the structure you intend visually readable in the code. And that code is what AI gets to see.
Our glossary entry on HTML covers the basics if tags are new to you.
Why does AI read your HTML and not your styling?
Because crawlers collect the raw HTML of your page, not the finished image a visitor sees.
Colours, font sizes and positions set through CSS are largely noise for an extraction process.
What counts is the tree of tags underneath.
How a model splits your page
When an AI processes your page, it tries to split the content into meaningful chunks:
- what the main title is
- which questions the page addresses
- which answer belongs to which heading
- what’s a list and what’s data
If all of that sits in semantic tags, the model can pull those chunks straight out.
If you imitated it with styling, the model has to guess from patterns. And guessing produces errors.
Crawlers first need to get in
Extraction starts with access. Our own robots.txt lets every crawler in, AI bots included:
Our own robots.txt, October 2026: one rule for all crawlers, so every AI bot can fetch the raw HTML.
Once the bot is in, it reads the markup, not the design. Our guide on allowing AI crawlers covers the access side.
Watch out: content that only appears after JavaScript runs may never reach some crawlers. See client-side rendering and AI search.
Why identical pages perform differently
Two pages that look identical to a human can perform completely differently in AI answers.
One delivers neatly demarcated, citable chunks.
The other delivers a wall of text in which the model has to introduce structure itself.
Clean markup lowers that threshold.
It raises the chance that one specific piece of your page gets picked up as an answer.
Want to check your own site? Our piece on whether your website is readable for AI gives a quick test.
How do you make content machine-extractable?
Start with a logical heading structure, and use real lists and tables where they fit.
Here’s the decision path for each block of content:
The steps below cover each choice.
Use one clear heading hierarchy
One <h1> with the main topic, <h2>s for the sub-questions, and <h3> only for parts within a section.
Don’t skip levels.
Choose the level by meaning, not by how large you want the text.
MDN’s heading reference says the same: prefer one <h1>, don’t skip levels, and use CSS rather than headings to resize text.
A clean hierarchy is literally a table of contents the machine can follow. Our guide to heading structure for SEO has worked examples.
Phrase headings as the question someone asks
“What does a B2B website cost?” is far more useful to an AI than “Investment”.
The heading already matches a real question.
People do search in questions. In our own Search Console, question queries in the top 10 clicked at 0.19%, against 0.09% for other queries:
Non-branded queries ranking in the top 10, customerimpact.be, 1 June to 15 October 2026. From our CTR study.
That’s roughly double, in our own data.
Follow each heading directly with a short, complete answer before you elaborate.
Then every section becomes a standalone, citable block.
Put enumerations in real lists
A series of points belongs in a <ul> or <ol>. Not in separate paragraphs with dashes, and not in a table misused as a list.
A real list tells the machine: these are separate, equal-ranking items.
That’s exactly the content that often comes back as a bullet in AI answers.
Use tables only for real data
Comparing options, prices or specifications? Then use a <table> with clean header cells.
A good table with clear row and column headers is one of the easiest data forms to extract. We tested how AI engines handle them in tables in AI answers.
The W3C table tutorial asks for header cells in <th> and data in <td>. It also states that tables aren’t meant for layout.
Watch out: a layout table gives the machine a wrong signal about what the content means.
Mark other roles with the right elements
A few more roles to make explicit:
- Quote:
<blockquote> - Code example:
<code> - Navigation:
<nav> - Main content:
<main>
The more roles you make explicit, the less a machine has to interpret.
The common thread
Each time, you tell the machine what something is, instead of letting it infer this from what it looks like.
Our heading tags glossary entry sums up the levels. For the broader technical build, see our complete guide to building a B2B website.
How does semantic HTML relate to schema markup?
They complement each other: semantic HTML structures your visible content, schema markup adds explicit meaning on top.
Semantic tags say that something is a heading, a list or a table.
Schema markup, or structured data, adds that a block describes, for example, a frequently asked question, a product or an organisation.
The order matters
You need both, but in the right order.
Schema markup on a page with messy, non-semantic HTML is a coat of varnish on a shaky base.
Google’s structured data introduction warns against marking up information that isn’t visible to the user. So the markup has to describe content that’s really on the page.
Check what’s detected
Once both layers are in place, test them.
Here’s what the Schema Markup Validator detects on our own English homepage:
The Schema Markup Validator on our own English homepage, October 2026. Each detected type should match what the page visibly says.
If a type describes something you can’t see on the page, that’s the mismatch Google warns about.
How that extra layer works is in our explanation of schema markup and the broader principle of structured data. For the steps, see how to implement schema markup.
Schema can’t rescue a sloppy page
The pitfall is thinking schema markup can compensate for a sloppy page structure. It can’t.
Is semantic HTML only for AI, or also for your regular visitors?
You don’t have to choose: the same markup helps AI, accessibility and classic search at once.
It’s not a separate AI trick. It’s solid craftsmanship that pays off on several fronts.
Accessibility: the direct effect
Screen readers rely entirely on semantic tags to read a page aloud and make it navigable.
A user who jumps through your page by headings can only do so if your headings are real headings.
Sloppy markup shuts out part of your visitors. That’s one of the mistakes in our piece on common accessibility mistakes, and the basics are in website accessibility.
Classic SEO: real but smaller than claimed
Google’s SEO Starter Guide recommends headings to help users navigate.
Yet it says heading order doesn’t matter for Google Search, because the web in general isn’t valid HTML.
So don’t expect a ranking boost from tags alone.
Your visitors: faster answers
A clear heading structure helps visitors find what they need faster.
That directly helps turn visitors into leads.
At Customer Impact we build platform-independently on a clean, semantic base.
Whether your site runs on Webflow, WordPress or headless, the principle doesn’t change.
Here’s how the gains stack up:
| Who reads the markup | What semantic HTML gives them |
|---|---|
| AI crawlers and models | Clear chunks to extract and cite |
| Screen readers | Headings and lists to navigate by |
| Google Search | Easier understanding, no direct ranking boost |
| Your visitors | Faster scanning, quicker answers |
If you’re bound by accessibility rules, our WCAG compliance service starts from the same markup.
For visibility in AI search engines, the strategic context is in our guide to generative engine optimization.
How do you check the semantic HTML of a page?
Look at the page the way a machine does: without the styling.
Four checks cover most of it, per page template.
Step 1: Read the page without CSS
Open the page source, or switch off styles in your browser’s developer tools.
What’s left is what a crawler sees.
If the structure falls apart into one long column of text, the meaning lived in the CSS.
Step 2: Check the heading outline
HTML has six heading levels, <h1> to <h6>. List the ones on your page in order.
You want one <h1>, then <h2>s, then <h3>s inside them, with no jumps from <h2> to <h4>.
Tip: a heading that only exists to make text bigger is the first thing to fix.
Step 3: Check lists and tables
Search the source for lines that start with a dash or a bullet character inside a <p> or <div>. Those are lists in disguise.
Then check every <table>: does it hold real data, with <th> header cells?
Step 4: Test the extra layer
Run the page through a structured data test, as in the validator screenshot above.
Every type it finds should match visible content. Our schema markup testing guide covers the tools.
Rule of thumb: fix the templates, not single pages. One clean template fixes every page built on it.
Frequently asked questions
Does semantic HTML improve my Google rankings?
Not directly. Google’s SEO Starter Guide says heading order doesn’t matter for ranking. The gains are in understanding, accessibility and AI extraction.
Is semantic HTML the same as schema markup?
No. Semantic HTML structures your visible content with the right tags. Schema markup adds a separate layer of explicit meaning, such as “this is an FAQ”.
How many h1 headings should a page have?
MDN recommends one <h1> per page, with <h2> and <h3> below it in order, without skipping levels.
How do I check the semantic HTML of my site?
Switch off the CSS and read what’s left, check the heading outline, look for fake lists and layout tables, and run a structured data test. Fix it per template, so every page built on it improves at once.
Does semantic HTML help screen readers?
Yes, directly. Screen readers use headings, lists and landmarks such as <nav> and <main> to let users jump through a page instead of listening to it top to bottom.
Can I use a table for page layout?
No. The W3C table tutorial says tables aren’t meant for layout. Use them only for real data in rows and columns.
The short summary
Use the right tag for the right content, so a machine can read your structure directly.
AI reads the code, not the styling. So a logical heading hierarchy, real lists and real tables make your content easy to extract and cite.
Schema markup builds on top of that, but never replaces a sloppy base.
Want our web designer to put your pages on a clean, machine-readable base that generates leads?
Contact us and we’ll look at where your site leaves structure on the table.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.