Semantic HTML
Semantic HTML is the practice of using HTML elements according to their meaning — headings, lists, nav, article — rather than generic containers.
Semantic markup makes a page easier for browsers, assistive technology, search engines, and AI engines to understand. It is a foundation of both accessibility and machine-readability, and it costs nothing beyond the discipline to use the right element.
How it works
Browsers and assistive technology build an accessibility tree from the HTML, and search and AI crawlers read the same structure. Elements such as <header>, <nav>, <main>, <article>, usually one <h1> followed by headings in order, <button> and <a> tell them what each part of the page is and what it does, with no extra code.
A generic <div> tells them nothing; making it behave like a button then needs roles, keyboard handling and focus management added by hand.
Example
A "Read more" control built as a <div> with a click handler cannot be reached by keyboard and is invisible to crawlers as a link. The same control written as <a href="/insights/…"> works for keyboards, screen readers and search engines at once.
In practice
When briefing a developer, ask them to confirm a few specifics: one main heading per page with subheadings in order, navigation marked as navigation, links that go somewhere built as links, buttons that do something built as buttons, and form fields with visible labels connected to them. These are quick to check in a browser's developer tools, and an accessibility checker will flag most failures. If the site uses a page builder or theme, ask whether those choices can be set per block, and who on your team will set them.
Content editors affect semantic structure as much as developers. Choosing a heading because it looks the right size, bolding a line instead of using a heading, or pasting text from a word processor with odd formatting all damage the structure. A short guide for editors, explaining which heading levels to use and why, prevents most of it. Watch also for content that only appears after scripts run, such as tabs or accordions built in unusual ways, and check that the text is present in the page's HTML so crawlers and assistive technology can reach it.
Why it matters for your business
You will rarely see semantic HTML, but you pay for its absence. Some page builders and themes produce layers of generic containers that look fine on screen yet leave keyboard and screen-reader users stuck, give crawlers a weaker picture of the page, and make later accessibility fixes expensive because the structure has to be rebuilt. Asking for proper headings, real links and buttons, and correctly labelled forms in a brief costs nothing extra at the start. It also supports WCAG compliance and technical SEO at the same time. A two-minute test is pressing Tab through your key pages: if you cannot reach and use everything, the markup is part of the problem.
Common mistakes
- Choosing heading levels for their size instead of their place in the outline.
- Using buttons for navigation and links for actions.
- Rendering key content only with JavaScript, so crawlers that do not run it see an empty page.
Questions people ask
How can I tell if my website uses semantic HTML?
Try three quick checks. Press Tab through a page and see whether every link and button can be reached and used. Open the browser's reader mode and see whether the main content and headings appear sensibly. Then run a free accessibility checker, which flags missing headings, unlabelled form fields and buttons built from generic elements.
Do page builders produce semantic HTML?
Some do well and some poorly, and the result often depends on how the builder is used. Many let you choose the correct heading level and element for each block, but default to generic containers if nobody sets them. Inspect a finished page or run an accessibility check before committing to a builder for a large site.
Does semantic HTML change how my website looks?
No. Appearance is controlled by CSS, so a semantic page can look exactly like one built from generic containers. The difference is what browsers, assistive technology and crawlers understand about each part. That is why a site can look perfect and still fail visitors who use a keyboard or a screen reader.