On the content chunking debate in GEO / AEO
While Google has said that content chunking is unnecessary for appearing in its own AI systems, it’s worth understanding the concept, why it’s an often-discussed tactic in GEO/AEO, and why optimizing content at the “chunk” level can still matter for visibility.
Content chunking & AI extractability
Many AI systems do not “read” your entire page at once during their information retrieval phase. Instead, they utilize a process called chunking — breaking documents into smaller, discrete segments that can be independently indexed and retrieved.
AI sometimes uses a content chunking method because LLMs often operate on ultra-large knowledge bases, containing more “tokens” of contextual data and content than can be easily included in a single prompt, thus requiring a more scalable RAG (Retrieval-Augmented Generation) system.
Per Anthropic:
“RAG works by preprocessing a knowledge base using the following steps:
- Break down the knowledge base (the “corpus” of documents) into smaller chunks of text, usually no more than a few hundred tokens; [*Editor’s Note: 100 tokens = roughly 75 words.]
- Use an embedding model to convert these chunks into vector embeddings that encode meaning;
- Store these embeddings in a vector database that allows for searching by semantic similarity.
- At runtime, when a user inputs a query to the model, the vector database is used to find the most relevant chunks based on semantic similarity to the query. Then, the most relevant chunks are added to the prompt sent to the generative model.”
Critically, the retrieval step for some AI systems operates at the passage level, not the page level — typically retrieving sections of 100-300 words that semantically match the query.
Passage-level retrieval is common because it is often more efficient and relevant than sending an entire long document into a model for every query. LLMs have context window limits, so feeding an entire 3,000-word article into the model for every query would be computationally expensive and often irrelevant. Instead, many AI retrieval systems surface only the most relevant passages, which are then used as context for answer generation. This means your content’s internal structure can influence how easily individual sections are interpreted, retrieved, and reused by systems that operate at the passage level. A 3,000-word article might have ten different sections that could be independently retrieved for ten different queries — but only if each section is structured to stand on its own.
Semantic content chunking
According to research from Anthropic (“Introducing Contextual Retrieval in AI Systems”), standard RAG (Retrieval-Augmented Generation) systems often fail when individual content chunks lack sufficient context, leading to “failed retrievals” or hallucinations:
“In traditional RAG, documents are typically split into smaller chunks for efficient retrieval. While this approach works well for many applications, it can lead to problems when individual chunks lack sufficient context.”
For GEO, this means you should move beyond “fixed-size” chunking (splitting content into smaller chunks purely by a set number of characters or length) in favor of “Semantic Chunking”; organizing your content into semantically complete, coherent modules. This strategy ensures that each section of your content represents a “complete thought” that an AI can extract and use without losing the surrounding logic, making it significantly easier for AI “Judges” to verify your evidence chain.
Keeping entities clear across sections
With semantic chunking, you’ll want to avoid the “pronoun penalty,” or using pronouns instead of specific entity names in any given chunk of content.
As explained in the Anthropic research:
“A relevant chunk might contain the text: ‘The company’s revenue grew by 3% over the previous quarter.’ However, this chunk on its own doesn’t specify which company it’s referring to or the relevant time period, making it difficult to retrieve the right information or use the information effectively.”
This suggests that, if you want to make it as easy as possible for AI retrieval systems to understand our content, you should keep core entities visible throughout your content ‘chunks’. Repeat key entity names and terms consistently so the reasoning chain is easy to follow across individual content sections.
While pronouns may improve human readability, excessive substitution of pronouns for core entities (e.g., replacing “Steve Jobs” with “he,” or “the company” with “it”) can reduce the visibility of those entities within a passage. In AI retrieval systems that evaluate passages based on entity presence and relational clarity, this can weaken alignment with the query’s underlying reasoning structure.
While the Anthropic research on contextual retrieval for RAG systems was actually written to introduce a solution to this information chunk retrieval issue (“Contextual Retrieval solves this problem by prepending chunk-specific explanatory context to each chunk before embedding”), and while Google says content chunking is unnecessary for visibility its own AI systems, you still might want to consider semantically chunking your content as a GEO best practice to help your content maintain utmost ease of retrieval across all AI systems, regardless of how sophisticated or contextually aware their RAG systems may be.
GEO and SEO experts still routinely echo the suggestion to optimize your content into semantically coherent chunks. After studying AI patents and research papers for two years, SEO and AI search thought leader Olaf Kopp wrote in a 2026 LinkedIn post that one of his key takeaways is:
“Structure content as self-contained, answer-first chunks so LLMs can find, extract, and cite precise information.”
Content chunking isn’t about gaming retrieval algorithms. It’s about recognizing that if some AI systems will only “see” one section of your article at a time, that section needs to be independently valuable and comprehensible.
This doesn’t mean arbitrarily or awkwardly breaking content up into fixed-length smaller parts. What you need is clear sectioning, for both human readers’ comprehension and information gain and machine-readability: use H2 and H3 headings to organize content into logical sub-topics, ensure each section addresses a distinct aspect of your subject, and write each section so it can be understood without requiring the reader (or the AI) to have read what came before.
After all, Google is not saying that content structure is irrelevant. Common, longstanding SEO and general writing advice also recommends organizing content into clear paragraphs, sections, and headers for human readers, too. Clear structure is good SEO, good UX, and likely helpful for some AI systems’ information retrieval processes.
In short: You probably don’t need to artificially “chunk” content into rigidly imposed, limited-length sections (especially for Google’s AI systems). But do structure and segment content clearly because human readers, crawlers, accessibility tools, and many AI retrieval systems all benefit from passage-level clarity.
About Lumar’s GEO / AEO explainer series
In this Lumar series, we’re exploring strategies for generative engine optimization (GEO), also known as answer engine optimization (AEO) — that is, how to boost your brand’s AI visibility and likelihood of earning mentions or citations from LLMs and AI-powered platforms like ChatGPT, Claude, Gemini, Perplexity, or Google’s AI Overviews and AI Mode.
