How to group content in <section> blocks instead of flat <div> soup
Last updated:
AI Search Score checks how your content is grouped. Pages built as one long stack of <div>s — with no <section> or <article> grouping — read as undifferentiated soup to a machine. Grouping related content into sections gives it structure that agents and engines can navigate.
Why this matters
A clean accessibility tree is the “machine-eye view” of your page. When each thematic block sits in its own <section> (ideally with a heading), an AI agent or screen reader can understand where one idea ends and the next begins. Flat <div> stacks flatten that meaning. This is also part of Google’s new agentic-readiness signals.
How to fix it
In the WordPress block editor (Gutenberg), wrap each heading-and-its-content in a Group block, and set the Group to output a <section> element:
- Select a heading and the blocks under it (up to the next heading).
- Use “Group” (the toolbar’s group option) to wrap them.
- In the Group block’s settings → Advanced → HTML element, choose
<section>. Repeat for each thematic block. Each section ideally starts with a heading.
(This is exactly the approach used on this site’s own pages — grouping flat blocks into sections lifted the semantic-HTML score with no custom code.)
How to check it worked
Re-scan. “Content grouped in section/article” should turn green, and the section count in the detail should rise from near-zero. The div-to-section ratio drops, which is what you want.
Prefer this done for you? See our services.