📖 In This Issue

  • Featured Snippets: (News & Resources)

  • Cover Story: ​Retrieval Augmented Generation (RAG)​ is the future of SEO

  • Operator of Interest: Eli Schwartz

  • Learn This: Deep Learning

📰 Featured Snippets (News & Resources)

Rumors suggest that Meta, OpenAI, and others are each developing their own index of the web so they can be less reliant on search engines. Which makes this week’s newsletter ever more interesting.

Chris Long details a test he performed on brand positioning in LLMs. A lot of good tips here that align well with some of my past advice.

Kuber Mehta tells us why asking a LLM to humanize it’s output risks a degraded quality. I see this a lot, but mostly when including more detailed lengthy prompts or instruction sets.

Mark Zuckerberg published a personal AI manifesto on Monday. He outlines his very idealistic vision for how AI will empower and transform, and of course Meta will drive it all. While it seems grandiose, it is at least more grounded than his now forgotten Metaverse dreams.

Your Understanding Of RAG Is Critical To Unlocking AI Search & GEO Success

What if the most important concept in AI search isn’t prompting, citations, or even “GEO”, but retrieval? A lot of the conversation starts at the end: which brands appear, which URLs get cited, and which competitors seem to show up more often. Then we try to reverse-engineer the output. That makes sense because the output is visible. But it can also push us to focus on the wrong part of the system.

Many AI search experiences retrieve information before generating an answer. The exact implementations vary across products, but the useful lesson for SEOs is the same: before information can influence an answer, the system often has to find and select it. That makes retrieval one of the most important concepts for understanding where SEO fits into AI search.

​How Search Enabled RAG Works​

​A basic overview of how AI Assistants use Search Engines with​ ​Retrieval Augmented Generation (RAG).

  1. ​A user sends a question or request to the ​​AI Assistant​​ in the form of​
    ​a prompt.​

  2. The ​​LLM ​​reads the prompt and decides if it needs to use web search to​
    ​properly respond.​

  3. ​If the​​ LLM​​ decides to use web search, it will then create a collection of​
    ​search queries to send to a​​ search engine ​​to collect more​
    ​information. This process is called ​​Query Fan Out​​.​

  4. ​The ​​AI Assistant​​ will then send the queries to the​​ search engine
    ​through an API.​

  5. The​​ search engine ​​will receive each query and send back the same​
    ​Search Engine Result Page​​ that it sends human users.​

  6. The ​​AI Assistant​​ will visit the most relevant pages listed in the​
    Search Engine Result Pages ​​and collect the page's content.​

  7. The ​​AI Assistant​​ then combines all of the content it has collected​
    ​from the web pages, with any rich data it found on the ​​Search Engine​
    ​Result Pages​​ (rich snippets, FAQs, Knowledge Graph, Local Listings),​
    ​with the original prompt from step 1, and sends it to the LLM​​.​

  8. ​The ​​LLM​​ then takes all of the collected data + the original prompt and​
    ​finally creates a response to the user.​

RAG changes the GEO conversation

If retrieval happens before generation, then GEO cannot only be about “optimizing for LLMs.” It is also a retrieval problem. That brings familiar SEO questions back into focus: can the system access your content, understand what it is about, identify the important facts, and trust it as useful evidence for the question being asked?

Those questions are not identical to traditional ranking questions, but they are not foreign to SEO either. Google’s own guidance says existing SEO best practices still apply to its generative AI features, including crawl access, internal linking, textual availability, and accurate structured data. The interface changed. Many of the constraints underneath it did not.

The risk is treating AI visibility as a generation problem

The temptation is to optimize the part of AI search we can see. Teams rewrite copy to “sound like AI,” add endless FAQ sections, create pages around hypothetical prompts, and obsess over individual citations. Some of those experiments may be useful, but the mistake is treating generation as the whole system.

If your content never makes it into the relevant retrieval set, none of that matters. A perfectly written answer cannot influence the output if the system cannot discover it, understand it, or considers other sources more useful. Generation is visible. Retrieval mostly is not. That makes the output easier to sell than the infrastructure underneath it, but not more important.

But RAG is not SEO with a new name

It would be equally wrong to conclude that GEO is just SEO with a different interface. Retrieval can work at a more granular level than traditional page rankings, and a single question may trigger multiple searches across related subtopics. Different AI systems can also use different indexes, ranking methods, and retrieval approaches.

That means no single page or source necessarily “wins” the answer. A model can combine evidence from several places, rely on third-party corroboration, or retrieve your content without citing it prominently. RAG does not prove traditional SEO already solves GEO. It shows where existing SEO principles still apply, and where new measurement models are needed.

Stop asking how to “rank in AI”

Instead of asking, “How do we rank in AI?”, ask: “For which questions are we likely to be retrieved as useful evidence?” Ranking suggests a single ordered result set. Retrievability asks whether your information is relevant, clear, specific, accessible, credible, and strong enough to be selected in the first place.

Those factors will vary across systems, so there is no universal GEO ranking formula. But the strategic goal is clearer: not simply moving one URL up a few positions, but becoming a source that retrieval systems consistently consider useful for an important set of questions. That may be harder to measure, but it is probably closer to the real objective.

Content has to become useful evidence

The goal is not to “write for AI.” That risks repeating the same mistake as writing mechanically “for Google”: optimizing for visible patterns while making the underlying content worse. A better standard is whether your content is useful evidence: clear, specific, original, well-structured, and consistent.

First-party research, product details, expert insight, and clearly stated claims give retrieval systems something distinct to work with. Strong structure helps machines understand relationships between ideas, while consistency reduces ambiguity across your site and third-party sources. The goal is not to turn every page into a collection of AI-friendly snippets. It is to make sure the important information is easy to find and hard to misinterpret.

Technical SEO did not stop mattering

Retrieval also means GEO cannot sit only with content teams. Machines still have to access, crawl, render, and understand information before they can use it. For Google’s AI features, that dependency is explicit: a page must be indexed and eligible in Search before it can appear as a supporting link.

That is why technical SEO still matters. Authentication, rendering problems, weak internal linking, canonical conflicts, and unclear structured information can all make retrieval harder. A sophisticated AI visibility strategy built on unresolved technical debt is still built on unresolved technical debt. AI does not remove those problems. It gives them another place to surface.

The biggest risk is building strategy without a system model

Teams do not need deep machine-learning expertise, but they do need a basic model of what happens between a question and an answer. Without that, every visible output starts to look more meaningful than it is: one citation becomes a strategy, one missing citation becomes a penalty, and one vendor metric becomes a KPI.

SEO has seen this pattern before. We observe an output, invent a theory about the system behind it, then scale the tactic before validating the theory. RAG does not give us perfect visibility into AI search. It gives us something more useful: a better framework for asking the right questions.

Retrieval is the part GEO cannot afford to ignore

RAG does not make SEO obsolete. It helps explain why so much of SEO still matters. AI search may change the interface, retrieval process, and how information is synthesized, but before a system can use external information, it still has to find, access, and understand it.

That means the fundamentals remain familiar: content has to be accessible, relevant, credible, and worth retrieving. This is not primarily a prompt-engineering problem. It is an information infrastructure problem, and that is exactly why SEOs should be paying attention.

GEO may feel new. Retrieval is not.

The teams that understand the difference will be better equipped to build durable AI-search visibility instead of another collection of tactics designed around this month's screenshots.

👤 Operator of Interest: Eli Schwartz

Learn This:

Deep Learning: A type of machine learning using multi-layered neural networks.

One more thing: AI is only as good as its operator, and if you are reading this newsletter, you’re better than most!

Till next time,

Joe Hall

PS: Let me know what you think of this issue, or anything else here: [email protected]