If your company is about to change domains, platforms or URL structure, the biggest risk is not the change itself. It is the URL nobody inventoried before go live.
In CLM Controller's international project, we mapped 2,013 redirects before flipping the switch. In this guide, I walk through that process from inventory to post migration monitoring.
What site migration means in SEO
Site migration in SEO is any structural change that alters the way Google and AIs see your pages: a change of domain, protocol, URL structure, platform or a deep content redesign. A well planned migration preserves the authority each URL has built over the years while the site moves house. Without that care, rankings built over years can vanish in weeks.
In practice, there are five types of migration that genuinely move rankings. It is worth knowing each one before approving any project from the technology team.
1. Domain change. The company rebrands, merges operations or moves from .com.br to .com. This is the highest risk scenario.
2. Protocol change. The classic move from HTTP to HTTPS. It seems trivial, but each URL technically becomes a new address in the search engine's eyes.
3. URL restructuring. Categories that change names, folders that disappear, parameters that turn into slugs. The domain stays, the paths change.
4. CMS or platform change. Moving from WordPress to Next.js, or from one e-commerce platform to another. Rendering changes, speed changes and, almost always, the URLs change too.
5. Redesign with content rewriting. The address may stay the same, but titles, headings and copy are rebuilt. To the algorithm, the page has lost the identity that ranked.
Here is the nuance many people ignore: the change itself rarely drops traffic. What drops traffic is the accumulated signal lost along the way.
Every old URL carries backlinks, click history, AI citations and relevance built query by query. When a page changes address without a proper redirect, all of that equity is orphaned. And Google will not go looking for it on its own.
Why sites lose traffic after migrating
The drop almost never comes from a single error. It comes from three or four small failures nobody spotted before go live. These are the most common symptoms we find in post migration audits.
Redirect chains and 302s used instead of 301s
A 302 tells Google the change is temporary, so the old URL's authority sits waiting for a return that never happens. Chains (URL A redirects to B, which redirects to C) dilute signal and burn crawl budget.
Observable signal: in Search Console, under the Page indexing report, look for "Page with redirect" growing week after week.
Orphan URLs and pages nobody mapped
Every migration has pages nobody remembered existed: old landing pages, indexed PDFs, URLs with parameters. If they do not make it into the inventory, they become 404s the next day.
Observable signal: 404 errors rising in GSC and, in GA4, organic channels dropping on pages that do not even exist on the new site.
Content cut in the middle of the migration
Redesigns usually come with the order to "trim the copy". The team cuts H2s, removes the FAQ, shortens product descriptions. Google reassesses the page as if it were a different, weaker one.
Observable signal: the URL stays indexed, but average position collapses in GSC for the same queries.
robots.txt blocks and noindex tags forgotten in the new environment
The staging environment is blocked on purpose. At go live, someone forgets to unblock it. The whole site disappears from the index within days.
Observable signal: "Blocked by robots.txt" or "Excluded by noindex tag" in GSC right after launch. This is the cheapest error to prevent and the most expensive to discover late.
The migration checklist we used across 2,013 redirects
When CLM Controller decided to launch its international structure, with a .com in English, Spanish and Chinese, we mapped 2,013 redirects and ported 20 pages before the go live in August 2026. The method behind that project breaks into three phases.
Before: full URL inventory and performance baseline
Run Screaming Frog on the current site and export every indexable URL. Cross reference it with Search Console (pages that receive clicks) and with Ahrefs (pages that receive backlinks). The union of those three lists is your real inventory.
Then freeze a baseline: traffic per page in GA4, positions for the main terms and Core Web Vitals. Without that snapshot, you will never know whether the migration worked.
During: one to one mapping and staging validation
Every old URL needs a destination defined in a spreadsheet, with a direct 301 redirect and no chains. A page with no equivalent goes to the closest category, never to the homepage en masse.
In multilingual projects like CLM's, hreflang comes in here: each language version points to its siblings, with reciprocal return tags. Validate everything in staging with a full crawl before flipping the switch.
After: 90 days of monitoring in Search Console
On go live day, submit the new sitemap and request reindexing of the main pages. In the following weeks, track the coverage report: 404 errors, spikes in "page with redirect" and drops in impressions by directory.
Compare everything against the baseline. Two to six weeks of fluctuation is normal; a drop that lasts beyond 90 days demands an audit.
What changes when the migration has to survive AIs
In 2026, migrating a site stopped being a Google only problem. ChatGPT, Perplexity, Gemini and Claude cite URLs in their answers, and those citations do not follow the same logic as the search index.
When Google finds a 301, it transfers the signal within weeks. An AI that learned your old URL during training may keep citing that address for months, even with the redirect live. If the page disappears without a redirect, the user who clicks the citation lands on a 404 and your brand loses the answer it had earned.
That is why, before any go live, it pays to map which pages of your site already appear in LLM answers. Ask the AIs themselves about the topics you own, record the URLs cited and treat that list as untouchable: those pages get a direct 301, with no chain, and the destination content must preserve the answer that made the AI cite you.
Here at Netlinks we monitor citations across dozens of AIs through App Netlinks, 24 hours a day. In CLM Controller's project, the full hreflang setup across English, Spanish and Chinese served exactly that purpose: signaling to search engines and generative models which version answers each audience.
That care connects migration to our method, Response Marketing. Understanding the difference between SEO and GEO helps make the point clear: the URL is the address of your answer. Break the address and the AI serves your competitor's.
What to do before setting the go live date
If you made it this far with a migration on the horizon, you probably recognized a ghost or two: the forgotten 302, the redirect chain, the AI still citing a 2023 URL. Now you know that post migration traffic drops have traceable causes, and are almost always avoidable.
Three principles sum up everything we covered:
- Inventory before any decision. Nobody redirects well what they do not know. A full crawl of the current site is always the starting point.
- A redirect is an equity transfer. Every correct 301 preserves years of accumulated authority. Every mistake hands that authority back to the market.
- Go live opens the work, it does not close it. Monitoring rankings, logs and AI citations in the following weeks is what separates a scare from a catastrophe.
Tomorrow's practical step fits into one morning: run a crawl of your site, export the list of URLs with traffic and backlinks, and ask the team who owns the redirect map. If nobody raises a hand, you have just found the project's biggest risk.
That rigor is what put 2,013 redirects live with no improvisation in CLM Controller's project. The same process works for your domain, your platform or your international expansion.
Want to know where the risks of your migration are before Google and the AIs find them first? Talk to an Expert and get a diagnosis of your scenario, with no strings attached.
Migration does not lose traffic. Poorly planned migration does.
Frequently asked questions
Does migrating a site cause you to lose Google traffic?
You lose traffic when the work stops at design and nobody takes care of the redirects. A planned migration, with a full URL inventory, a 301 map and post go live monitoring, preserves accumulated authority and keeps traffic stable. The drop many people accept as "normal" almost always comes from avoidable failures: 302s instead of 301s, redirect chains and pages that vanished without a mapped destination.
How long does a site migration take without losing SEO?
It depends on the size of the site. Planning (URL inventory, redirect map, ranking benchmark) usually takes 2 to 8 weeks on medium sized sites. After go live, Google takes 4 to 12 weeks to reprocess signals and stabilize positions. In international projects, such as CLM Controller's with 2,013 mapped redirects, planning starts months before the switch.
What is the difference between a 301 and a 302 redirect in a migration?
A 301 signals that the change is permanent and transfers authority from the old URL to the new one. A 302 says the change is temporary, so Google holds the signals on the old URL waiting for it to come back. In a migration, using a 302 is one of the most expensive mistakes there is: the new site goes live without inheriting anything the old one built.
Do I need to redirect every URL from the old site?
Every URL with traffic, backlinks or rankings needs a mapped destination. A page with no value at all can return a 410, but that decision has to be deliberate, URL by URL. Redirecting everything to the homepage is also a mistake: Google treats it as a soft 404 and discards the authority. The inventory built from Screaming Frog, Search Console and GA4 is what separates a migration from a gamble.
What is hreflang and when is it mandatory?
Hreflang is the tag that tells Google which language or country version each page serves. It is mandatory on any site with versions in more than one language; otherwise Google may serve the Chinese page to someone searching in Portuguese. In CLM Controller's international project, with a .com in English, Spanish and Chinese, full hreflang was on the checklist before go live.
Does site migration affect citations in ChatGPT and Perplexity?
It does, and for longer than in Google. Search engines reprocess a 301 within weeks, but an AI that learned your old URL during training may keep citing that address for months. That is why redirects need to stay active for a long period, and post migration monitoring should include where the AIs are pointing, not just the Google index.
How much does a site migration with SEO support cost?
As an industry reference, migration projects with SEO consulting in the Brazilian market vary widely depending on the number of URLs, languages and platform complexity: from a few thousand reais on small sites to tens of thousands in international operations. The real comparison cost is a different one: how much the traffic the site loses is worth when the migration is done without a method.
