Glossary

The language of code-first websites

How websites get built, rendered, and deployed now, the formats and Git behind them, how they get found in search and AI answers, and what it takes to run them after launch.

Client-side rendering (CSR) sends a mostly empty HTML page plus JavaScript, and the browser builds the page content after the JavaScript runs.

A dynamic website generates pages on a server when they are requested, often from a database, so content can differ per visitor or change instantly.

Edge rendering runs server-side rendering on servers distributed close to visitors, such as CDN edge locations, instead of in one central region.

Hydration is the step where JavaScript attaches to server-rendered or pre-rendered HTML in the browser, making the page interactive.

Incremental static regeneration (ISR) serves statically generated pages but rebuilds individual pages in the background after a set time or on demand.

Islands architecture renders a page as static HTML and hydrates only small, independent interactive components, called islands.

Server-side rendering (SSR) builds a page’s HTML on the server for each request, so the visitor receives a fully rendered page with fresh data.

SSG renders pages once at build time and serves the same files to everyone; SSR renders each page on the server per request, trading speed and cost for fresh, request-specific data.

Static site generation (SSG) renders pages to HTML at build time, so the server only has to send pre-built files when someone visits.

A static site generator is a framework such as Astro, Hugo, or Eleventy that builds a website into HTML files ahead of time, usually from templates and Markdown content.

A static website serves pre-built pages that are the same for everyone; a dynamic website builds pages on a server per request, so they can change per visitor or instantly.

A static website serves pre-built HTML files that are the same for every visitor, instead of generating pages on a server for each request.

AEO (answer engine optimization) is making content easy for AI answer engines like ChatGPT, Perplexity, Claude, and Google’s AI Overviews to find, understand, and quote.

An answer engine is a search tool that responds with a written answer, usually generated by AI from several sources, instead of a list of links.

A canonical URL is the preferred address for a page, declared with a link rel="canonical" tag, so search engines consolidate duplicate versions into one.

GEO (generative engine optimization) is improving how often and how accurately generative AI systems mention and describe your brand or content in their answers.

Google Search Console is Google’s free tool for site owners to see how their site performs in Google Search and fix indexing problems.

Internal links are links between pages on the same website, which help readers and crawlers find related content and understand which pages matter most.

llms.txt is a proposed convention for a Markdown file at a website’s root that gives AI systems a concise overview of the site and links to its most useful content.

A meta description is a short summary of a page in its HTML head that search engines may show under the title in results.

robots.txt is a text file at the root of a website that tells crawlers which paths they may or may not crawl.

SEO (search engine optimization) is the work of making a website’s pages easy for search engines to crawl, understand, and rank for the searches its audience makes.

A sitemap is a file, usually sitemap.xml, that lists a website’s pages so search engines can discover and crawl them.

Structured data is machine-readable information about a page, usually written as JSON-LD using schema.org types, that tells search and answer engines what the page describes.