Topic 3 min
Retrieval & Embeddings
Your page is chopped into chunks and stored as vectors; the engine pulls the chunk that is the closest semantic match, not the best-ranked page.
Why it mattersA self-contained, on-topic paragraph can be retrieved even when the page does not rank.
Definition & Foundation
What it is, in plain words
When an engine indexes your page, it does not store the page; it chops it into chunks and stores each chunk as an embedding: a list of numbers representing what the text means. At answer time the query becomes a vector too, and the engine pulls the chunks that sit closest in meaning-space. The unit of competition is the chunk, and the match is semantic; a paragraph can be retrieved for a question that shares none of its keywords.
Two practical consequences follow. First, a self-contained paragraph can be retrieved even when its page never ranks; retrieval rewards the best-matching chunk, not the best-ranked URL. Second, structure decides your fate before quality gets a vote: if your answer is smeared across three sections, no single chunk carries it, and no chunk gets retrieved. Citation studies consistently favor self-contained passages of roughly 134–167 words, about the size one chunk holds cleanly.
Four Terms, One Picture
How your page looks to a retrieval system
Chunk
A slice of your page: typically a heading plus the text under it, or a few adjacent paragraphs. Engines retrieve chunks, not pages. If the answer straddles two chunks, neither contains it.
Embedding
Each chunk is converted into a vector that encodes its meaning. "How do I stop emails going to spam?" and "improving deliverability" land close together in this space even with zero shared words.
Vector similarity
Retrieval = "find the chunks whose vectors sit nearest the query's vector." Nearness is meaning-likeness. This is why answering the actual question beats repeating the keyword.
Semantic match vs keyword match
Classic SEO asked "does the page contain the words?" Retrieval asks "does this chunk mean the answer?" Synonyms, paraphrases, and plain language all match; keyword stuffing adds nothing.
Putting It to Work
Structure pages so the right chunk exists
You can't control how an engine chunks your page, but you can write so that any reasonable chunking yields a self-contained, retrievable answer. That is a structural craft:
The chunk-friendly structure playbook
One question per section
Give every section a single job, stated in its heading (ideally as the question users ask). A section that answers three questions poorly beats none of the three chunks that would each answer one well.
Answer within the first two sentences under the heading
Chunk boundaries often fall at headings, so the heading plus its opening lines is the most reliably intact unit. Put the direct answer there; elaborate below.
Make each passage survive amputation
Resolve pronouns, repeat the entity name, restate the subject; the chunk may be read with zero surrounding context. "It also supports this" is dead weight; "Acme also supports SAML single sign-on" retrieves.
Keep key passages in the 130–170 word zone
Long enough to fully answer, short enough to fit a chunk cleanly. If a key answer runs 400 words, extract its essence into a lead paragraph and let the detail follow.
Write for the paraphrases too
Semantic match means "email warm-up," "sender reputation," and "why do my emails bounce" can all pull the same chunk, if the chunk speaks plainly. Use the words real users use, not only your product's vocabulary.
Verification Checks
How to know it's really done
Your structure is retrieval-ready when chunks survive on their own. Click a check to mark it verified:
Works Together With
The nodes this one leans on
Tools for this from How AI Engines Work
Go deeper from The RAG Pipeline
Always current
These links resolve live: what you get is generated or filtered the moment you click.
Fresh from the field feed refreshed July 8, 2026
- Jul 7 SEO Study: 5 Lessons From Running AI Agents Across Every Search via @sejournal, @lorenbaker Search Engine Journal
- Jul 7 Google On Using Markdown For AI SEO via @sejournal, @martinibuster Search Engine Journal
- Jul 6 SMX Now: Build better site architecture for SEO, AI, and users Search Engine Land
- Jul 6 Google Answers Question About LLMs-Author.txt For SEO via @sejournal, @martinibuster Search Engine Journal