AI Automation & AEO Glossary — 50+ Terms Defined

A working reference for the vocabulary that comes up when you ship LLM features, automation workflows, and content that gets cited by answer engines. Written for builders who'd rather read three sentences than three paragraphs. Updated 2026.

A

Action

The end step of a workflow that produces a side effect — sending an email, writing to a database, calling an API. In n8n and Zapier, every flow is a chain of trigger plus one or more actions; the action is where the work actually lands.

AEO (Answer Engine Optimization)

The practice of structuring content so LLM-driven answer engines (Claude, ChatGPT, Perplexity, Gemini) cite you in generated responses. AEO rewards direct definitions, structured data, comparison tables, and clear authorship over keyword density.

Agent

An LLM-powered system that uses tools (function calls, web browsing, code execution) in a loop to accomplish a goal that requires more than one inference step. An agent decides what to do next based on prior tool outputs; a chatbot just generates text replies.

Answer Engine

A search interface that returns synthesized natural-language answers instead of (or alongside) a list of links. Perplexity, ChatGPT search, and Google's AI Overview are answer engines; classic Google is a search engine.

API

An Application Programming Interface — a defined contract for two systems to exchange data. In automation, every integration is fundamentally an API call: read from this one, transform, write to that one.

B

Branching

A workflow node that splits execution down two or more paths based on a condition. Healthy automations branch early and merge late; flows that try to handle every case in one straight line become un-debuggable within months.

C

CCBot

The user-agent string used by Common Crawl, the nonprofit web archive whose dataset trains a meaningful fraction of every major LLM. Blocking CCBot removes you from future model training data — usually the wrong call for service businesses.

Chatbot

A conversational interface that exchanges text (or voice) messages with a user. Modern chatbots wrap an LLM with system prompts, tool use, and memory; older rule-based bots match keywords to canned replies.

Citation

A link or named reference inside an LLM-generated answer that attributes a claim to a source. Citations are the AEO equivalent of organic rankings: they drive clicks, brand exposure, and downstream trust.

ClaudeBot

The user-agent string Anthropic uses when crawling the web for Claude's training and search features. ClaudeBot respects robots.txt and llms.txt; allowing it is generally beneficial for AEO unless your content is paywalled.

CMS

A Content Management System — WordPress, Sanity, Contentful, Webflow, Strapi. The CMS is where editors author content; everything downstream (your site, your search index, your AEO surface) renders from what's stored there.

Condition

A boolean check inside a workflow that decides whether to branch, skip, or continue. Good automations log condition outcomes so you can audit why a record took the path it did three months later.

Cron

A scheduled-trigger syntax (originating from Unix) that runs a job at fixed intervals: every five minutes, every Monday at 9am, the first of the month at midnight. In n8n it's the Schedule Trigger; in serverless platforms it's a cron job.

CRM

A Customer Relationship Management system — HubSpot, Salesforce, Pipedrive, GoHighLevel. The CRM holds the authoritative customer record; automations either feed it (new lead capture) or read from it (personalized outreach).

D

DefinedTerm

A schema.org type used to mark up vocabulary entries in a glossary so search engines and LLMs can parse them as structured definitions. Pairing DefinedTerm with DefinedTermSet (this page) is one of the cleanest AEO patterns.

E

EEAT

Google's quality framework: Experience, Expertise, Authoritativeness, Trustworthiness. Originally an SEO ranking signal, EEAT has bled into LLM ranking heuristics — authored content by named humans with verifiable credentials outranks anonymous content.

Embeddings

Numerical vectors (usually 768 or 1536 dimensions) that represent the meaning of a piece of text in a way that lets you compute similarity by distance. Embeddings power semantic search, retrieval for RAG, and de-duplication of generated content.

ETL

Extract, Transform, Load — the classical data-pipeline pattern. Pull data from a source, reshape it, push it to a destination. Most n8n workflows are small ETL jobs even when they're called "automations."

F

Fine-tuning

Updating an LLM's weights on a domain-specific dataset so it learns a style, format, or knowledge area you can't reliably get from prompting. Useful for narrow tasks with thousands of examples; almost always the wrong first move when prompting plus RAG would suffice.

Function Calling

The pattern where an LLM emits a structured JSON object describing a tool to invoke (and arguments) instead of free text. Function calling is how chatbots cross from "generates text" to "does things in the real world."

G

GEO (Generative Engine Optimization)

A near-synonym for AEO used by some agencies to sound new. The tactics overlap heavily; the framing emphasizes optimizing for generative answers rather than answer engines specifically. Use whichever term your client uses.

GHL (GoHighLevel)

A bundled CRM, marketing automation, and white-label SaaS platform popular with agencies. Has built-in workflow automation, SMS/email/voice, and a snapshot system for cloning client setups — strong for agencies, less flexible than n8n for engineering-heavy work.

Google-Extended

A separate user-agent token Google introduced so site owners can allow Googlebot (for Search) while blocking Google's AI training crawler. Setting User-agent: Google-Extended Disallow: / removes you from Bard/Gemini training while preserving Search visibility.

GPTBot

OpenAI's user-agent for crawling sites to train and improve GPT models. Respected by robots.txt directives. Most service businesses should allow GPTBot — being in training data is upstream of being cited.

H

HowTo (schema)

A schema.org type for step-by-step instructions, with structured properties for tools, supplies, and timing. HowTo markup is one of the strongest signals LLMs use to pick a source for procedural answers.

I

Idempotency

The property that running the same operation twice produces the same result as running it once. Webhooks must be idempotent or retries will double-charge customers, send duplicate emails, and create duplicate database rows. Always pass an idempotency key.

J

JSON-LD

JSON for Linked Data — the structured-data format Google, Bing, and LLMs prefer for parsing schema.org markup. Goes in a script tag with type application/ld+json. Easier to maintain than microdata or RDFa because it's separate from your visible HTML.

K

Knowledge Graph

A structured database of entities (people, places, organizations, concepts) and the relationships between them. Google has one; LLMs build implicit ones from training data. Getting your entities into the right relationships is core AEO work.

L

LLM

Large Language Model — a neural network trained on a large text corpus to predict the next token given prior tokens. Modern LLMs (GPT-4, Claude, Gemini) add instruction tuning, RLHF, and tool use on top of that base capability.

llms.txt

A draft standard (proposed by Jeremy Howard) for a markdown index file at /llms.txt that tells LLMs which of your pages are canonical, citable, and structured for ingestion. Adoption is partial; cost to add is 30 minutes and the upside is compounding.

M

MCP (Model Context Protocol)

An open protocol introduced by Anthropic for connecting LLM clients to external tools, data sources, and services. MCP standardizes the function-calling contract across providers so a single tool server works with Claude, ChatGPT, and other compatible clients.

Microdata

An older inline format for structured data, embedded directly in HTML attributes (itemscope, itemtype, itemprop). Still parsed by Google but harder to maintain than JSON-LD; new sites should pick JSON-LD.

N

n8n

An open-source workflow automation platform with self-hosting, branching, code nodes, and a node library covering 400+ services. Pronounced "nodemation." Built around a fair-code license that allows self-hosting for free but restricts commercial resale.

O

OAuth

An authorization protocol (currently OAuth 2.0) that lets a user grant a third-party app limited access to their account without sharing their password. Most modern API integrations use OAuth; the token-refresh dance is where many automation bugs live.

OpenAPI

A specification format (formerly Swagger) for describing REST APIs in a machine-readable YAML or JSON document. Tools generate clients, docs, and validators from OpenAPI; LLMs can call an API directly given its OpenAPI spec.

Observability

The discipline of instrumenting a system so you can answer "why did it do that" from logs, metrics, and traces — without redeploying. For automations, observability means structured logs at every node and an alert when error rate exceeds a threshold.

P

PerplexityBot

The user-agent Perplexity uses for crawling source pages it cites in answers. Perplexity tends to update its index fastest of the major answer engines — sometimes within 7 days of publishing — so allowing PerplexityBot has the quickest AEO payoff.

Prompt Engineering

The practice of writing inputs to an LLM that reliably produce useful outputs. Includes role assignment, few-shot examples, output schemas, chain-of-thought scaffolding, and negative instructions. A discipline, not a hack — the difference between a flaky bot and a reliable one is mostly prompt quality.

Q

Queue

A data structure that holds pending work items so they can be processed asynchronously and in order. In n8n, queue mode uses Redis to decouple workflow scheduling from execution; in any production automation, a queue is what prevents one slow job from blocking everything.

R

RAG (Retrieval-Augmented Generation)

The pattern of fetching relevant documents from a knowledge base and passing them to an LLM as context before generation. Solves the "model doesn't know my data" problem without fine-tuning. Most production chatbots are RAG systems wearing different UI.

Rate Limiting

A cap on how many requests an API will accept per time window. Production automations must respect rate limits with exponential backoff, queue draining, and idempotent retries — otherwise you'll get IP-banned at the worst possible moment.

robots.txt

A plain-text file at /robots.txt that tells crawlers which paths and user-agents are allowed or disallowed. Honored by ethical crawlers (Googlebot, GPTBot, ClaudeBot, PerplexityBot); ignored by scrapers. The first file every LLM crawler reads.

S

Schema Markup

Structured data following the schema.org vocabulary — Product, Article, FAQPage, Organization, Person — embedded as JSON-LD or microdata. Schema markup tells search engines and LLMs what your page is about at the entity level.

Sitemap

An XML file at /sitemap.xml listing every URL on your site you want crawled, with lastmod timestamps. Sitemaps don't directly boost rankings but they make sure crawlers know what exists, especially deep pages with few internal links.

Structured Data

Any machine-readable annotation of page content following a known vocabulary (schema.org being the dominant one). Structured data is the difference between "this page is about something" and "this page is about a Product called X with price Y and rating Z."

System Prompt

The persistent instruction set prepended to every conversation with an LLM, defining role, constraints, tone, and tool-use rules. Live in version control like code, not in a Notion doc — they drift fast.

T

Tool Use

The capability for an LLM to invoke external functions (search, calculator, database query, custom API) during a conversation. Tool use plus a reasoning loop is what turns a chatbot into an agent that can complete real-world tasks.

Trigger

The starting event of a workflow — a webhook firing, a scheduled cron tick, a new row in a sheet, an inbound email. Every n8n or Zapier flow starts with exactly one trigger; everything downstream is reaction.

U

User-agent

The identifier string a crawler sends in HTTP request headers (GPTBot, ClaudeBot, PerplexityBot, Googlebot). robots.txt rules match against user-agent. Knowing the right strings is the foundation of controlling who reads your content.

V

Vector Database

A database optimized for storing and querying embeddings by similarity — Qdrant, Pinecone, Weaviate, Postgres with pgvector. The retrieval half of RAG runs here. For most projects under 1M documents, pgvector on your existing Postgres is the right answer.

W

Webhook

An HTTP POST sent from one system to another when an event happens — new order, completed payment, form submission. Webhooks are how systems push data without you polling them; they require idempotency, signature verification, and timeouts to be production-safe.

Webhook Signature

A cryptographic hash (usually HMAC-SHA256 of the body using a shared secret) sent in a header so the receiver can verify the webhook came from the expected sender. Skipping signature verification is how attackers inject fake events into your CRM.

Workflow

A defined sequence of trigger plus actions plus conditions that automates a process. In n8n, Zapier, Make, and GoHighLevel, workflow is the unit of automation. A clean workflow does one thing well; a messy workflow does seven things and breaks weekly.