GEO in a Website Redesign: The Briefing and SEO Checklist

A website redesign is the cheapest moment to build in AI visibility, and the most expensive moment to lose it. The short answer: set GEO (Generative Engine Optimization, being visible in the AI answers of ChatGPT, Perplexity and Google AI Overviews) as an explicit requirement in your website redesign briefing, alongside your requirements for design and conversion. Make sure AI crawlers can read your content, that your structure and data are machine-readable, and that you protect your existing citations during the migration with redirects and preserved crawler access. If you don’t, your agency will optimize a beautiful new site that AI models understand worse than the old one.

In this article you’ll read what belongs in the briefing, how to stop a redesign from wrecking your AI visibility, and how this connects to your broader redesign process. This is part of the wider approach to building a B2B website.

Why do you lose AI citations precisely during a redesign?

Citations in AI answers don’t sit “inside your brand” as a fixed asset. Like your SEO rankings, they are tied to specific URLs and to content that AI models once read and judged trustworthy. During a redesign, three things often change at once: the URL structure, the way content is technically loaded, and the content itself. Change that without a plan, and the models lose the trail to exactly the pages you were cited for.

On top of that comes a second risk that matters less in classic SEO. Many modern sites load their most important content only through JavaScript, in the visitor’s browser. For Google that’s usually manageable, because Googlebot executes JavaScript. For AI crawlers it’s different: large-scale analyses show that bots like GPTBot, OAI-SearchBot and ChatGPT-User read almost only the raw HTML and do not run your JavaScript. Content that appears only client-side simply doesn’t exist for those models. A redesign onto a heavy JavaScript framework can therefore make you unintentionally invisible to the engines you want to be found in.

The good news: this is fully manageable, provided you put it in the assignment up front. Fixing it afterwards is expensive and slow. That’s why GEO belongs in the briefing, not in the evaluation.

What goes into the website redesign briefing for GEO?

Set GEO as an explicit, testable requirement in the briefing, on equal footing with design and conversion. A wish (“AI-proof would be nice”) steers nothing; a requirement with an acceptance criterion does. If you don’t yet know how to structure such an assignment, use our approach to writing a strong website briefing or RFP as a starting point. Concretely, these points belong in your assignment to the agency:

• Rendering: core pages deliver their full main content in the first HTML response, via server-side rendering or static generation, not only through client-side JavaScript.
• Structure: a logical, stable URL structure and a clear heading hierarchy, so that both human and machine can follow the website architecture.
• Structured data: relevant schema markup on the right pages, so that models can unambiguously interpret entities like your company, services and authors.
• Crawler access: a robots.txt that deliberately allows the AI crawlers that earn you citations, instead of blocking them by accident.
• Migration protection: a complete redirect and URL-mapping plan for the transition, so that existing citations and links don’t dead-end.
• Answer-first content: a content model in which every core page opens with a short, citable answer to the question it addresses.

These requirements cost almost nothing during the build, because the agency makes the choices anyway. Building them in afterwards costs a second project. That’s exactly why a redesign is the right moment: you pay once for foundations that carry both your conversion and your AI visibility.

How do you make sure AI can read your content?

The most important technical requirement is that your content sits in the raw HTML before any JavaScript comes into play. So explicitly ask your agency for server-side rendering or static generation for every page you want to be found: your service pages, your knowledge articles and your most important landing pages. A handy test: open a page, turn off JavaScript in your browser, and see whether the body text is still there. If your content disappears, it also disappears for a large share of the AI engines.

This lines up nicely with other foundations of a good site. Fast-loading, server-rendered pages score better on Core Web Vitals and are more pleasant for visitors. So you don’t have to trade off GEO against user experience here: the same technical choice serves both. We are platform-agnostic and build in Webflow, WordPress or custom/headless. Which route fits depends on your team, content and growth plans, but the requirement “content in the first HTML” holds on every platform. Read more about that trade-off at our website development.

Which structure and data help AI cite you?

AI models cite sources they can understand quickly and unambiguously. Three things help, and all three are cheap to build in during a redesign.

First, a clean structure. A stable URL setup and a tidy heading hierarchy (one H1, with logical H2s framed as questions) make it easy for a model to see what a page is about and which snippet holds the answer. Second, structured data: with the right structured data you literally tell a machine what an entity is, who the author is and what you offer, without it having to infer that from running text.

Third, the writing style itself. Pages that open with a short, complete answer and only then elaborate are rewarding to cite, because the citable block sits right at the top. That’s exactly the structure you’re reading now. Lock this content model into the briefing, so that your redesign doesn’t just deliver prettier pages, but pages an AI answer can easily take over. This is the core of GEO and dovetails neatly with good conversion copy: a clear answer up front helps both the reader and the machine.

How do you keep your citations through the migration?

Treat your AI visibility during the transition just as carefully as your rankings. The most important measure is a complete 301 redirect plan: every old URL that was cited or linked points, after launch, to the corresponding new address. Without it, every new URL starts from scratch again, and existing references from AI sources dead-end. This is the same discipline as in a migration without ranking loss, now applied to your citations too.

Also watch two things that matter specifically for AI. First, your robots.txt: check that the new site doesn’t block the crawlers that earn you citations. A fresh build sometimes starts with a locked-down robots.txt from the test phase, and if that goes live with it, you shut out GPTBot, ClaudeBot, PerplexityBot and Google-Extended in one stroke. Make their access an explicit launch point on your checklist.

The short summary

A redesign determines for years whether AI engines can read and cite your brand. So set GEO as a testable requirement in the briefing: content in the first HTML via server-side rendering, a clean structure with structured data, answer-first pages, and a migration plan with 301 redirects and preserved crawler access. Those choices cost almost nothing during the build and serve your conversion and user experience at the same time. The honest nuance: GEO isn’t a switch you flip afterwards, but a foundation you lay during the build, or don’t. Whoever forgets it in the briefing pays later for a second project.

Want to set up your redesign so you win AI citations instead of losing them? Book your free intake and we’ll look together at what your site needs.