A site migration or redesign is a change to your URLs, templates, or domain that risks losing indexing, rankings, and citations in AI answers. The essentials are a map of old URLs to new ones, permanent 301 redirects, structured data carried over intact, and measurement both before and after launch. This guide covers what to watch before, during, and after a migration — including confirming that old URLs still lead to matching content and that the new build hasn’t blocked crawling or indexing.
What migrations add in the AI era
Classic SEO migration work watches indexing and rankings: redirects, sitemaps, internal links. That still holds. But there’s a new layer on top.
Many AI tools cite specific URLs or source pages in their answers. When a URL changes and the old one stops working, the citation loses its destination. On top of that, these tools ingested your content earlier and refresh on their own schedule — with some of them, changes surface later than they do in regular search, and the pace varies from tool to tool. So for a while, AI may point at URLs you no longer have — and whether the visitor lands on the right page or on an error comes down to your redirects.
| Aspekt | Area | What to watch for |
|---|---|---|
| Redirects | Classic SEO | A 1:1 map, permanent 301s, no chains and no blanket redirect to the homepage |
| Cited URLs | AI layer | Many AI tools link to specific URLs — those should stay reachable after the migration |
| Structured data | Both | The new template often forgets to carry it over |
| robots.txt and noindex | Both | A crawl or indexing block left over from staging is a classic post-launch mistake |
| Refresh cadence | AI layer | With some AI tools, changes surface later and less predictably |
Before the migration: what to prepare
Most problems come down to nobody measuring the starting point. Without it, you can’t tell after launch whether a drop is real.
- URL inventory Export every indexed URL from Search Console, your sitemap, and a crawl of the site.
- Measurement baseline Record traffic, indexing, and visibility before the migration — otherwise you'll have nothing to compare against.
- Prioritize cited pages Find out which pages get AI traffic or tend to be cited; watch those most closely.
- Map of old URLs to new ones A specific destination with matching content for every old URL — not a blanket redirect to the homepage.
- Back up content and data Save the original copy and structured data so you have something to compare against after launch.
The migration, step by step
-
Measure your baseline and export your URLs
Export indexed URLs from Search Console and your sitemap, and record your starting traffic and visibility.
-
Match old URLs to new ones
Give every old URL a specific new address with matching content. Pages with AI traffic come first.
-
Deploy permanent redirects
For a permanent migration, 301 is the right call; 302 is meant for temporary moves. Avoid chains — a single hop straight to the destination is ideal.
-
Carry over structured data and check robots.txt
Confirm the new template has the same structured data, and check robots.txt, noindex tags, and canonical URLs.
-
Submit your sitemap and track the results
Submit the sitemap to Search Console and Bing Webmaster Tools, and compare indexing and traffic against your baseline.
If you’re targeting Bing as well, you can announce the URL changes through IndexNow. It can speed up discovery of the changes inside the Bing ecosystem, but on its own it won’t guarantee that every signal gets rewritten quickly — more details are in the article on Bing as a layer for AI. Settings for AI crawlers are covered in robots.txt for AI.
After launch: what to measure
The first few days matter. Track:
- Indexing and crawl errors — especially a spike in 404s, which points to missing redirects.
- Internal links and navigation — make sure they point straight to the new URLs, not through a redirect.
- AI traffic — if you track it (through custom segments or traffic sources), check whether it dropped; AI segments in Search Console help here.
- AI visibility, manually — run your key queries through a visibility test and compare against the pre-migration picture.
- Structured data — whether the new template actually outputs it; see structured data for AI.
Common mistakes
A 404 instead of a redirect
The fastest way to lose both your rankings and the foundation for AI citations. Every old URL needs a destination.
Everything to the homepage
Redirecting old URLs to the homepage en masse can be treated as a soft 404 or an irrelevant redirect, and the relevance is lost.
A forgotten crawl block
A line blocking crawling of the whole site survives from staging. The site is live for users, but robots.txt can stop search crawlers from crawling it.
Everything at once
Changing URLs, templates, and copy together means you won’t know what caused a drop. Separate the steps when you can.
Key takeaways
- A migration changes what search engines and AI already know — without a URL map, you risk losing indexing and citations alike.
- 301s and a single hop — permanent redirects, no chains, no blanket redirect to the homepage.
- Leave the redirects running for a long time — AI can point at old URLs well after the fact.
- Structured data and robots.txt — the two things a new template breaks most often.
- Measure before and after — without a baseline you can’t evaluate a drop; why URLs matter.
Planning a redesign and don’t want to lose visibility? This site is run by Sniper Design — an AI SEO audit walks your redirects, structured data, and AI visibility after a migration and pinpoints what got lost along the way.
For transparency: this process draws on public search engine documentation and practice as of July 11, 2026. The pace at which AI systems settle after a migration varies by tool and can’t be guaranteed; the steps here reduce the risk but don’t eliminate it. How the content on this site is produced is described on the author page.
