Engineering & Growth Glossary

The engineering and content practice of structuring web pages to be accurately parsed, extracted, and cited by conversational AI engines like ChatGPT, Perplexity, Gemini, and Google AI Overviews.

Unlike traditional SEO which focuses on 10 blue link keyword rankings, GEO focuses on entity graphs, citation density, structured JSON-LD data, sub-100ms server responses, and explicit factual answer blocks that LLM RAG pipelines require.

The optimization of content to win direct-answer features, such as Google Featured Snippets, Voice Search responses, and People Also Ask (PAA) blocks.

AEO relies on placing 40–60 word concise, definitive summary blocks directly beneath interrogative H2 headings, paired with FAQPage schema markup for automated machine extraction.

A decoupled content management system where the backend repository is separated from the frontend presentation layer.

In a headless architecture, content is created in a CMS (such as WordPress or Sanity) and served purely via REST or GraphQL APIs to a high-speed frontend framework like Next.js running at the CDN edge.

The practice of capturing analytics and ad conversion data on a secure cloud server before relaying it to advertising platforms.

Moving conversion tracking from the user's browser to a dedicated Server-Side Google Tag Manager container bypasses ad-blockers, overcomes Apple Safari ITP cookie deletion windows, and restores up to 30% of lost conversion attribution.

A direct server-to-server connection that sends marketing events (purchases, leads, appointments) from your web server directly to Meta or Google Ads.

CAPI operates in tandem with or in replacement of client-side browser pixels, delivering higher Event Quality Match scores and enabling automated ad bidding algorithms to optimize for actual revenue outcomes.

A Next.js rendering feature that allows developers to update static pages in the background without rebuilding the entire website.

ISR pairs the sub-millisecond delivery speed of static HTML with the live freshness of server-rendered pages by revalidating cache tags on-demand when editors publish new content in the headless CMS.

A set of standardized user experience metrics established by Google to evaluate page load speed, responsiveness, and visual stability.

Comprises Largest Contentful Paint (LCP < 2.5s), Interaction to Next Paint (INP < 200ms), and Cumulative Layout Shift (CLS < 0.1). Passing CWV is a confirmed ranking signal and direct driver of conversion velocity.

A Core Web Vital metric assessing a page's overall responsiveness to user interactions (clicks, taps, keystrokes).

INP replaced First Input Delay (FID). It measures the latency between user input and the browser's subsequent visual update, heavily penalizing heavy client-side JavaScript execution.

An emerging web standard served at /llms.txt that provides structured, markdown-formatted context for LLMs to ingest a domain's core resources.

Similar to robots.txt for traditional search bots, llms.txt provides concise entity summaries, service documentation, and clean links optimized for AI crawlers without requiring HTML rendering.