What to Check When a Website Migration Changes AI Referral Traffic
When a website migration changes AI referral traffic, the first instinct is to assume ChatGPT, Perplexity or Gemini stopped recommending you. Sometimes that is true. Often, however, the drop is caused by something more mundane: broken redirects from URLs that AI answers still cite, analytics tags that changed during the rebuild, or new security settings that block AI crawlers. This migration-specific checklist helps you separate real visibility loss from measurement errors and technical breaks, in the order that finds problems fastest.
Step 1: Confirm the Change Is Real
Before investigating causes, make sure the numbers can be trusted.
- Compare the same date ranges before and after launch, adjusting for weekday patterns and seasonality.
- Check whether your AI channel grouping still exists in the new analytics property or container.
- Confirm the analytics tag fires on every template of the new site, including blog, product and location pages.
- Check whether consent banner settings changed, which can reduce tracked sessions across all channels.
If organic, direct and AI referral traffic all fell by a similar proportion on launch day, the cause is probably tracking, not AI visibility. Our guide to AI search impact on traffic explains how to tell channel-wide shifts from AI-specific ones.
Step 2: Check Whether Referrer Data Survived the Migration
Migrations can change how referral information is captured:
- New redirects that strip parameters: AI platforms often add
utm_sourcevalues to cited links. A redirect that drops query strings loses that tagging. - Domain or subdomain changes: cross-domain tracking that was not configured can turn referrals into direct traffic or self-referrals.
- Referrer-Policy headers: a stricter policy on the new site does not affect incoming referrers, but misconfigured intermediate redirects through other domains can.
- Single-page app routing: if the new site uses client-side routing, page views may not be recorded correctly after the first page.
Test by clicking a cited link from a real AI answer and checking the session in GA4 DebugView or real-time reports. Repeat the test on mobile, because some AI apps open links in in-app browsers that behave differently from desktop browsers. If you need a refresher on channel setup, our AI search optimization team documents the referral sources worth tracking.
Step 3: Test the URLs AI Platforms Actually Cite
This is the most important migration-specific check. AI answers keep citing old URLs for weeks or months after a migration, because their indexes and training data update slowly. If those old URLs return 404 errors, users clicking from AI answers land on error pages, and the referral session may not register at all.
Build a list of previously cited URLs from:
- Pre-migration landing pages for AI referral sessions in analytics
- Your prompt testing records of cited URLs
- User-triggered AI fetcher requests in historical server logs
Then crawl the list and confirm every URL redirects with a single permanent redirect to the closest equivalent new page.
| Old URL status | Impact on AI referral traffic | Fix |
|---|---|---|
| 404 | Clicks lost, citation likely dropped later | Add permanent redirect |
| Redirect chain | Slower, sometimes timed out by fetchers | Point directly to final URL |
| Redirect to homepage | Poor user experience, low conversion | Map to equivalent page |
| 200 on new equivalent | Healthy | Monitor |
Step 4: Verify AI Crawlers Can Still Access the New Site
New hosting, CDN or security settings often arrive with a migration. Check that robots.txt on the new site matches your intended crawler policy, that firewall and bot management rules do not challenge AI crawlers, and that server logs show verified requests from OAI-SearchBot, ChatGPT-User, PerplexityBot and similar agents after launch. If AI crawler activity dropped sharply on launch day, investigate access before anything else. Our fix AI crawler indexing service starts with these checks.
Step 5: Compare Content Between Old and New Pages
Rebuilds often change content without anyone intending it to:
- Long explanations shortened into marketing copy
- FAQs removed or moved into tabs loaded by JavaScript
- Tables and specifications converted into images
- Author information, dates and sources dropped from templates
- Internal links reduced by new navigation designs
These changes can reduce how often a page is selected as a source, even when redirects are perfect. Compare archived versions of top cited pages with their new equivalents and restore the elements that made them citable. AI content optimization can then build on that restored base.
Step 6: Check Canonicals, Sitemaps and Indexing
AI systems that rely on Google or Bing indexes inherit any indexing problems created by the migration. Confirm that canonicals on new pages self-reference, that XML sitemaps list only final URLs, and that Search Console shows new pages being indexed at the expected rate. A slow transfer of indexing signals delays recovery in AI answers too.
Step 7: Re-Test Visibility With Your Prompt Set
Once technical and tracking issues are resolved, run your standard prompt set and compare mention and citation rates with pre-migration results. If mentions remain stable but citations now point to third-party sites, your new URLs are not yet trusted or indexed. If mentions have dropped too, focus on content and entity signals.
Plan the Next Migration Better
Most of these problems are preventable. Before any future migration, export every URL that receives AI referral sessions, add them to the redirect map with high priority, and include AI crawler access in your launch checklist. Record a prompt-testing baseline in the month before launch, so you can compare like with like afterwards. If the new site changes templates, involve your content team early so that tables, FAQs and author details survive the redesign. Teams that plan this way usually see AI referrals recover within weeks rather than months, and some see no dip at all. Treat the AI-cited URL list as seriously as your top organic landing pages, because for many businesses those pages now drive the most qualified enquiries. Include Core Web Vitals optimization checks too, since slow new templates frustrate the visitors AI platforms send.
Attribution Notes for Your AI Referral Traffic Report
When reporting on AI referral traffic after a migration, separate the findings clearly: measurement changes, broken URLs, access issues and genuine visibility changes. Leaders need to know which problems are already fixed and which require longer-term work.
Frequently Asked Questions
How Long Do AI Platforms Keep Citing Old URLs?
It varies. Live retrieval platforms update faster, while answers influenced by training data may reference old URLs for months. Keep redirects permanent.
Should I Ask AI Platforms to Update My URLs?
There is usually no direct submission process. Make sure search engines index the new URLs and that redirects are clean.
Why Did AI Traffic Drop While Organic Traffic Held Steady?
Usually because AI platforms cite specific deep URLs that lost their redirects, or because AI crawlers are now blocked.
A careful post-migration check protects one of your most valuable traffic sources. For hands-on support, see our AI traffic drop recovery service, read our AI traffic recovery case study, book a technical SEO audit, learn how to fix AI search visibility, explore website maintenance services, or review ChatGPT visibility ranking.