Migration & redesign
A website migration or redesign that keeps your rankings
A redesign or a platform migration can quietly erase years of ranking the moment it goes live, and a business often doesn't find out until the traffic is already gone. The pattern is well documented: agencies across the industry run entire recovery practices built around exactly this failure. I'm Nipun Arora, running SEO-first migrations and redesigns since 2014, and every one follows the same four-part check before a single old URL gets retired.
What actually happens
Redesigns lose rankings often enough to support a recovery industry
A mishandled redesign or migration typically costs a site 30% to 70% of its organic traffic, a range independently repeated across agency analyses of the pattern (WebFX's breakdown of redesign traffic drops). Most of that loss traces to the same handful of decisions: a deleted page with no redirect, a changed URL structure, a lost internal link, or a canonical tag pointing at the wrong page, exactly the technical calls a developer makes alone, without an SEO review, during a rebuild.
One named case shows the scale at its worst. A developer-led redesign for a painting business replaced hundreds of blog articles and dozens of service pages with a six-page brochure site, breaking every existing link into a 404; organic traffic collapsed from over 300 visits a day to fewer than 10 (Hog the Web's published account of the Imhoff Painting recovery, 27 Aug 2026). Levi Meulen of Hog the Web, the agency that restored the traffic within about a month, put it plainly: "A prettier website isn't much of an improvement if the pages bringing customers disappear."
That case isn't an outlier. It's common enough to sustain a whole tier of the market: at least eight agencies, including Hog the Web, WebFX, Sixth City Marketing, and Sagapixel, publish dedicated recovery services for exactly this problem. Google's own support forum carries a live thread titled "Lost Organic Traffic After Website Redesign", proof the pattern reaches Google's own help desk, not just agency blogs with a recovery service to sell.
Recovery is possible once the technical gaps are found: businesses that fix redirects, canonicals, and sitemaps after a bad redesign typically recover 70% to 80% of pre-redesign traffic within 60 to 90 days (Demand Influence's recovery-timeline research). Even large, well-resourced sites aren't immune: NerdWallet lost an estimated 23.6% of its organic traffic, worth roughly $6 million, over three months following site changes (Ahrefs' case study).
The framework
Four checks that run before an old URL gets retired
Every migration or redesign on this page follows the same order, and skipping a step is exactly how the cases above happen.
Redirect mapping. Every existing URL gets matched to its replacement, one to one, before the old site comes down. A redirect list built after launch is a redirect list built too late; a page that loses its target 404s the moment the switch flips.
Content parity. Pages that already rank keep the content that earned the ranking: the same topic coverage, the same internal links pointing in, carried into the new structure rather than trimmed down to a shorter page that covers less ground.
Schema continuity. Structured data moves with the page it describes. A Service or Article schema block that existed on the old URL exists on the new one too, so a crawler that already trusted that page doesn’t have to re-learn what it is.
Measurement before and after. Rankings, indexed pages, and Core Web Vitals get recorded before the migration and checked again on a fixed schedule after. A drop gets caught and traced to its cause within days, not discovered three months later in a report nobody opened until now.
Leaving WordPress
Moving off WordPress without losing what it already ranks for
WordPress owners who want out, for plugin bloat, security patching, or a slow editor, face the same fear as any redesign: the jump itself is what risks the rankings, not the destination. The four-step framework above runs on a WordPress departure exactly as it runs on any other migration.
Astro is the stack this site runs on, and the one I move WordPress departures to: static HTML by default, no plugin stack to patch, and the same JSON-LD written in from day one rather than rebuilt from a theme's defaults. Astro's own team names "SEO best practices" as one of five official partner service categories, at four agencies worldwide, a small, credentialed field rather than a crowded one. A WordPress-to-Astro move is scoped on this page rather than a separate one: describe your current setup on the contact page and it runs through the same four checks above as any other platform migration.
Who this is for
Three situations that bring a site to this page
A redesign is planned, and the traffic the current site already earns can't be an afterthought in that plan.
A redesign or migration already happened, and traffic dropped, sometimes overnight, sometimes over a slow month, and nobody has traced why yet.
WordPress is the platform being left, and the fear of losing rankings is the only reason the move hasn't happened yet.
A site that doesn't exist yet is a different job: SEO Website Development covers a build from the ground up, with the same search-first order run here. If Dubai is the specific market you're hiring for, start at SEO consultant in Dubai instead.
The question of who leads a migration, not just which platform to move to, is covered in who should build your website when SEO matters.
Send your domain and I'll scope the migration.
Start a migrationWhat this doesn't promise
No guaranteed ranking, on any migration
No migration or redesign ships with a guaranteed ranking outcome, and a consultant who prices that promise is pricing something outside anyone's control, migration included. What's committed is the four-step check above, run in full, and a written record of what moved, what changed, and what the numbers looked like before and after, whether the result flatters the work or not.
This is a fixed-scope engagement, agreed and priced before the current site gets touched, following the same proposal discipline as every engagement on this site. The price isn't published on this page; send your domain through the contact page and I'll quote a fixed number before I open anything.
Questions
Six questions before a migration or redesign
How do I migrate my website without losing SEO rankings?
Map every old URL to its replacement before the switch, carry content and schema across instead of trimming it down, and measure rankings and Core Web Vitals before and after. Those four checks separate a safe migration from the redesigns that lose 30% to 70% of their traffic.
What causes ranking loss after a website redesign?
Most often a missing redirect, a changed URL structure, deleted content that was actually ranking, or a canonical tag left pointing at the wrong page, the same handful of decisions a developer makes alone, without an SEO review.
Do I need a 301 redirect for every old URL?
Every URL that currently ranks or holds an inbound link, yes. A URL with no traffic and no links can retire without one; the redirect-mapping step above is what tells the difference.
How long does it take to recover rankings after a bad migration?
Recovery timelines vary, but sites that fix redirects, canonicals, and sitemaps after a mishandled redesign typically recover 70% to 80% of prior traffic within 60 to 90 days. A migration run correctly the first time skips that recovery period entirely.
Can you migrate a WordPress site to Astro?
Yes. It's the migration this practice runs most often off WordPress, following the same four-step framework as any other platform move.
Does this service include ongoing SEO after the migration?
The migration itself is the fixed-scope deliverable. Ongoing work after launch, content, links, further technical fixes, gets its own proposal, agreed separately, never assumed from the migration engagement.
A rebuild and a penalty recovery, both run through these four checks, are written up with dated numbers in the case studies.
Send your current site and the platform you're moving to, or the redesign you're planning, and I'll map what a ranking-safe move actually involves before anything changes.
Start a migration