Lesson 0001 · Foundations

The Two Pipelines

Before any tactic makes sense, you need the machine it feeds. There are two of them.

You’re a developer building marketing automation. So skip the tips-and-tricks framing. The only durable model is this: your content flows through a pipeline of distinct stages, and every SEO/AEO tactic is just an intervention at one stage. Master the stages and every tactic finds its slot.

Your win for this lesson: given any SEO or AEO tactic, you can name which pipeline and which stage it targets — and therefore what your tooling must produce for it.

Pipeline 1 — Classic search

This is what “SEO” has always meant. Google (or Bing) runs four stages, in order. A page that fails an early stage never reaches the later ones — you cannot rank a page that was never indexed, and you cannot index a page that was never crawled.^[1]

Classic search · SEO

Crawl bot fetches your pages

→

Index parse + store in the database

→

Rank order pages for a query

→

Serve render the results page

Pipeline 2 — AI answer engines

This is “AEO” (a.k.a. GEO). ChatGPT, Claude, Perplexity, and Google’s AI Overviews don’t hand you ten links — they compose one answer and cite a few sources. The stages are different: retrieve candidate passages, synthesize an answer, cite the sources used.^[2]

AI answer engine · AEO / GEO

Retrieve pull passages, often via live search

→

Synthesize LLM writes one answer

→

Cite attribute the sources used

▲ Retrieval usually reads from the same crawled & indexed web as Pipeline 1.

The key connection: AEO does not replace SEO — it sits on top of it. Most answer engines retrieve from the indexed web (frequently by running a search query under the hood). So being crawlable and indexable is table stakes for both. AEO then adds a new question: once retrieved, is your page easy to extract a clean, quotable, citable fact from?

Why a builder cares: each stage is a thing your software touches

The reason this model is worth memorizing: every stage maps to a concrete artifact your automation will read or write.

Stage	What your tooling does here
Crawl	Generate/validate `robots.txt` & `sitemap.xml`; check pages return 200 and aren’t blocked.
Index	Render pages headless; verify titles, canonicals, and that content is in the HTML, not hidden behind JS.
Rank	Audit content depth, internal links, page speed; track keyword positions via an API.
Serve	Emit `schema.org` structured data so you win rich results & snippets.
Retrieve	Make facts extractable: clear headings, self-contained sentences, structured data.
Cite	Track which AI engines cite you, for which prompts, over time.

Future lessons drill into one cell at a time. Today you only need the map.

Retrieval practice · no peeking

Place the tactic on the pipeline

Answer from memory — that effort is what makes it stick. One try each; pick before you read the others.

Question 1 / 4

In classic search, which stage decides the order results appear in?

Question 2 / 4

An AI answer engine mostly draws its answer from…

Question 3 / 4

For AEO, why does getting indexed still matter?

Question 4 / 4

Your tool validates robots.txt and sitemap.xml. Which stage is it serving?

Primary source — read this next (≈15 min)

“In-depth guide to how Google Search works” — Google Search Central

The crawl → index → serve pipeline straight from the engine's own docs. The highest-trust source there is for Pipeline 1.

Stuck or curious? This agent is your teacher. Ask it anything — “show me a real robots.txt”, “do Claude and Perplexity retrieve differently?” — followups are the fastest way to learn.