What Is Semantic HTML? A Designer’s Guide to Header, Nav, Main and Section Tags
If you have ever opened a template and found forty nested <div> tags before reaching an actual sentence, you have met div soup. Semantic HTML is the cure. It is the practice of choosing HTML elements for what the content means, not for how it looks. This guide is written for designers, front-end beginners and site owners. No jargon dump: just a plain definition, two versions of the same layout side by side, and a quick reference for the question everyone gets wrong (article vs section vs aside). What is semantic HTML? The short answer Semantic HTML is the use of HTML tags that describe the role and meaning of the content they wrap, so that browsers, assistive technologies and search engines can understand the structure of a page without seeing its design. A <div> says nothing. It is a generic box. A <nav> says “this block is navigation”. A <h1> says “this is the main title of the page”. Same pixels on screen, completely different information for machines. Semantic elements: header, nav, main, section, article, aside, footer, h1 to h6, figure, table, button, time, address Non-semantic elements: div and span (useful, but purely structural hooks for CSS and JavaScript) Think of it like a floor plan. A div layout is a building where every room is labelled “room”. A semantic layout labels them “entrance”, “corridor”, “living room”, “storage”. Anyone who cannot see the building can still move around it confidently. Side by side: div soup vs semantic markup Below is the exact same blog layout written twice. Visually identical once styled. Radically different for a screen reader and for Google. Version A: the div-heavy layout <div class=”top-bar”> <div class=”logo”>Atelier Panpan</div> <div class=”menu”> <div class=”menu-item”><a href=”/”>Home</a></div> <div class=”menu-item”><a href=”/blog”>Blog</a></div> <div class=”menu-item”><a href=”/contact”>Contact</a></div> </div> </div> <div class=”content”> <div class=”post”> <div class=”post-title”>Choosing a colour palette</div> <div class=”post-date”>10 October 2026</div> <div class=”post-body”><p>Colour is never decoration only…</p></div> </div> <div class=”sidebar”> <div class=”widget-title”>Related reading</div> <div><a href=”/typography”>Typography basics</a></div> </div> </div> <div class=”bottom”><div>© 2026 Atelier Panpan</div></div> What a machine sees: a stack of anonymous boxes. The “title” is not a heading, it is styled text. There is no navigation landmark, no main content region, no way to skip anything. See mozilla.org for their take. Version B: the semantic layout <header> <a href=”/” class=”logo”>Atelier Panpan</a> <nav aria-label=”Main”> <ul> <li><a href=”/”>Home</a></li> <li><a href=”/blog”>Blog</a></li> <li><a href=”/contact”>Contact</a></li> </ul> </nav> </header> <main> <article> <h1>Choosing a colour palette</h1> <p>Published on <time datetime=”2026-10-10″>10 October 2026</time></p> <section> <h2>Start with contrast</h2> <p>Colour is never decoration only…</p> </section> <section> <h2>Test on real screens</h2> <p>Calibrate before you commit…</p> </section> </article> <aside aria-label=”Related reading”> <h2>Related reading</h2> <ul> <li><a href=”/typography”>Typography basics</a></li> </ul> </aside> </main> <footer> <p>© 2026 Atelier Panpan</p> </footer> Same design, but now the page has landmarks, a heading outline and a machine-readable date. Nothing was added visually. Only meaning. What changes for a screen reader user This is the part most tutorials skip. Screen reader users rarely read a page top to bottom. They jump, using three shortcuts: Landmark list to jump between regions (banner, navigation, main, complementary, contentinfo) Headings list to scan the outline of the page like a table of contents Links list or form controls list to reach interactive elements In Version A, the landmark list is empty and the headings list is empty. The user has to arrow through every single line to find the article. In Version B, they press one key and land on <main>. Semantic tags and their implicit accessibility roles Tag Implicit role What it is for How many per page <header> banner (only at top level) Logo, site title, main nav, intro block One site header, plus optional headers inside article or section <nav> navigation Major groups of links: main menu, breadcrumbs, pagination Several, each with its own aria-label <main> main The unique content of this page, excluding repeated chrome Exactly one <article> article A self-contained item that would make sense republished alone As many as needed <section> region, only if it has an accessible name A thematic chunk of content that owns a heading As many as needed, always with a heading <aside> complementary Tangential content: sidebar, related posts, pull quote, ad block Several, labelled <footer> contentinfo (only at top level) Legal links, copyright, contact, secondary nav One site footer, plus optional footers inside article <div> none (generic) Pure layout wrapper for CSS grid, flexbox, animation Unlimited, but only when no semantic tag fits Important nuance: a bare <section> with no heading and no label is treated as a generic container, exactly like a div. Give it a heading or an aria-label, otherwise you gained nothing. A step-by-step version exists if you prefer that format. What changes for Google Semantic HTML is not a magic ranking button, and no tag by itself pushes you to position one. What it does is reduce ambiguity, and reduced ambiguity is what crawlers reward. Main content detection: search engines try to separate boilerplate (menu, sidebar, footer) from the real content. <main> and <article> make that job trivial, which matters for how your page is summarised and quoted. Heading hierarchy: h1 to h6 give Google a topical outline. A single h1 plus logical h2 and h3 levels helps the engine understand the subtopics you cover. Featured snippets: clean <table>, <ol> and <ul> markup is far more likely to be lifted into a rich result than a grid of styled divs. Navigation and internal linking: links inside <nav> and breadcrumb markup help crawlers map your site architecture. Dates and metadata: <time datetime=”2026-10-10″> is unambiguous, whereas “10/10/26” inside a div is a guess. Put simply: semantic HTML will not rescue weak content, but it removes friction between good content and the machines that have to classify it. article vs section vs aside: the quick reference Here is the decision path we use internally. Run through it in order and stop at the first “yes”. Could this block be cut out and republished elsewhere and still make sense on its own? Use <article>. Blog post, product card, user review, forum reply, news item, comment. Is
What Is Semantic HTML? A Designer’s Guide to Header, Nav, Main and Section Tags Read More »
