AEO, agent-readiness, and open-source foundation terms — defined

25 terms spanning AI search, schema, and foundation architecture. Each one is defined once and bound to the pillar that ships it.

Jump to a term

AI search, schema, and open-source foundation vocabulary, A to Z.

A

  • AEO

    Structuring a site so AI systems can read, trust, and cite it in answers.

  • Agent-ready website

    A site AI agents can read and act on, not just human visitors.

  • AI search

    Finding information via an AI system instead of a search results page.

  • Apache 2.0

    A permissive open-source license allowing commercial use with minimal restriction.

  • Audit CLI

    A command-line tool that scores a site's structural AEO readiness.

C

  • Citation gap

    A structural deficiency that silently prevents AI citation.

  • Citation share

    The proportion of AI answers in which a brand gets cited.

  • Content adapter

    The integration layer connecting an external CMS to AILK's schema system.

E

  • Entity markup

    Schema identifying the real-world business, person, or product behind a page.

F

  • FAQ schema

    Schema.org markup that lets AI systems extract Q&A pairs directly.

  • Foundation

    The underlying codebase and architecture a site is built on top of.

G

  • GEO

    Optimizing content to surface inside generative AI answers.

H

  • Headless CMS

    A content system that delivers content via API with no built-in front end.

J

  • JSON-LD

    The lightweight data format used to embed schema markup in a page.

L

  • Launch Service

    A fixed-scope, productized engagement to deploy a site on a given foundation.

M

  • Marginal cost of a page

    The incremental cost of adding one new page to a site.

  • MCP

    An open protocol letting AI agents call tools and read structured data.

O

  • OSS-as-marketing

    Labeling a product open-source while crippling the free tier as a funnel.

P

  • Peer surfaces

    One capability exposed identically to humans, agents, and programs.

  • Pillar topic

    A broad subject anchoring a content strategy's keyword clusters.

  • Prompt tracking

    Running fixed prompts against AI models to measure citation share over time.

S

  • Schema (markup)

    Structured code that tells search engines and AI what a page is about.

  • Scaffolder

    A CLI tool that generates a working project skeleton in one command.

  • Starter

    A pre-built project template with common infrastructure already wired.

  • Structured data

    Any content organized in a standardized, machine-readable format.

Answer Engine Optimization

AEO

AEO is the practice of structuring a website so AI systems like ChatGPT and Perplexity can read, trust, and cite its pages when answering a question.

Also known as
Answer Engine Optimization

Generative Engine Optimization

GEO

GEO is the practice of optimizing content so generative AI models surface it inside synthesized answers rather than a list of links.

Also known as
Generative Engine Optimization

AI search

AI search means using an AI system — ChatGPT, Perplexity, Google AI Overviews — to find information instead of scanning a traditional results page.

Agent-ready website

An agent-ready website lets AI agents — not just human visitors — read its content and act on it, typically through a machine-callable interface like an MCP server or API.

Schema (markup)

Schema markup is structured code embedded in a page's HTML — typically JSON-LD — that tells search engines and AI systems exactly what the page is about, using a shared schema.org vocabulary.

JSON-LD

JSON-LD is a lightweight data format used to embed schema markup in a webpage — a script tag search engines and AI crawlers parse directly, without touching the visible HTML.

Entity markup

Entity markup is schema — using types like Organization, Person, or LocalBusiness — that identifies a specific real-world business or person, so AI systems attribute a page's claims correctly.

FAQ schema

FAQ schema is the schema.org FAQPage type. It marks up question-and-answer content, letting search engines and AI systems extract and quote individual answers directly.

Model Context Protocol

MCP

MCP is an open standard, introduced by Anthropic, that lets AI agents call tools and read structured data from an application — the same way a person uses a web interface.

Also known as
Model Context Protocol

Peer surfaces

Peer surfaces is AILK's term for an architecture where one capability is exposed identically to a human via web UI, an agent via MCP, and a program via HTTP API — with CI-enforced parity across all three.

Citation share

Citation share is the proportion of AI-generated answers, within a topic or prompt set, in which a specific brand gets cited or recommended.

Headless CMS

A headless CMS stores and delivers content through an API, with no built-in front-end templating — the presentation layer is built separately.

Content adapter

A content adapter is the integration layer connecting a headless CMS or external content source to AILK's page-rendering and schema system, so content authored elsewhere still emits correct JSON-LD.

Scaffolder

A scaffolder is a command-line tool that generates a working project skeleton — file structure, configuration, boilerplate — from a single command instead of an empty directory.

Audit CLI

An audit CLI scores a website's structural readiness — schema completeness, entity markup, AEO gaps — and reports the result as pass/fail output usable in a CI pipeline.

Pillar topic

A pillar topic is a broad subject that anchors a content strategy — narrower cluster topics organize around it to build topical authority with search engines and AI systems.

Prompt tracking

Prompt tracking runs a fixed set of representative user prompts against AI models on a recurring basis, recording which brands or sources get cited in the answers.

Citation gap

A citation gap is a structural or content deficiency — missing schema, ambiguous entity markup, a page that doesn't emit JSON-LD — that keeps a brand from being cited even when its content is relevant.

Structured data

Structured data is the broader category: any content organized in a standardized, machine-readable format. Schema markup — usually delivered as JSON-LD — is the specific version search engines and AI systems parse most often.

Apache 2.0

Apache 2.0 is a permissive open-source software license that lets anyone use, modify, and distribute code — including in proprietary commercial products — with minimal restrictions.

OSS-as-marketing

OSS-as-marketing describes labeling a product open-source while structurally crippling the free tier, so it functions as a lead-generation funnel rather than usable software.

Launch Service

A Launch Service is a productized, fixed-scope engagement in which a vendor deploys a customer's website on a given foundation within a defined timeline, rather than an open-ended custom build.

Foundation

A website foundation is the underlying codebase, architecture, and structural conventions a site is built on — distinct from its content, design, or hosting.

Starter

A starter, in web development, is a pre-built project template that gives a developer a working codebase with common infrastructure already wired, instead of an empty repository.

Marginal cost of a page

The marginal cost of a page is the incremental time, money, or effort to add one new page to an existing site, holding the foundation constant — the cost AILK's agent-assisted scaffolding drives toward zero.

Frequently asked questions about AEO and agent-ready terminology

How is this glossary different from AILK's blog content?

This glossary gives the atomic, one-sentence definition of a term on its own. The blog content walks through why each term matters and how AILK's architecture implements it — check a term fast here, read the pillar posts for the argument behind it.

Are these definitions AILK-specific or industry-standard?

Most terms — AEO, GEO, MCP, JSON-LD — are industry-standard, defined the way the broader AEO and developer communities use them. A few, like peer surfaces and marginal cost of a page, are terms AILK uses to name a specific part of its own architecture, and are marked as such.

Will new terms be added to this glossary over time?

Yes. New terms get added as AILK's topical authority clusters expand across the three pillars, and as AEO and agent-readiness vocabulary evolves. Each addition binds to a pillar cluster the same way the current set does.

Can I cite or link to a definition on this page directly?

Each term has its own anchor link (for example, /glossary#mcp), so a specific definition can be linked or quoted on its own without needing the rest of the page for context.

See these terms shipped, not just defined.