CMS & content-platform terms, in plain language

A 2026 framing for judging whether a CMS can take part in automated, AI-driven workflows, measured across API coverage, MCP support, workflow automation, auditability, permissions for non-human actors, and content structure. The term is new and its meaning varies by vendor.

Automated bots run by AI companies that fetch web pages, either to help answer a user's question in real time or to gather text for training future models. GPTBot, ClaudeBot, PerplexityBot, and Google-Extended are examples.

The full cost of running a CMS over its life: licences and seats, hosting and infrastructure, development, content operations, and the cost of eventually leaving it.

An approach to building a system from independent best-of-breed parts, each chosen for its job and connected over APIs, rather than adopting one suite that does everything.

The blueprint that defines the types of content a system holds, the fields each type has, and how they relate to one another. It is the structure your content is stored in.

The people, process and tooling that produce and govern an organisation's content at scale: who writes, who reviews, who approves, how consistency holds across many contributors, and how work moves through translation to publication.

A system that treats content as structured, reusable data an organisation owns and publishes to many destinations, rather than a single website tied to one set of templates.

A suite that bundles content management with adjacent marketing tools, personalisation, analytics, campaigns, commerce, assets and customer data, into one integrated product. Adobe Experience Manager, Sitecore, Optimizely and Acquia are examples.

Two acronyms for the same broad practice of preparing content so AI systems quote and cite it inside a generated answer. GEO stands for Generative Engine Optimization, AEO for Answer Engine Optimization. The terms arrived by different routes and are used interchangeably today.

A content management system that stores and edits content and delivers it over an API, leaving the rendering of pages to a separate front-end application your team builds and runs.

The difference between a CMS that renders your pages for you and one that manages content and delivers it over an API for a separate front end to render.

A plain-text file a website can publish to point AI systems at the content it considers most useful. It is a readable map, not a rule that is enforced, and it is an emerging convention rather than a settled standard.

An acronym for microservices-based, API-first, cloud-native SaaS and headless: a set of principles for building systems from independent, swappable parts connected over APIs.

A single content platform that serves many separate sites or brands, called tenants, from one shared installation, with each tenant's content and permissions kept apart.

Moving a website's content estate from one content management system to another, together with the content model, templates, integrations and URLs that change with it. The word names different work in cloud migration and in ecommerce.

The choice between running a CMS on infrastructure you control and using one delivered as a managed service by a vendor. It decides who patches, who scales, who owns uptime, and where your data lives.

Content stored as separate, typed fields with defined meaning, rather than as text painted into a finished page. The structure is what lets software reliably find and reuse each piece.

The set of costs and obstacles that make leaving a supplier hard once you have adopted it. It takes several forms, from where your data lives to which skills your team has invested in.