How to protect AI visibility during a redesign or migration

To protect your AI visibility during a redesign or migration, protect your search visibility first. Keep every URL you can, redirect each one you can't to its closest equivalent, carry over the content that answers customer questions, and make sure the new site and its host don't block crawlers. Then check the results after launch instead of assuming.

The link between the two is documented for Google. A page must be indexed and eligible to be shown in Google Search with a snippet before it can be a supporting link in AI Overviews or AI Mode. If a relaunch knocks pages out of the index, it removes them from that pool too. For ChatGPT, Claude and Perplexity, we found nothing published about how they treat a moved site, so the safe plan is the careful one.

Work out which kind of change you are making

"Redesign" and "migration" cover very different projects. The risk depends on whether URLs change.

Google's guide to moving a site also gives advice that many projects ignore: "Plan your changes to your site one after the other, not everything at the same time." Its example is to move to a new domain first and change the layout afterward.

What Google says to expect

Even a well-run move causes movement. Google says: "Expect temporary fluctuation in site ranking during the move," and gives a general rule that "for medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones (and for larger sites, even longer)."

On redirects and link value, Google is reassuring: "301 and other permanent redirects don't cause a loss in PageRank."

On redesigns combined with a move, it is less so. The Change of Address help page says: "If you combine a site move with a redesign of the site's content and URL structure in the new location, you will probably see some traffic loss as Google might need to relearn and reassess the individual pages."

We found no Google statement that a site move affects AI Overviews or AI Mode differently from classic Search. Since those features draw on indexed, snippet-eligible pages, plan on your AI visibility following your index status.

Before launch: inventory and map

1. List every current URL. Google suggests sitemaps, server logs or analytics for the URLs that get the most traffic, the links report in Search Console, and your content management system.
2. Mark the pages that carry your answers. These are the pages that state facts about you: services, pricing, locations, policies, FAQs, About and author pages. If you track AI answers, also mark any page an assistant has cited.
3. Build a URL map. Each old URL gets one new destination. Google's steps call this "a URL mapping from the current URLs to their corresponding new format."
4. Decide what is retired. For content you are not moving, Google says to "make sure those URLs correctly return an HTTP 404 or 410 error response code on the new site."
5. Save a baseline. Export Search Console data, and record what AI assistants say today about your business and main services.

Carry over the content and the structured data

Redesigns often lose content without anyone deciding to remove it. A new template shortens service pages, drops an FAQ block, hides text behind tabs, or leaves out the markup the old theme added automatically.

Compare old and new versions of each marked page before launch:

• Are the direct answers, definitions, tables and prices still on the page, in text?
• Is the structured data still present, and does it match the visible page? Google's rule is to make sure "structured data matches the visible text on the page."
• Do images and downloads still exist? Google says to "Transfer images and downloads (such as PDF documents) that you host."
• Does the content appear without scripts that a crawler might not run? Our technical audit checklist for GEO covers this check.

If the new site has language versions, Google says to update hreflang annotations to the new URLs. Our guide to multilingual and international GEO explains those.

Redirects: type, targets and how long to keep them

Google's advice on type is clear: "we recommend that you use HTTP permanent redirects if possible, such as 301 and 308." Its redirects documentation explains that a permanent redirect shows the new target in search results, while a temporary one keeps showing the source page. JavaScript redirects are a last resort, because "Google might never see it if rendering of the content failed."

Three rules on targets:

• Redirect to the equivalent page. "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site." Google says this "might be treated as a soft 404 error."
• Avoid chains. Googlebot can follow up to 10 hops, but Google advises "redirecting to the final destination directly."
• Test the targets. Google notes: "We frequently see people redirecting to the wrong (non-existent) URLs on the new site."

On duration, Google gives two numbers, and you should know both:

Neither page says you can remove redirects once Google has processed them. Treat a year as the floor, and keep them longer if you can.

Bing's webmaster guidelines say to "Use 301 redirects for permanent URL changes" and to "Use 302 redirects only for very short-term changes (less than 2 days)." The same guidelines say Bing and Copilot search experiences rely on the same crawling, indexing and ranking foundation, so this matters for Copilot answers too.

Launch day: remove the blocks you added for development

Google's "Common mistakes" list for site moves begins with "noindex or robots.txt blocks." Its instruction: "Don't forget to remove any noindex or robots.txt blocks that were only needed for the migration."

Run this list as soon as the new site is live:

1. Open robots.txt on the live domain. Confirm it does not disallow the whole site, and that any rules for AI crawlers are the ones you intend. Our robots.txt guide covers the syntax.
2. Check the page source of several templates for a leftover noindex rule.
3. Confirm each page's canonical tag points to its own new URL.
4. Click through a sample of old URLs and confirm each redirects once, to the right page.
5. Update internal links so they point to new URLs directly.
6. Submit the new sitemap in Search Console.
7. Confirm Search Console verification still works. Google warns that an HTML verification file or meta tag can go missing in a new copy of the site.

New host, CDN or firewall: check crawler access

A move to a new host often brings a new security layer with its own defaults. Google's hosting-change guide warns: "Check your firewall configuration or denial of service (DoS) protection. Make sure it does not block Googlebot's ability to reach the DNS or the hosting provider's servers."

The same risk applies to AI search crawlers. OpenAI recommends "allowing OAI-SearchBot in your site's robots.txt file and allowing requests from our published IP ranges." Perplexity says sites behind a web application firewall may need to explicitly allow its bots. Anthropic says its bots honor robots.txt and that it will not attempt to bypass CAPTCHAs, so expect a challenge page to stop them.

Two guides help here: how to check whether your CDN or firewall is blocking AI crawlers, and AI crawlers and robots.txt for the tokens. If you change crawler rules at launch, allow for a delay. OpenAI says it can take about 24 hours for its systems to adjust to a robots.txt update for search results, and Perplexity says up to 24 hours.

What is not documented for ChatGPT, Claude and Perplexity

As of October 2026, we found no statement from OpenAI, Anthropic or Perplexity on whether their crawlers follow 301 redirects, how fast they pick up moved URLs, or how long old URLs stay in their systems. Anyone who gives you a number for that is guessing.

The low-risk steps are the same ones that help people:

• Keep redirects in place so any old link or stored URL still reaches the right page.
• Keep crawler access open on the new site from the first hour.
• Update the links you control. Google's list includes social profile links and ad campaigns. Add business listings and directories.
• Ask sites that link to your important pages to update their links.

After launch: what to re-check

Google's advice is to monitor both the old and new URLs. Check often in the first weeks, then monthly.

• Search Console indexing and sitemap reports. New URLs should rise as old ones fall.
• URL Inspection on key pages. Google suggests it for checking that Googlebot can reach new infrastructure.
• Server logs. Look for errors and confirm that search and AI crawlers are getting pages, not blocks. See how to verify real AI bots in your server logs.
• The Generative AI performance report. Its Pages tab shows which URLs earned impressions in AI Overviews and AI Mode. Google says it groups data by the final URL "after any redirects." Our guide to reading that report explains its limits.
• Your baseline questions. Ask the same AI assistants the same questions you recorded before launch, and compare.

If you are changing domains

A domain change adds the Change of Address tool in Search Console. Google says to use it "after you've moved and redirected your site." Its help page sets out the main points:

• You must be an owner of both the old and new properties, in the same Google account.
• Use it for all subdomain variants of the old domain, including www and non-www, even ones you don't actively use.
• Its effects "continue for 180 days after you start migration in Search Console."
• Google recommends "continuing to pay for the old domain for at least a year to prevent others from buying and using your abandoned domain for malicious purposes."

Conclusion

The best protection for AI visibility in a redesign or migration is the work that protects search visibility: URLs mapped, redirects permanent and kept for at least a year, answer content and markup carried over, and no crawler blocked by the new setup. For the AI assistants whose handling of site moves we could not find documented, careful redirects and open access are the low-risk steps. If a relaunch is on your calendar, request a free GEO audit before you start. More guides are in our GEO and AEO Guide.

Frequently asked questions