The engine changed, not the rules

How does AI search work (and what it means for SEO)

Your rankings held.

Your content is good by every checklist you have ever used.

And your organic traffic still fell off a cliff after the last core update.

The reflex is to assume you broke something, or that “quality” now means something you have not decoded.

I do not think either is true.

What changed is the engine reading your content. Most SEO advice still describes the engine we had before and that gap is where the anxiety lives.

So this is a mechanism walkthrough, not another “AI Overviews are here, adapt or die” post.

I want you to see the actual machine, to see how an AI search system retrieves, ranks, and cites, and which of your existing SEO signals it still runs on.

Once you can see it, the drop stops being mysterious and the work stops being guesswork.

AI search is a new engine, not a new SERP

The common framing is that AI Overviews (AIO) are a new kind of SERP.

A richer results page, optimized the way you once optimized for featured snippets.

That framing is comforting, and I think it is wrong. It is also why “I published good content and lost traffic” keeps happening.

On r/SEO the same story repeats. One tech blog reports its Google organic traffic down 73% in six months. Another, with 1,000+ posts, watches it collapse after the December 2025 core update. The sentiment underneath recurs: “ranking doesn’t mean what it used to, now it’s about being cited.”

Those are not two complaints. They are one event seen from outside.

The page still ranks. It just stopped being picked by a different system that now sits in front of the ranking you can see.

Here is the distinction I keep coming back to:

A SERP is a list. Classic search retrieves documents, orders them, and you compete for a position in that order.

An AI search system does not hand you a list to win. It pulls passages from many documents, weighs them against each other, writes one answer, and cites a handful of sources.

The ranked links still exist underneath. But the AIO box you are worried about is the output of a retrieval-and-synthesis pipeline, not a position you climb.

Why now, and why Google first? Because it already had the index, the compute, and the query volume to make a generated answer the default instead of an experiment.

The engine is new. The web it reads is the same one you have been optimizing. That is the whole reason the fix is mechanical, not magical, and it is what the rest of this piece is about.

The engine: a RAG pipeline, end to end

Most explainers draw AI search as a straight line: query in, answer out, five neat boxes in between.

I find that picture misleading. The real thing is a loop:

A planner reads your query and splits it into the smaller questions it thinks it needs to answer. (That step is query fan-out, and it earns its own piece, so I break down how query fan-out works separately.) For each sub-question, a router decides how to go find the answer: a keyword index, a vector search over meaning, or a structured data feed. None of this is hypothetical. Google holds a patent on generating query variants, a trained model that turns one query into many, which is the mechanism the industry now calls query fan-out.

Then it retrieves, judges what it got back, and here is the part the straight-line drawing misses. If the evidence is thin or contradicts itself, the system loops and asks again before it writes a single word.

This whole arrangement has a name: retrieval-augmented generation, or RAG.

The short version is that the model does not answer from memory. It retrieves real passages first, then writes its answer grounded in what it pulled. Strip away the fancy name and AI search is a retrieval system with a writer bolted onto the end. Think of it as a personal assistant helping users filter through the noise, save them time, and put the most relevant results on the map based on their preferences, search history, local documents, and more. Just like that. Like snapping your fingers.

Search is moving from something you do to something an agent does for you.

You used to scan the list of links yourself; now an agent scans, filters, and synthesizes on your behalf. iPullRank describes the agent’s behavior vividly. It will “tear the binding off the book, ignore the table of contents, and pull out only the pages and paragraphs it needs, sometimes revisiting them again and again.” Your content is read by the agent first, the human second, if a human reads it at all. Depending on the task, the agent may answer and the person may never see your page.

The retrieval step is where the SEO you already do still does the work.

Two methods run side by side:

One is lexical, the classic keyword match, with BM25 as the workhorse, and it rewards the exact terms on your page.

The other is semantic where content becomes embeddings, vectors of numbers that place a passage by its meaning instead of its wording, so a page can match a question it never says word for word.

A single query can fan out into somewhere between five and twenty of these internal retrievals, each one pulling its own candidate passages.

Then comes selection, and this is the gate most GEO advice skips. The system does not keep everything it retrieved. It reranks the candidates, often by comparing them against each other in pairs, and only a handful survive to be cited. Retrieval gets you considered. Reranking decides whether you are used.

Synthesis is the last step. The model takes the survivors and writes one answer, with citations pointing back to the passages it leaned on. And if the critic earlier in the loop was not satisfied, none of this happened yet, because it sent the planner back for another pass.

Step back and look at what this is built from. Crawlable pages. Clean, parseable content. The exact terms and the clear meaning of what you wrote. Authority strong enough to survive a head-to-head.

None of that is new, is it?

AEO, GEO, LLM optimization, whatever the label is this quarter, these are layers on top of the same retrieval the last decade of SEO already fed. They are not a replacement for it. That is the thread I pull through the rest of this piece.

How we got here: a decade of information retrieval

None of this appeared overnight, and that matters more than it sounds.

The engine in the last section runs on ideas that have been compounding for more than a decade. Walk the lineage and the “everything changed” panic gets a lot smaller.

For most of search history, retrieval counted words. TF-IDF and then BM25 scored a page on how often your terms appeared, weighted by how rare they were. Effective, but blind: to that machine, “car” and “automobile” are strangers. Thus the need for stuffing keywords everywhere.

Then came embeddings.

In 2013, Word2Vec turned words into vectors, positions in a space where meaning is distance, so “car” and “automobile” finally landed next to each other. The idea underneath is old linguistics: you know a word by the company it keeps.

Embeddings still read words in isolation.

Transformers fixed that.

The 2017 paper “Attention Is All You Need” (that flat little title is the paper the entire LLM era stands on, no big deal) let a model weigh every word against every other word in a sentence, so context finally counted.

BERT, in 2018, read in both directions at once, which is how a system learns that “bank” means different things in “river bank” and “savings bank.”

From there it kept widening.

Google’s MUM, in 2021, reached across languages and formats, pulling meaning from text, images, and video together.

MUVERA, in 2024, made the math cheap enough to run this kind of retrieval at Google’s scale without the latency falling apart.

So when someone tells you AI search is a clean break from SEO, hand them this timeline. The pieces arrived one at a time, each solving the limit before it, and the result is the engine you now optimize for.

New on the surface, yes, but a decade deep underneath.

The pipeline is intent-dependent

Not every query wakes the engine up.

Some still return a plain list of links; others trigger a full generated answer.

The difference is intent.

Semrush tracked this across 2025. In January, informational queries (the “how does X work” kind) triggered an AI Overview 91.3% of the time. By October it was 57.1%. Over the same months, commercial, transactional, and even navigational queries climbed from near-zero into double digits. That shift matters more than it looks.

A year ago, AI Overviews were mostly an informational-query phenomenon you could plan around; now they are spreading into commercial and transactional queries too, and the mix keeps moving. You can no longer assume which of your pages sit outside the blast radius.

Intent is one axis. Industry is the other.

The same engine engages unevenly by topic, and according to the same Semrush’s data analysis, science leads AI Overview saturation at around 26%, with computers and electronics and then people and society close behind, while plenty of other niches barely register.

This is why your blog and your storefront do not behave alike. An informational post lives in the intent class AI Overviews have favored the most so far, so it gets pulled into answers and quietly loses the click. A product or category page sits in commercial and transactional territory, where AIO is newer and thinner, so the mechanics, and the damage, look different on each.

And one more thing, because it trips SEO and non-SEO people up:

A single page can serve more than one intent at once, and that is fine. What breaks things is dilution: spreading a page so thin trying to answer everything that it answers nothing cleanly.

Which intents a query actually spans is decided by the fan-out, not by your gut. Ask “best running shoes for flat feet” and the engine quietly splits it into a how-do-I-choose question, a which-models question, and a what-causes-flat-feet question, each pulling different pages. That decomposition is the whole game, and I take apart the query fan-out mechanism separately.

What this changes for SEO

So what actually changes in your week? Less than the panic suggests, and more than the checklists admit.

The unit of optimization shrinks.

You are no longer writing a page to rank; you are writing passages that can be lifted out and still make sense on their own. ALM Corp frames the test better than I could: copy a paragraph, drop it alone into an answer box, and ask if it still holds up. If it needs the three paragraphs above it to make sense, the engine cannot use it.

That one test reorganizes a lot. Answer the question early. One idea per section. Define your terms before you lean on them. Put the reusable sentence near the top, not buried under a windup.

It also moves the target from keywords to entities and meaning.

The old reflex was to repeat a phrase until the page “owned” it. That does little for a system reading embeddings; what helps is being unambiguous about the things you discuss and how they relate, so your passage lands in the right neighborhood of meaning instead of just matching a string.

Measurement is where most people will get blindsided.

Your rankings can hold while your real footprint moves, because a citation badly under-reports how often you were actually used.

iPullRank’s read is that the gap runs 3 to 10 times, meaning you might feed 4 of 12 internal retrievals on a query and get cited once. Rank tracking alone goes blind here. You start watching whether you show up across a query’s sub-questions, how much of the answer you cover, and whether that presence holds steady over time.

And the page is no longer the only thing on the table. Passages, files, images, and video get indexed and pulled into answers too, so the question is not only whether your HTML is good but whether the right format of your answer is reachable at all.

Here is the part I want you to sit with:

The foundations of SEO do not break here. Crawlable, clean, clearly-meant content is still what gets retrieved. Google frames this as still just SEO, and I would not take that at face value.

It is an interested party widening the work without widening anyone’s budget, while internally running AI Mode and classic ranking as separate systems. The discipline holds; the scope outgrew the label.

So the rebrand pitch, the one selling GEO as a clean replacement for everything you know, does not survive contact with the mechanism. There is a longer argument to have there. For now, the short version is enough.

Go back to where we started.

The page that “ranked fine” and lost its traffic was not punished for quality. It just was not built to be retrieved, judged, and cited by the engine that now sits in front of the results. That is fixable, and now you know what you are fixing.

I genuinely believe that the bar is placed higher now.

For those used to cracking the code, so to speak, and really do what actually makes sense and what these systems are designed for, there was always a clear, unmistakable action to take:

no shortcuts,

no tactics,

do what’s right for the visibility (and now authority) of the business long-term.

Lock that in: long-term.