Redesigning your website? How to keep the AI citations you already have

What happens to your AI citations when page addresses change?

An AI answer that cites your page points to an address. When a redesign changes that address, the citation survives only if the old URL leads in one step to a page that still states the same fact. If it lands on an error page or a generic page, the engine needs another source. That source may belong to a competitor.

Engines that search fetch pages while they build an answer, so they meet your redirects directly. Ahrefs, which sells AI visibility tools, tracked 66.6 million free, logged-out ChatGPT responses in August and September 2026 and found that 14.4% triggered a web search.¹ Google says a page only needs to be indexed and eligible for a snippet to appear as a supporting link in AI Overviews or AI Mode.² Either way, the engine works from addresses it already holds and pages it can still fetch.

What a cited URL needs to survive a move

1. Answer cites the old URL
2. Engine fetches the old URL
3. One permanent redirect
4. New page states the same fact
5. Citation holds

Prior work, and what this method adds

Site migrations are well documented for search. Google's guide to site moves with URL changes covers URL mapping, redirects, sitemaps and the Change of Address tool, and we follow it below.³ Search agencies publish detailed migration checklists too. This piece adds the AI answer layer: a log of the URLs engines cite today, a rule for where each one should go, and a test after launch on the same prompts.

A disclosure first. Sigzen AI sells AI visibility audits and sprints at published prices, so weigh our view with that in mind. Several of the studies cited here also come from companies that sell tools in this category.

Why a redesign puts citations at risk

A redesign rarely sets out to change content, but it usually does. Templates change, sections merge, old posts are dropped and the CMS assigns new addresses. Each change can break the link between a buyer's prompt and the passage an engine used to quote. Five failures cause most of the damage.

• Old URLs return errors. Pages are deleted or moved without a redirect, so an engine that fetches the cited address gets a 404.
• Redirects go to the homepage. Many old URLs are sent to one page that answers none of the questions they used to answer.
• Facts change shape. A price table becomes an image, a feature list moves into tabs that scripts load later, or a key paragraph is cut for layout.
• Redirect chains. The old URL points to an interim address, which redirects again, adding delay at every hop.
• Crawlers are blocked. A new CDN or bot setting refuses the crawlers that fetch pages for answers.

Google's site move guide addresses two of these directly. It asks for each old URL to redirect straight to its final destination, and it advises against sending many old URLs to one irrelevant page, such as the new home page.³

Step 1: log the URLs AI answers cite today

Before anyone touches a template, record which of your URLs AI answers cite for the prompts that matter. This log is your baseline. Without it, you cannot tell after launch whether your citations held. For a mid-sized site it takes a day or two.

Start from a fixed prompt set: the questions buyers ask when your company is a fair answer, with their constraints attached. Our guide to building a prompt set covers where those questions come from. Run each prompt several times on each engine you track, because answers vary between runs, and record every URL each answer cites.

Then add the pages that already receive AI referrals. Analytics can show which landing pages visitors from ChatGPT, Gemini or Copilot reach, and our note on AI referrals in analytics covers the traps. Together, the two lists show the URLs engines quote and the URLs buyers click.

Normalise the URLs before you compare them. Strip tracking parameters, fragments and trailing slashes, and resolve redirects that already exist, so one page does not appear under three addresses. Keep the raw form too, because a broken or invented address in an answer is itself a finding.

What the log should hold

• The cited URL, exactly as the answer gave it, including any parameters.
• The prompt, engine, run and date that produced it.
• The fact or passage the answer took from the page, in one sentence.
• Whether the answer named your company, and whether the fact was right.

Our view: the "fact taken" column is the one teams skip and later need most. A redirect can keep an address alive, but only the destination's copy decides whether the engine can still quote the same fact.

Which pages should you protect first?

Protect the pages that carry facts buyers check: pricing, core service or product pages, documentation and comparison pages. Engines look for official sources when a question is factual, so these pages are the most likely to be cited and the most costly to break.

Company pages matter more in AI answers than many teams assume. Profound, which sells an AI visibility platform, counted 11.84 billion citations on eight engines from 16 April to 16 July 2026, and about 57% pointed to company-owned websites.⁴ That share covers every company's site. A page you lose in a migration is a slot a rival's page can fill.

AI traffic is small next to search, which is why it often gets no line in a migration plan. SE Ranking found that AI platforms sent 0.32% of all visits across 101,574 websites in 250 countries and territories in January to April 2026.⁵ Similarweb counted an average of 770.7 million AI referral visits a month worldwide between June 2025 and May 2026.⁶ The share is small, but the audience is large, and it lands on the pages answers send it to.

AI answers in 2026

A small share of visits, sent to pages engines trust

57%of citations on eight engines pointed to company-owned websitesProfound, Apr–Jul 2026

0.32%of website visits came from AI platforms, 101,574 sitesSE Ranking, Jan–Apr 2026

770.7MAI referral visits a month, worldwideSimilarweb, Jun 2025–May 2026

Our view: rank pages for protection by the facts they carry, not by their traffic. A pricing page with modest visits that engines cite often deserves more care than a popular blog post they never quote.

Step 2: map every cited URL to a page with the same facts

Every URL in the log needs a destination that states the same facts in text, reached through one permanent redirect. Build the map as a table before development starts. A cited URL with no matching destination is a content gap to fill, not a redirect to improvise.

Google treats a permanent redirect as a signal that the target should be canonical, and a temporary redirect as no such signal.⁷ Its site move guide asks for server-side permanent redirects, sent straight to the final address and kept for as long as possible, generally at least one year.³

Illustrative: a citation map for a fictional freight forwarder's redesign.

Where an old cited URL should point

Redirect to the homepage

• Answers none of the old prompts
• Engine must find a new source
• Buyer lands without the fact
• Google advises against it

Redirect to the matching page

• Same fact, stated in text
• One permanent hop
• Citation can carry over
• Buyer lands on the answer

Some pages have no real successor. Our view: if a page is retired for good and nothing replaces its facts, let it return a 404 or 410 rather than redirecting it somewhere unrelated. A clear "gone" is more honest to engines and buyers than a page that pretends to answer.

Step 3: launch without changing two things at once

Ship new URLs and new copy in separate releases where you can. If addresses, templates and wording all change on one day, a fall in citations afterwards cannot be traced to any one of them. You will not know what to undo.

The safer order is to move first and rewrite later. Launch the new design and URLs with cited facts carried over word for word, check that citations hold, then rewrite pages one at a time. Our section-by-section rewrite method covers that second stage and how to test it.

Launch-day checks

• Every URL in the citation map returns a single 301 or 308 to its destination, with no chains.
• Each new page carries a self-referencing canonical tag, and internal links use the new addresses.³
• A new sitemap lists the new URLs with real last-modified dates.
• Key facts sit in the HTML the server sends, not only in images, scripts or PDFs. Google's guidance for its AI features asks for important content in textual form.²
• Changed, redirected and deleted URLs go through IndexNow. Its FAQ asks for redirected URLs and pages returning 404 or 410 to be submitted, and Google is not among the engines it lists.⁸

Test the map on a staging copy before launch. Request every old URL in the log, check that each returns one permanent redirect, and confirm that the destination still contains the fact recorded against it.

If the domain changes as well as the paths, Google's Change of Address tool applies too. Google says the tool is not needed for path changes within the same domain.³

Is your CDN or bot setting blocking the engines?

Check this before launch day, because a block at the CDN hides every other fix. Redesigns often bring a new host, firewall or bot policy, and those settings decide which crawlers can fetch your pages at all.

Defaults change too. Cloudflare's July 2026 changelog splits AI traffic into Search, Agent and Training.⁹ From 15 September 2026, new domains on Cloudflare block Training and Agent bots on pages that display ads, while Search remains allowed.⁹ A site that moves to a new domain or account during a redesign can pick up defaults the old one never had.

Search crawlers index pages so engines can answer questions later, so they are the ones a migration must keep. Agent traffic acts for a person in real time, and our site check for browser agents covers when to allow it. Whether to block training crawlers is a separate decision, which we weighed in an earlier note.

How do you check the move after launch?

Re-run the same prompt set on the same engines, with the same number of runs, two, four and eight weeks after launch. Compare three shares with the baseline: answers that name you, answers that cite one of your URLs, and answers that state the fact correctly.

Engines do not re-read a site all at once. Google's site move guide says a small to medium-sized site can take a few weeks for most pages to move, and larger sites take longer.³ Expect some answers to cite old URLs for a while. That is fine as long as each old URL redirects to the right page.

An AI citation check around a redesign

1. Before launch

   Log cited URLs and the facts taken, several runs per prompt per engine.

2. Launch day

   Redirects, canonicals, sitemap, IndexNow and a crawler access check.

3. Week 2

   First re-run; fix any cited URL that errors or lands on the homepage.

4. Week 4

   Second re-run; compare named, cited and correct shares with the baseline.

5. Week 8

   Third re-run; then start rewriting pages one at a time.

What to look for in the re-runs

• Cited URLs that now return an error or land on the homepage. Fix these first.
• Answers that still name you but no longer cite you. The fact may sit on a page the engine has not re-read yet.
• Answers that state an old fact, such as last year's price. Trace the passage back to the page it came from.

Watch for model updates too. If an engine changes its model between the baseline and a re-run, the shift may come from the engine, not your migration. Our note on measuring around a model release explains how to separate the two. MaxAEO, which sells AI visibility measurement, has written about how repeated runs of one prompt tend to cluster, so they carry less independent information than their count suggests.¹⁰

What will redirects not fix?

Redirects keep addresses working for engines that fetch pages. They do not change what a model already holds, what other sites say about you, or how an engine treats a page that lost its facts in the redesign.

Answers drawn from memory change slowly. If 14.4% of free, logged-out ChatGPT responses in August and September 2026 triggered a search, most of the rest drew on what the model already held.¹ Those answers may repeat an old URL or an old fact long after the move. A wrong fact usually traces back to a page somewhere on the web, and our guide to fixing wrong AI answers shows how to find it.

Some engines also cite broken addresses on their own. In a study published in March 2025, now dated, with its test period not stated, the Tow Center at the Columbia Journalism Review tested eight AI search tools on 1,600 queries. In that test, whose period was not stated, more than half of the responses from two of the tools, one of them Gemini, cited fabricated or broken URLs.¹¹ That test used news articles, and engines have changed since. It is still a reason to log the exact URLs answers give and to redirect old addresses generously.

Dates need care as well, because migrations often reset or drop them. Ahrefs studied 16.975 million cited URLs in a report published in July 2025, now dated, with its data period not stated. Pages cited by AI assistants were on average 25.7% newer than pages in organic results, in data whose period was not stated.¹² Google says its systems estimate when a page was published or significantly updated, and that dates must describe the page itself.¹³ Keep original dates through the move, and change them only when the substance changes.

Third-party links move slowest. Directories, partner pages and old press releases will keep pointing to your old URLs. Update the few that engines cite most often, which your log will show, and let redirects carry the rest.

A redesign checklist for AI search

Add an AI answer stream to the migration plan you already have. It needs one owner, a fixed prompt set and three moments: a baseline before launch, the launch itself and the re-runs after it.

1. Log cited URLs and the facts engines take from them, on every engine you track, before design work starts.
2. Rank pages by the facts they carry, with pricing, services, documentation and comparisons first.
3. Map every cited URL to a destination that states the same facts, through one permanent redirect.
4. Carry key facts over word for word in server-sent text, and rewrite later, one page at a time.
5. Check CDN and bot settings so search crawlers can fetch the new pages.
6. Submit the new sitemap and changed URLs, and keep redirects for at least a year.
7. Re-run the same prompts at two, four and eight weeks, and fix what broke.

Our view: the citation log is the cheapest part of the plan and the part most often missing. It costs a day or two before launch and cannot be rebuilt afterwards. If you want an outside baseline, Sigzen AI's AI visibility audit runs one across five engines and names the three pages to fix first.