Content chunking

nounalso called chunking, passage indexing or passage-level retrieval

Definition

Content chunking is the splitting of a page into smaller passages — often a heading and the text beneath it — that an AI retrieval system indexes, scores and quotes individually, which makes the section, not the whole page, the unit that competes for a citation.

Updated 5 min read9 cited sources

On this page7 sections

Why it matters for founders and small teams

AI engines don’t judge your article as a whole; they judge each section on its own, which means one well-built section can win a citation for a site with no other authority on the topic. For a small team, that makes it the most leveraged editing habit there is: every section should answer one question without leaning on the rest of the page.

How does content chunking work in AI search?#

Content chunking works by splitting each fetched page into passages — often a heading and the text under it — that are indexed, retrieved and scored individually, so the engine can quote the one section that answers a question and ignore the rest of the page.

Perplexity describes the step in its architecture write-up: a content-understanding module splits each document into “self-contained spans” that are “individually retrieved and ranked at query time.” Google moved the same way in classic search in October 2020, saying it could now “better understand the relevancy of specific passages” in addition to the page as a whole, a change it expected to improve 7 percent of search queries (Google).

  1. 1

    The page is fetched as HTML

    Most AI fetchers read raw HTML and don’t run JavaScript, and Claude’s fetcher can truncate long pages to a token budget.

    Your lever: Server-render the page, and put the most important sections early.

  2. 2

    It's split into passages

    Headings, paragraphs, lists and tables mark the boundaries. Perplexity parses list- and table-heavy pages more formulaically.

    Your lever: Use real H2s and H3s, and real HTML tables for specs and comparisons.

  3. 3

    Each passage is embedded and indexed

    The passage is represented on its own, without the paragraphs around it. See vector embeddings.

  4. 4

    Passages compete for the question

    Retrieval and reranking score passages against the query, and the answer quotes the winners.

    Your lever: Answer each section’s question in its first sentence.

Why do chunks lose context?#

Chunks lose context because each passage is indexed and read on its own, so anything it relies on from elsewhere on the page — the product name, the time period, what “it” refers to — disappears when the passage is lifted out.

Anthropic’s contextual retrieval research gives the textbook example: the chunk “The company’s revenue grew by 3% over the previous quarter” is useless alone, because it doesn’t say which company or which quarter. Anthropic’s fix — adding a short generated summary of the surrounding document to every chunk before indexing — cut failed retrievals by 35%, by 49% when paired with keyword matching, and by 67% with reranking added.

You can’t count on every engine doing that repair for you. The safe move is to write passages that carry their own context:

Leans on the pageStands alone
“It integrates with Slack and Teams.”“Plannora integrates with Slack and Microsoft Teams on every plan.”
“As mentioned above, pricing starts at $8.”“Plannora’s pricing starts at $8 per user per month.”
“This makes it ideal for smaller teams.”“Plannora’s free tier covers teams of up to five people.”
“Revenue grew 3% last quarter.”“Plannora’s revenue grew 3% in Q2 2026.”

Rankbox benchmark

The Passage-Size Benchmarks

The published numbers that bound a good passage, from vendor documentation and large citation studies. Use them as guardrails when editing a section, not as quotas.

≤150 characters

Quotable sentence

The most text a Claude web-search citation quotes from a page, per Anthropic’s documentation. Put each key fact in a sentence this short.

Over 120 words

Section length

In SE Ranking’s study, ChatGPT citations rose with the words between headings: 2.7 on average under 50 words, 4.6 at 120–180 and 5.7 above 180. A correlation, not a rule — the clear lesson is to avoid thin sections.

First 30%

Where the answer sits

44.2% of ChatGPT citations came from the first 30% of a page in Growth Memo’s analysis of 1.2 million answers.

A few hundred tokens

Production chunk size

Anthropic describes typical RAG chunks as “usually no more than a few hundred tokens” — about one well-scoped section.

10 kB ≈ 2,500 tokens

Page weight Claude reads

Anthropic estimates an average 10 kB web page at about 2,500 tokens; its fetcher truncates content beyond the limit a developer sets.

First 2 MB

HTML Googlebot fetches

Content after the first 2 MB of a URL’s HTML is not fetched, rendered or indexed.

How to read it: Read the list from the sentence up: one fact in one short sentence, inside a focused section with enough substance to stand alone, near the top of a page light enough to be read in full. Each number comes from a different engine or study, so treat the set as a shared envelope rather than one engine’s spec.

Free to use and adapt. If you cite it, link to rankbox.xyz/glossary/content-chunking.

How do you write content that chunks well?#

Write content that chunks well by giving every section one question-shaped heading, answering it in the first sentence, naming the subject instead of using pronouns, and giving each section enough substance to stand alone — very short sections earned the fewest ChatGPT citations in SE Ranking’s study.

  1. One heading, one question. The heading is the chunk’s label, so make it the question the section answers.
  2. Answer first. Growth Memo found 44.2% of ChatGPT citations came from the first 30% of a page, and the same logic holds inside a section. See answer-first content.
  3. Name the subject in each section’s opening sentence, even if the previous section just did.
  4. Don’t go too thin. SE Ranking found sections under 50 words averaged 2.7 ChatGPT citations, against 4.6 for sections of 120–180 words and 5.7 for longer ones.
  5. Use real structure. HTML tables and lists are parsed as structure, and they split cleanly into passages.
  6. Put key facts in short sentences. Claude’s citations quote at most 150 characters.

Common mistakes with content chunking#

The most common content chunking mistakes are sections that depend on the one before, headings too clever to say what’s below them, answers buried after a long preamble, and key facts hidden in images, tabs or scripts a fetcher never sees.

Myth

Chunking means breaking content into tiny pieces.

Reality

Google says there’s no need to, and tiny sections lose the evidence that makes them worth citing. The goal is self-contained sections, not short ones.

Myth

A long page gets more chances to be cited.

Reality

Only if its sections stand alone. A 4,000-word page with the answer buried in paragraph nine can have fewer winning passages than a focused 1,500-word page.

Myth

Headings are just for design.

Reality

Headings mark passage boundaries and tell retrieval what each passage is about. “Our approach” labels nothing; “How long does Plannora take to set up?” labels everything.

Myth

Content in tabs and accordions is fine.

Reality

Only if it’s in the server-rendered HTML. Text injected by JavaScript on click is invisible to fetchers that don’t run scripts — every major AI fetcher except Google’s. See server-side rendering.

Sources

  1. 1.Architecting and evaluating an AI-first search APIPerplexity Research · research.perplexity.ai
  2. 2.Optimizing your website for generative AI featuresGoogle Search Central · developers.google.com
  3. 3.How AI is powering a more helpful Google (Search On 2020)Google · blog.google
  4. 4.Introducing Contextual RetrievalAnthropic · anthropic.com
  5. 5.Web search toolClaude Developer Platform · platform.claude.com
  6. 6.Web fetch toolClaude Developer Platform · platform.claude.com
  7. 7.How to optimize for ChatGPTSE Ranking · seranking.com
  8. 8.44% of ChatGPT citations come from the first third of contentSearch Engine Land (Growth Memo study) · searchengineland.com
  9. 9.Googlebot's 2 MB fetch limit and renderingGoogle Search Central Blog · developers.google.com

Know someone who’d find this useful? Send it their way.

Written by

Rankbox Team

The team behind Rankbox. We study how ChatGPT, Perplexity, Gemini, and Google AI Overviews choose their sources, and publish what we learn so you can put it to work.

See which AI answers cite you today

Enter your site to see how often ChatGPT, Perplexity, Gemini, and Google cite your brand, and exactly what to publish next.

No credit card required · Free 7-day trial