How to Fix Passage-Level Content Chunking for AI Answers
This check flags pages where content is written as long, unbroken text or as sections that depend on earlier paragraphs to make sense. Search engines and AI answer engines pull individual passages, not whole pages, so a chunk that says "as mentioned above, this costs less" is useless on its own. By the end of this guide, your key pages will be split into headed sections that each answer one question completely and can be quoted without the rest of the page.

Why it matters
Google ranks individual passages, and AI systems such as Google AI Overviews, ChatGPT search, Perplexity and Copilot split pages into chunks of a few hundred words before deciding what to quote. If a chunk has no clear heading, starts mid-thought or relies on pronouns that point to earlier text, it scores poorly for relevance and gets skipped, even when the page as a whole is the best answer. Self-contained sections are retrieved and cited more often, and they also help skimming readers and screen-reader users who move between pages by heading.
What you need
Step-by-step fix
Measure section length on each flagged page
Open a flagged page, press F12 to open DevTools, go to the Console tab and paste the snippet below. It prints a table of every heading and the number of words that follow it before the next heading. Any row over about 300 words, or a large "(top)" block before the first heading, is a chunk that needs splitting.
(() => { const root = document.querySelector('main, article') || document.body; const rows = []; let cur = { heading: '(top)', words: 0 }; root.querySelectorAll('h1,h2,h3,h4,p,li,td,blockquote').forEach(el => { if (/^H[1-4]$/.test(el.tagName)) { rows.push(cur); cur = { heading: el.tagName + ': ' + el.textContent.trim().slice(0, 60), words: 0 }; } else if (!el.closest('li') || el.tagName === 'LI') { cur.words += el.textContent.trim().split(/\s+/).filter(Boolean).length; } }); rows.push(cur); console.table(rows.filter(r => r.words > 0)); })();Map each section to one question
List the questions the page answers, using Search Console queries (Performance > Search results > Queries, filtered to the page) and the People Also Ask box for your main keyword. Give each question its own section. If one section answers two questions, split it; if two sections answer the same question, merge them.
Add descriptive H2/H3 headings every 150-300 words
Break long blocks with real heading elements, not bold paragraphs or styled divs. Use H2 for main topics and H3 for subtopics, without skipping levels. Write headings that name the subject and the angle, so the heading alone tells a machine what the chunk is about.
- Weak: "Overview", "More details", "Step 2"
- Strong: "How long does a domain transfer take?", "Step 2: Unlock the domain at your current registrar"
<section id="domain-transfer-time"> <h2>How long does a domain transfer take?</h2> <p>A domain transfer to Example Co usually takes 5 to 7 days. The delay comes from the losing registrar's approval window, which ICANN rules allow to run for up to 5 days.</p> <p>You can shorten it by approving the transfer email from your current registrar as soon as it arrives.</p> </section>
Lead every section with a direct answer
Make the first one or two sentences under each heading a complete answer of roughly 40-60 words. Put supporting detail, examples and caveats after it. AI engines often quote only the opening of a chunk, so the answer must be there, not in the fourth paragraph.
Remove dependencies on other sections
Read each section as if it were the only text on the page. Replace anything that only makes sense in context:
- "As mentioned above" / "see below" → restate the fact in a short clause
- "It", "this", "they" at the start of a section → use the actual noun ("The Pro plan", "Example Co's API")
- "The second option" → name the option
Repeat the subject in each section even if it feels redundant to a human reader; one extra noun costs nothing.
Keep paragraphs short and use lists and tables
Limit paragraphs to 2-4 sentences and one idea each. Turn sequences into ordered lists, options into bulleted lists and comparisons into HTML tables with a header row. Structured elements are split cleanly by chunkers and are frequently quoted verbatim.
<h3>Example Co plan limits compared</h3>
<table>
<thead><tr><th>Plan</th><th>Monthly requests</th><th>Price</th></tr></thead>
<tbody>
<tr><td>Starter</td><td>10,000</td><td>$0</td></tr>
<tr><td>Pro</td><td>500,000</td><td>$49</td></tr>
</tbody>
</table>Add a jump-link table of contents
On pages with five or more sections, add a table of contents linking to each section id. This exposes the structure in the first screen of HTML, lets Google show "Jump to" links, and makes deep links to a single passage possible.
<nav aria-label="On this page">
<ul>
<li><a href="#domain-transfer-time">How long does a domain transfer take?</a></li>
<li><a href="#transfer-cost">How much does a domain transfer cost?</a></li>
</ul>
</nav>Re-measure and re-run the audit
Publish, clear any page cache or CDN cache, then run the console snippet from step 1 again. Every row should be under about 300 words and there should be no large untitled block at the top. Finally, re-run the audit so the share of passing pages is recalculated.
Platform-specific notes
WordPress
In the block editor, use the Heading block (choose H2/H3 in the toolbar) rather than bold Paragraph blocks. Set section anchors in the block sidebar under Advanced > HTML anchor. Yoast SEO and Rank Math both include a Table of Contents block that builds jump links from your headings automatically.
Shopify
Edit blog posts under Online Store > Blog posts and pages under Online Store > Pages. Use the rich text editor's paragraph-style dropdown to set Heading 2/Heading 3. To add id anchors, click Show HTML (the <> icon) and add id attributes to the h2 tags manually.
Webflow
In a CMS Rich Text field, use the + menu or formatting bar to insert H2/H3. Webflow does not let you set ids on headings inside Rich Text, so add a small script in Page settings > Custom code (before </body>) that assigns slug ids to each h2, or build a separate TOC with a third-party component.
Next.js / MDX
Write sections as ## and ### Markdown headings and add the rehype-slug and rehype-autolink-headings plugins to your MDX config so each heading gets a stable id. Make sure content is server-rendered or statically generated so crawlers see the headings in the initial HTML.
Wix
In the Wix Blog editor, select text and choose Heading 2 or Heading 3 from the text style dropdown. For regular pages built in the Editor, use Text elements set to H2/H3 under Edit Text > Semantic tag, and add anchors via Add Elements > Anchor for jump links.
Check that it worked
✅ How to verify
- Run the DevTools console snippet on each fixed page and confirm no section exceeds about 300 words and no untitled block appears before the first heading.
- View the page source (Ctrl+U / Cmd+Option+U) and confirm the headings are real h2/h3 elements present in the initial HTML, not injected later or faked with styled divs.
- Copy three random sections into a blank document and check each one names its subject and answers its heading without needing the rest of the page.
- Re-run the audit and confirm the percentage of pages passing this check has increased.
⚠️ Common mistakes
- Adding headings but leaving the sections dependent on each other, with openers like "This means..." or "As shown above", so extracted chunks still make no sense.
- Using vague headings such as "Introduction", "Details" or "Conclusion" that tell neither readers nor AI systems what the passage answers.
- Faking headings with bold text or large-font paragraphs, which look like sections on screen but are invisible as structure to crawlers.
- Over-splitting into 30-word fragments under dozens of headings, which strips each chunk of enough context to be a useful answer.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
What is passage-level content chunking?
It is the practice of organising a page into short, headed sections that each fully answer one question. Search engines and AI answer engines split pages into passages before ranking or quoting them, so each passage needs to stand on its own.
How long should each section be for AI search?
Aim for roughly 150-300 words per heading. That fits comfortably inside the chunk sizes most retrieval systems use while leaving room for a direct answer plus supporting detail.
Does Google still use passage ranking in 2026?
Yes. Google has used passage-based ranking since 2021 to surface specific sections of long pages, and AI Overviews draw on the same idea of retrieving individual passages, so clearly separated sections continue to matter.
Will repeating the subject in every section look like keyword stuffing?
No, as long as you repeat it naturally, such as writing "the Pro plan" instead of "it" at the start of a section. That is clarity, not stuffing; stuffing is forcing the same keyword phrase into every sentence.
How to Fix Missing Outbound Citations in Your Content
How to Fix Brand + Category Co-occurrence for AI Search
How to Fix Local Entity Data for AI Assistants
How to Declare an AI Crawler Policy in robots.txt and llms.txt
How to Verify Your Site in Bing Webmaster Tools