Skip to content
Greeto

Glossary · Plain-language definitions

The language of AI-era websites.

Plain-language definitions of the terms behind AI-era web development, Next.js, technical SEO, AI search (AEO/GEO), and web performance — by Greeto Studio.

AEO/GEO

AI web development

Agentic workflow

An agentic workflow is a multi-step process where one or more AI agents plan, act, use tools, and check their own results in a loop — often split across specialized subagents — to complete a larger task.

Read definition →

AI agent

An AI agent is a system built on a large language model that pursues a goal across multiple steps — deciding actions, using tools, and reacting to results — rather than answering a single prompt in one shot.

Read definition →

AI-assisted web development

AI-assisted web development is building and maintaining websites with AI agents doing the heavy lifting under human direction — generating, editing, and testing real code — rather than a developer typing every line or a no-code tool producing a fixed template.

Read definition →

Claude Code

Claude Code is Anthropic's terminal-based AI coding agent: it reads your repository, runs commands, edits files, and verifies its own work in a loop — acting on a real codebase rather than handing you snippets to paste.

Read definition →

Coding agent

A coding agent is an AI system that performs software tasks end to end — reading code, running commands, editing files, and checking results in a loop — instead of only suggesting code for a human to copy.

Read definition →

Context window

A context window is the amount of text — measured in tokens — a large language model can consider at once. Everything the model 'sees' for a task, including instructions, code, and history, must fit inside it.

Read definition →

Human-in-the-loop

Human-in-the-loop is a workflow where a person reviews and approves an AI system's output before it takes effect, keeping a human accountable for every consequential decision the AI proposes.

Read definition →

Model Context Protocol (MCP)

The Model Context Protocol (MCP) is an open standard that lets AI agents connect to external tools and data sources — like analytics, a database, or a browser — through a consistent interface, so the model reasons over real data instead of guesses.

Read definition →

Spec-driven development

Spec-driven development is an AI coding practice where you write and approve a short specification before any code is generated, so the artifact you review is the plan — not a large diff after the fact.

Read definition →

Vibe coding

Vibe coding is building software by prompting an AI in a loose, conversational way and accepting what it produces without a written spec — fast for prototypes, risky for production code you have to maintain.

Read definition →

Migration

301 redirect

A 301 redirect is a server response that permanently sends a browser and search engines from an old URL to a new one. It passes nearly all ranking signals and is the standard way to move content without losing SEO.

Read definition →

Canonical URL

A canonical URL is the version of a page you tell search engines is the 'real' one when several URLs show the same or near-identical content, so ranking signals point to one address instead of being split.

Read definition →

Crawl budget

Crawl budget is the number of pages a search engine like Google will crawl on your site within a given window. It is set by how fast your server responds and how much the crawler wants your URLs.

Read definition →

DNS cutover

DNS cutover is the moment you change a domain's DNS records to point traffic from an old server to a new one. It's the final switch that makes a migration go live.

Read definition →

Index bloat

Index bloat is when a search engine indexes far more pages from your site than have real value — thin, duplicate, or low-quality URLs — which dilutes crawl attention and weakens how the site ranks overall.

Read definition →

Redirect map

A redirect map is a spreadsheet or file that pairs every old URL with its new destination, so a site migration sends each old page and its SEO value to the right new page.

Read definition →

WordPress to Next.js migration

WordPress to Next.js migration is the process of moving a site off WordPress and rebuilding it in Next.js, while preserving URLs, content, and search rankings through 301 redirects and matching metadata.

Read definition →

Next.js & technical SEO

App Router

The App Router is Next.js's routing system built on React Server Components, where folders in an app directory define URLs and pages render on the server by default, streaming HTML for fast, SEO-friendly results.

Read definition →

Incremental Static Regeneration (ISR)

Incremental Static Regeneration (ISR) is a Next.js feature that rebuilds individual static pages in the background after deploy, on a timer or on demand, so a site stays fast and cached while specific pages refresh without a full rebuild.

Read definition →

Next.js

Next.js is a React framework for building production websites and apps. It adds routing, server-side and static rendering, and build tooling on top of React, so pages can be fast, SEO-friendly, and deployed as one project.

Read definition →

Server-side rendering (SSR)

Server-side rendering (SSR) is when a web server builds the full HTML for a page on each request and sends it ready-to-read, so users and crawlers get content without waiting for client-side JavaScript.

Read definition →

Static site generation (SSG)

Static site generation (SSG) builds every page into a finished HTML file at deploy time, so the server sends pre-made files instead of rendering on each request. It makes pages load fast and stay cheap to serve.

Read definition →

Static vs dynamic rendering

Static rendering builds a page's HTML once at deploy or build time and serves the same cached file to everyone; dynamic rendering builds HTML on the server per request, so each response can differ by user or time.

Read definition →

Performance