Run your website with AI. Speak the language first.

AEO is the practice of making a website easy for AI assistants and answer engines to read, trust, and cite.

It overlaps with SEO but focuses on clear answers, structured data, and pages an assistant can quote without the rest of the site. No platform guarantees AI visibility; AEO improves the signals.

An agent-ready stack is a website setup an AI coding agent can safely change: code in a repository, reusable components, and a preview for every change.

Typical examples are Astro or Next.js sites hosted on Cloudflare, Netlify, or Vercel.

Agentic commerce is shopping with the help of AI assistants that research, compare, and on some channels buy on a shopper’s behalf.

For a store, the question is whether assistants understand its products, prices, and policies well enough to recommend them.

An AI-native website keeps its code and content in a repository your own AI agent can change directly, with your team previewing and approving each change before it goes live.

Updates start as plain-language requests instead of tickets or editor sessions.

AI website governance is the set of controls that lets AI agents change a production website safely: previews, approvals, attribution, and a way to restore.

It carries forward the safeguards a traditional CMS provided, for work an agent produces.

An AI website migration moves an existing site onto an agent-ready stack while preserving its design, content, and URLs where possible.

ZINC’s version comes with control built in: Dispatch is configured as part of the move, not bolted on after.

Bring your own agent means your team chooses the AI coding agent, such as Claude Code, Codex, or Gemini, and the governance layer works around it.

Dispatch does not lock a team into one model or one host.

Dispatch is ZINC’s governance platform: the management layer for AI-powered websites.

Your agent builds each change on its own branch; your team previews it and approves it by role and risk; every change is attributed, and supported changes can be restored with one click. Turn Dispatch off and the website keeps running.

A headless CMS stores content in structured fields and delivers it to a website, app, or other channel through an API, without controlling how it looks.

It can sit alongside an AI agent when editors want forms and fields.

llms.txt is a plain-text file at a site’s root that gives AI assistants a short, curated map of the site’s most important pages.

It complements, but does not replace, the sitemap and structured data.

MCP is an open protocol that lets AI assistants connect to tools and data sources, such as a CMS, a CRM, or a website platform, through a standard interface.

Some website platforms, including Webflow, offer MCP connections so agents can work on a site.

One-click restore returns a website to the version before a published change, without rebuilding the work from memory.

It covers the site’s code and deployment. Submitted forms, sent emails, and changes in external systems are handled by the systems that received them.

Preview before release means every proposed change is published to a private preview address for review before it can reach the live site.

Reviewers see the change in context, on the real design, and approve it or send it back.

A redirect map lists every URL that changes address in a migration and the new address it permanently (301) points to.

It is the first deliverable that protects search traffic, because a broken URL loses the signals it earned.

A risk tier is a rule that decides how much review a change needs: a copy fix might need one approver, a navigation or pricing change two.

Roles and risk tiers keep speed from outrunning judgment.

SEO parity means the new site carries over every title, description, heading, canonical tag, and piece of structured data from the old one before anything is improved.

Parity first makes a migration measurable: if traffic moves, there is one cause to look at, not ten.

A URL inventory is a complete list of a site’s live pages, grouped by template, with a planned destination for each before a migration starts.

Our own site had 49 live URLs across six templates.

Webflow Enterprise is Webflow’s plan for large organizations, with visual editing, a structured CMS, and enterprise hosting, security, and support.

It suits marketing teams that edit visually every day. ZINC designs, builds, and supports Webflow Enterprise sites.