SEO Migration: How to Move a Website Without Losing Rankings

An SEO migration is the work of moving a website (new platform, new design, new domain or consolidated sites) without losing the rankings, traffic and authority the old site earned. The method that protects you is unglamorous: freeze a full benchmark before anything moves, map every URL that earns traffic to its exact new home, redirect one-to-one, and verify the live result page by page after launch. Most migration damage is self-inflicted, and almost all of it happens in the planning gap before launch day.

Why migrations lose rankings

Google ranks URLs it has crawled, understood and connected to the rest of the web. A migration changes some or all of that at once: addresses change, internal links change, templates change how content renders, and metadata gets rebuilt by a new CMS with its own defaults. Each change alone is survivable. Shipping all of them blind, on one day, with no inventory of what mattered on the old site, is how a business wakes up to half its organic revenue gone.

The failure modes we see most, across replatforms and redesigns:

• URLs changed without redirects, or redirected in bulk to the homepage instead of to the matching page.
• Pages that earned traffic quietly dropped because nobody knew they earned it.
• Internal links still pointing at old URLs, burning crawl equity through redirect chains.
• Metadata and structured data replaced by CMS defaults.
• The new theme rendering key content client-side, or noindex tags surviving from the staging site.
• The staging domain itself getting indexed before launch.

Phase 1: benchmark before anything moves

Freeze the before-state while the old site is still live. This is the migration's evidence packet:

• A full crawl of the current site: every URL, title, meta description, canonical, status code.
• Search Console exports: queries, clicks, impressions and positions by page, over at least 90 days.
• Analytics by landing page, so revenue-earning pages are named, not assumed.
• Backlink targets: which URLs external sites actually link to.
• Current sitemap and index coverage.

Sort the URL inventory by commercial value. The pages with clicks, conversions or backlinks are the protected list; they migrate with a mapped destination or they don't migrate at all until one exists.

Phase 2: map one-to-one

Build the redirect map as a spreadsheet with two columns and no shortcuts: old URL, new URL that serves the same intent. Pattern rules can handle structured sections (products, categories), but every protected-list URL gets checked by hand. A redirect to a vaguely related page or the homepage tells Google the old page's topic no longer exists, and rankings follow it out the door.

While mapping, decide deliberately what dies. Thin pages, expired products and duplicate tag pages can be culled during a migration, but cull with a reason recorded per URL, and let genuinely dead pages return 410 or 404 rather than dragging every corpse across.

Phase 3: protect the launch

• Keep staging blocked from crawlers, and remove that block from the production build. Both directions of this mistake happen constantly.
• Carry titles, meta descriptions, canonicals and structured data over explicitly. Audit what the new CMS generates by default.
• Update internal links to point at final URLs, not through redirects.
• Ship the redirect map as server-side 301s, live from the first minute.
• Keep the old sitemap available briefly and submit the new one, so Google finds the redirects fast.

Phase 4: verify like you mean it

Launch day is the midpoint, not the finish. In the first 48 hours: crawl the new site in full, request the protected list's redirects live and confirm each returns a single 301 to the right destination, check rendering of key templates as Googlebot sees them, and confirm the accidental-noindex count is zero. Then watch Search Console's coverage and performance reports weekly, comparing the same page cohort against the frozen benchmark.

Expect some volatility for a few weeks while Google re-crawls and reconciles. What you should not accept as normal: a protected-list page with no traffic four weeks in, coverage errors trending up, or queries that moved to a competitor rather than to your new URL. Each of those has a findable cause, and the benchmark is what makes it findable. The diagnostic method in our post-update audit guide applies here unchanged: classify the loss before touching anything.

Replatforming and the AI-answer surface

Migrations now have a second audience. ChatGPT, Gemini, Perplexity and Google's AI features retrieve and cite pages, and a migration that breaks URLs breaks those citations too. Keep the facts AI systems quote (pricing, services, locations, proof) in readable HTML on stable URLs, and track AI citations as their own observation before and after the move. Our guide to AI search metrics covers the fields worth recording.

How we run migrations at Searchmaxxed

Searchmaxxed sells this as a fixed-scope product because the method is repeatable: the Agentic Migration. We run the benchmark, build and hand-check the redirect map, oversee the technical launch, then verify the live result and measure the same cohort until it's stable, inside the same Managed Search Loop discipline we run for ongoing clients: frozen baseline, one accountable change set, live verification, measured follow-up. If the migration is part of a bigger rebuild, the Agentic Website is the version where the new site is designed to out-cover the old one, not just preserve it.

Pricing for the migration product is public: A$3,000 one-off, with the full scope on the pricing page.

FAQs

What is an SEO migration?

An SEO migration is the process of preserving search rankings, traffic and indexing signals while a website changes platform, design, domain or structure. It wraps the technical move in benchmarking, URL mapping, redirects and post-launch verification.

What is a platform migration?

A platform migration moves a site between systems, for example WordPress to Shopify or a legacy CMS to a modern stack. URLs, templates, metadata and rendering usually all change, which is why it carries full SEO-migration risk even when the design looks the same.

How long does it take to recover rankings after a migration?

A clean migration typically settles within several weeks as Google re-crawls the redirects. Prolonged losses almost always trace to unmapped URLs, lost internal links, rendering problems or culled content, which is a diagnosis job, not a waiting job.

Do 301 redirects preserve rankings?

A one-to-one 301 to a page serving the same intent preserves the signal as well as anything can. Chains, loops and bulk redirects to the homepage do not. Redirects also need to stay in place long-term, not be removed after a few months.

Should I migrate and redesign at the same time?

It multiplies risk, because a traffic change can no longer be attributed to one cause. If you must combine them, keep URLs stable where possible and be twice as strict about the benchmark and verification phases.

Can I delete old pages during a migration?

Yes, deliberately. Cull thin or dead pages with a recorded reason per URL and let them 404 or 410. Never delete a page with clicks, conversions or backlinks without a mapped replacement.

What is the 80/20 of migration safety?

The redirect map for pages that actually earn traffic and links. Most migration loss comes from a small set of valuable URLs that moved without a correct forwarding address.

Does a migration affect AI answers and citations?

Yes. Answer engines cite URLs; break the URL and the citation dies. Stable URLs, readable HTML facts and consistent entity details protect the AI-answer surface through the move.

What does an SEO migration cost?

Australian agencies price migration support anywhere from a few thousand dollars to five figures depending on site size. Searchmaxxed's Agentic Migration is a public A$3,000 fixed scope; complex multi-site consolidations need custom scoping.

What's the single biggest migration mistake?

Launching without the frozen benchmark. Every other mistake is recoverable if you can see exactly what the old site had; none of them is diagnosable if you can't.

Next step

If a replatform, redesign or domain change is coming, get the benchmark done before the developers start. LET'S TALK and we'll scope the migration, or see the Agentic Migration on the pricing page.