Migration redirect recovery sends each old URL to its correct new page. The links, searches and buyers each old page earned then reach your new site again. The first causes to test are old URLs redirected to the homepage and old URLs left returning errors. Aemorph recovers a failed move with the seven-step process it uses to plan one. Synapxe.sg's 4,000+ page move to Sitecore, planned that way, went from 6,372 monthly organic visits in August 2023 to 21,953 in March 2024.
A Failed Migration Shows Up as Rankings That Stay Down After Launch
A failed migration shows up as rankings and organic traffic that fall in the weeks after launch and stay down, while Search Console fills with 404 errors and old URLs that land on the homepage. Google states that rankings fluctuate for a while during a move, so a drop that holds after the new site settles points to the redirects.
| Symptom | Where you see it | Likely cause to test | Fix | Where it gets fixed |
|---|---|---|---|---|
| Rankings collapse after launch and stay down | Ahrefs or Semrush position history | Old URLs redirected to the homepage | One-to-one redirects to the closest new page | Server or CMS redirect rules |
| Search Console reports a jump in 404 errors | Page indexing report in Search Console | Old URLs with no redirect | Map each old URL and add a 301 | Redirect list |
| Old URLs reported as soft 404s | Page indexing report in Search Console | Many old URLs sent to one irrelevant page | Replace each blanket redirect with a mapped one | Redirect list |
| Pages that ranked are missing from the new site | Wayback Machine snapshots and an Ahrefs top pages export | Content dropped in the rebuild | Restore the missing content on the new site | New site content |
| Inbound links point at dead URLs | Ahrefs broken backlinks report | Linked URLs left out of the redirect list | Redirect each linked URL to its closest new page | Redirect list |
Symptoms, likely causes and fixes for a failed site migration.
A failed migration sits in a group of technical faults that stop the right page being read, and it often starts on the build host: a new site built on a public host leads to a staging site indexed by Google, with test pages competing against your live ones. A move that keeps old and new versions live together duplicates each page, the problem keyword cannibalisation covers; a new site shipped as a JavaScript app leads to single-page app rendering failures; and broken URLs outside a move are 404 errors.
Why did my rankings drop after a website migration?
Rankings drop after a website migration when old URLs lose the signals they earned: redirected to the homepage, left returning 404 errors, or moved without the content that ranked. Google expects some fluctuation during a move, so a drop that persists after the new site settles is the signal to audit the redirects.
Redirects Fail When Old URLs Are Treated as Addresses, Not Pages
A migration fails when the redirect plan treats old URLs as addresses to clear instead of pages that each earned links, rankings and buyers, so the plan sends them to the homepage or to nothing and those signals stop counting for your site. Google tells site owners to map old URLs to new ones with server-side permanent redirects. Google also states that sending many old URLs to one irrelevant destination, such as the homepage, confuses users and risks being treated as a soft 404, and that redirects are best kept for at least one year.
Source: Google Search Central, October 2026
Each old page also stated facts about your business: a service, a location, a price or an answer to a buyer question. Aemorph's EAV Exhaustion Methodology records each of those facts as a slot. A homepage redirect empties each slot the old page filled, because the homepage states no such facts.
That is why a redirect count is the wrong measure of a migration. A plan with a redirect for each old URL still fails when the destinations no longer carry the facts the old pages stated.
What happens when you redirect old URLs to the homepage?
Redirecting old URLs to the homepage when no relevant replacement exists risks Google treating those redirects as soft 404s, and it leaves the links and rankings the old pages earned without a matching page to pass to. Each old URL needs its closest new equivalent instead.
Recovery Rebuilds the URL List, Restores Content and Redirects One to One
Recovering a failed migration rebuilds the full list of old URLs, maps each one to its closest new page, restores the content the move dropped and replaces each blanket redirect with a one-to-one 301. Aemorph runs recovery through its seven-step migration process, the same steps it uses to plan a move before launch:
- Compiles each old URL from Search Console, Ahrefs, Screaming Frog, the old XML sitemap and Wayback Machine snapshots, with duplicates removed.
- Lists each old URL that carries inbound links, from Search Console, Ahrefs and Google Analytics.
- Lists each old URL with rankings and sessions before launch, from the same three sources.
- Consolidates the three lists with Search Console 404s, decides which URLs map to a new page and sends the remainder to a custom 404 page.
- Restores the content and facts the rebuild dropped onto the mapped new pages, with titles, headings, canonical tags and internal links checked.
- Replaces each homepage or blanket redirect with a one-to-one 301 that your developers implement as specified.
- Monitors Search Console 404s, key-page uptime, Core Web Vitals, weekly Ahrefs crawls and analytics until the recovered pages hold their positions.
Aemorph specifies the redirects, your developers or IT vendor implement them, and Aemorph verifies the result.
Five past migrations ran through the same seven-step process, from 400+ to 4,000+ pages. These are planned migrations, not recoveries: they show what the process produces when it runs before launch.
| Site | Pages | Platform move | Period | Outcome with source |
|---|---|---|---|---|
| Synapxe.sg, Singapore's healthtech agency | 4,000+ | Custom CMS to Sitecore | Launched Jul 2023 (project Mar to Aug 2023) | 6,372 monthly organic visits in Aug 2023, 21,953 in Mar 2024, up 245% (Ahrefs organic traffic, captured April 2024) |
| Remarkablefurniture.com.au, an Australian outdoor furniture retailer with showrooms | 2,000+ | WordPress to Magento | Oct 2019 to Mar 2020 | 3,883 monthly organic visits in Sep 2019, 12,172 in Oct 2020, up 213% (Ahrefs, Australia, October 2020) |
| TWGTea.com, a global tea retailer | 2,500+ | Magento to custom CMS | 2018 | Held between 25,014 and 31,903 monthly organic visits through 2018 (Ahrefs, all countries, September 2026) |
| ePropulsion.com, an electric boat motor maker | 400+ | Wix to WordPress | Feb to Apr 2021 | 1,749 monthly organic visits in Dec 2020, 7,429 in Apr 2021 (Ahrefs, all countries, September 2026) |
| MyHeart.org.sg (Singapore Heart Foundation) | 1,500+ | WordPress to WordPress | Sep 2021 to Mar 2022 | Key-phrase rankings maintained and both project goals achieved (client statement, LinkedIn recommendation, 2 Jan 2023) |
Source: Ahrefs, on the dates named in each row
Synapxe.sg launched as a new domain, so August 2023, its first full month, is the baseline, and the result measures growth after launch, not a before-and-after comparison across the move. Each comparison covers two dates and does not isolate the migration from the work around it. Synapxe, TWG Tea, ePropulsion and the Singapore Heart Foundation are past clients.
“The move included a complete rebuild of our website ePropulsion.com and it was crucial that we didn't lose any rankings. Through the guidance of Kevin and his team, we were able to successfully move to a more flexible WordPress platform and our scores on Ahrefs also increased.”
Flora LuoePropulsion
“Kevin and his team at Aemorph were assigned to work on the SEO migration efforts of the MyHeart.org.sg website in early 2022. [...] I'm happy that we engaged Kevin and his expertise as the goals of both were successfully achieved.”
Kheng Leng ChngMedia and Comms Professional, MyHeart.org.sg
How long does it take to recover from a bad migration?
Recovery from a bad migration starts once the one-to-one redirects are live and Google recrawls the old URLs, and its pace depends on how many URLs carried links and rankings and how fast your developers ship the redirect list. Aemorph measures recovery from the date the corrected redirects go live, not from the original launch.
Each recrawl wait adds to the SEO time tax, the calendar time a business spends before SEO returns anything.
Does a website migration always lose traffic?
A website migration that maps each old URL to its correct new page before launch, verifies the redirects and monitors the new site afterwards gives each old page's links and rankings a matching page to pass to. Google still expects rankings to fluctuate for a while during a move, and the five migrations above ran on that plan.
Unmapped Old URLs Keep Losing the Signals They Earned
An old URL left unmapped keeps losing the links and rankings it earned for as long as it returns an error or lands on the homepage, so Aemorph fixes the URLs that carried links, rankings and sessions before launch first. Recovery order follows commercial value: bottom-of-funnel pages first, then middle-of-funnel pages, then top-of-funnel pages.
| Old URL state | What happens | What it costs you | Next step | What triggers a recheck |
|---|---|---|---|---|
| Returns a 404 with links pointing at it | Inbound links reach an error page | The authority those links earned stops counting | Map and 301 it first | A broken backlink in Ahrefs |
| Redirects to the homepage with no relevant replacement | Risks being treated as a soft 404 | The page's rankings and facts disappear from the new site | Replace with a mapped 301 | Soft 404s in Search Console |
| Redirects to a matching page without its content | The redirect works, the facts are missing | Rankings return slowly or never | Restore the content on the destination | A recovered URL that stays below its old position |
| Redirects one to one with content restored | Signals pass to the matching page | Rankings return as Google recrawls | Keep the redirects for at least one year | A platform change or URL restructure |
Cost and recheck point by old URL state, as illustrative scenarios. Keep-for-one-year guidance: Google Search Central, site moves with URL changes.
Aemorph reports recovery with cluster-level measurement: the share of questions in each buying decision where a recovered page ranks or where AI answers name your business, tracked from the date the corrected redirects go live. That view covers SEO, search engine optimisation, which earns your place in Google's results; AEO, answer engine optimisation, which gets you quoted in Google AI Overviews; and GEO, generative engine optimisation, which gets you cited inside the AI chats. Homepage traffic alone hides whether the service and location pages recovered.
How long do you keep 301 redirects after a migration?
Keep 301 redirects after a migration for as long as possible, and at least one year, which is Google's own guidance for site moves with URL changes. Removing them earlier cuts off the old links and bookmarks that still point at the old URLs.
Buyers Following Old Links Meet What the New Site States
A failed migration sends buyers who follow an old link to a page that no longer states what they came for, and a buyer who meets a missing service, a dead price page or an error page draws conclusions about your business. Old URLs live in emails, proposals, directory listings and AI answers long after launch.
Where the old pages carried regulated statements, such as a financial disclosure, a health claim or a licence number, a redirect to a page without that statement removes it from the path a buyer follows. Aemorph checks that each restored page carries the same approved facts the old page stated, against your verified record, the one approved set of facts about your business. A question about a specific obligation is one for a qualified legal adviser in your jurisdiction.
General guidance, not legal advice.
Who is responsible for a failed website migration?
The business that owns the site carries the commercial cost of a failed website migration, so the redirect plan needs a named owner on your side, a specification from your SEO adviser and a verification step before and after launch. Aemorph specifies and verifies; your developers or IT vendor implement.
Technical SEO Brings Your Old Pages' Rankings Back to the New Site
Aemorph's technical SEO rebuilds your old URL list, specifies the one-to-one redirects and restored content, and verifies the recovery once live, so the rankings and buyers your old pages earned reach your new site. The same work plans a migration before launch, which costs less than recovering one, and the free Money on the Table audit puts a number on the revenue lost at your current visibility in search.
The Showstopper Sensor (Sprint 1), a 30-day showstopper-answer sprint for ChatGPT, Claude, Gemini and Perplexity, publishes your approved answers to your showstopper questions, the buyer questions that stop a purchase when AI answers them badly, on your site. Those answers need pages that Google and AI crawlers reach, so a recovered redirect list is part of the ground they stand on.
Who plans the redirects, Aemorph or your developers?
Aemorph plans and specifies the redirects and your developers or IT vendor implement them: Aemorph builds the old URL list, maps each URL, specifies the restored content and verifies the redirects once live. Your team keeps control of the CMS, the server rules and the release schedule.
Start with a free strategic conversation, which includes prompting the AI chats for your current brand answers. Technical SEO fixes are scoped from the audit findings and set out in your quote; starting points are on the pricing page.