Reference · adhere to these definitions in every lesson

Glossary

Shared vocabulary for SEO, AEO, and the automation built on top of them. Tags: SEO classic search · AEO AI answer engines · BOTH

The fields

SEO — Search Engine Optimization SEO: Making a site rank higher in classic search results pages (the "ten blue links"). Optimizes for the crawl → index → rank → serve pipeline.
AEO — Answer Engine Optimization AEO: Making your content the source an AI answer engine cites when it generates a reply (ChatGPT, Claude, Perplexity, Google AI Overviews). Sometimes called GEO.
GEO — Generative Engine Optimization AEO: Academic name for AEO, from the GEO research paper. Same goal: visibility inside generated answers, not just ranked links.

The classic pipeline

Crawling SEO: A bot (e.g. Googlebot) fetches your pages by following links and reading your sitemap.xml. Gated by robots.txt.
Indexing SEO: The engine parses a crawled page, renders it, and stores it in a giant searchable database. A page that isn't indexed can never rank.
Rendering (two-wave / deferred) BOTH: Google processes JS pages in phases: it crawls the raw HTML first, then — in a separate, deferred queue, once resources allow — a headless Chrome runs the JavaScript and re-indexes what it produced. Content that only exists after JS is indexed late, or never by bots that don't render.
CSR vs SSR / SSG BOTH: Client-side rendering (CSR): the server sends an empty shell (<div id="root">) and JS builds the page in the browser — invisible to no-JS bots. Server-side rendering (SSR) / static site generation (SSG): the content is in the first HTML response, seen by every bot immediately. For SEO/AEO, get facts into the server's HTML.
Ranking SEO: For a given query, the engine orders indexed pages by hundreds of signals (relevance, links, quality, freshness). Decides position.
Serving / SERP SEO: The Search Engine Results Page actually shown to the user — links, plus features like snippets, knowledge panels, and AI Overviews.

The answer-engine pipeline

Retrieval AEO: The answer engine pulls candidate passages — usually from the same crawled/indexed web (often via a live search) — to ground its answer. This is why indexing still matters for AEO.
Synthesis / Generation AEO: The LLM writes a single composed answer from the retrieved passages plus its training knowledge.
Citation AEO: The link/attribution the engine shows next to (or behind) its answer. Being the cited source is the AEO win — the equivalent of a #1 rank.
Passage / chunk AEO: The retrieval unit. Engines split pages into smaller passages, embed them, and pull the few most relevant — so the thing that gets cited is a self-contained chunk, not the whole page. Write each section to stand alone.
Answer-first (inverted pyramid) AEO: Lead with the direct answer in 1–2 sentences, then expand with detail. Makes the opening a quotable, self-contained chunk an engine can lift verbatim. Borrowed from journalism's inverted pyramid.

Quality & trust

E-E-A-T BOTH: Experience, Expertise, Authoritativeness, Trust — Google's framework for "is this content trustworthy?", used by quality raters. Trust is the centre; the others feed it. Not a direct ranking factor and not a score — Google approximates it with "a mix of factors." For builders: audit the machine-detectable proxies (author + sameAs, dates, publisher, outbound sourcing, about/contact).
YMYL — Your Money or Your Life SEO: Topics that could significantly affect health, financial stability, safety, or societal well-being. Held to a far higher E-E-A-T bar — trust signals matter most here, and faking them is risky.
sameAs BOTH: A schema.org property linking an entity (a Person author, an Organization) to its authoritative profiles elsewhere (LinkedIn, Wikipedia, ORCID). The machine-readable way to assert who an author is — an Authoritativeness signal.

Builder-facing artifacts

Structured data BOTH: Machine-readable markup (usually schema.org JSON-LD) embedded in a page that tells engines exactly what an entity is. Powers rich results and helps machines extract facts.
JSON-LD BOTH: Google's recommended structured-data format: a <script type="application/ld+json"> block of JSON, kept separate from visible HTML. Each type has required properties (miss one → no rich result) and recommended ones.
Rich result SEO: An enhanced SERP listing — star ratings, prices, FAQ accordions — earned by valid structured data. Takes more space, draws more clicks than a plain blue link.
robots.txt BOTH: A file at your site root that tells crawlers which paths they may or may not fetch. First thing a crawler reads.
sitemap.xml BOTH: A machine-readable list of your URLs (with metadata) that helps crawlers discover pages efficiently. Passive: engines pull it on their own schedule. Spec limits: ≤50,000 URLs and ≤50 MB per file; <loc> required, <lastmod> optional (W3C date); all URLs on one host. Past 50k URLs, use a sitemap index (a sitemap of sitemaps).
IndexNow BOTH: An open protocol to actively push changed URLs to engines: POST {host, key, keyLocation, urlList} (≤10,000 URLs/post), and the ping is shared across all participants. Supported by Bing, Yandex, Naver, Seznam — not Google, which sticks to sitemaps + its own crawl scheduling. The key (8–128 chars) lives in a file at your root to prove host ownership.
noindex SEO: A directive telling the engine to drop a page from the index. Lives in <meta name="robots"> or the X-Robots-Tag header. Only works if the page is crawlable — a blocked page's noindex is never read.
X-Robots-Tag SEO: An HTTP response header that carries indexing directives (like noindex) — the header-level equivalent of the robots meta tag. Useful for non-HTML files (PDFs, images).
Canonical BOTH: Via <link rel="canonical">: declares which URL is the "real" one when several show near-identical content, so the engine consolidates signals onto one.
Search Console (API) SEO: Google's first-party feed for your site: impressions, clicks, average position, and the queries that surfaced you — from Google's own logs. The searchanalytics.query endpoint makes it pollable. The Web search type now includes AI-feature traffic.
Share of voice AEO: Your slice of all citations across a prompt set: your citations ÷ everyone's citations. The headline AEO metric — but a proxy, since the prompt set is sampled, not the engine's real traffic. Pair with coverage (% of prompts that cite you at all).