Migrations without losing everything you’ve built.
Replatforming, redesigning, or restructuring is where ranking equity tends to die — quietly, and often a fortnight after launch. We do the URL mapping, the redirect choreography, and the post-launch monitoring so your accumulated search authority arrives intact at the new front door.
Eight sub-techniques.
One careful handover.
An SEO migration is not a launch task you bolt onto a redesign. It is a parallel project with its own checklist, its own timeline, and its own failure modes — most of them invisible until rankings start sliding.
Every migration we run begins weeks before launch with a full crawl of the old site, follows a documented redirect map through cutover, and continues for at least four to six weeks of post-launch monitoring before we close the engagement.
URL Mapping
FoundationalBefore anything else, a full inventory. We crawl the existing site end to end, extract every indexable URL, cross-reference it with Search Console, Ahrefs, and Google Analytics to identify which pages are earning traffic, links, and rankings, and then build a one-to-one mapping of every old URL to its new equivalent on the destination site. The map becomes the single source of truth for the migration — every redirect, every internal link rewrite, and every post-launch verification step traces back to it. Pages with meaningful equity are never collapsed without a deliberate decision and a documented destination.
Redirect Planning
Equity transferEvery old URL needs a 301 redirect to its closest new equivalent — not a 302, not a soft redirect, not a redirect chain that hops through three intermediate URLs before landing. We plan the redirect rules at the server or CDN layer, test them against the URL map before launch, and keep them in place permanently. Where one-to-one mapping is genuinely impossible, we route to the most relevant parent category rather than dumping orphan URLs at the home page — a common shortcut that loses most of the link equity in transit. We also clean up the legacy redirect chains the previous site had accumulated, so the new redirects do not inherit them.
Content Preservation
EditorialRedesigns are also a chance — and often a temptation — to rewrite or trim the existing copy. We push back where the existing content is what is earning the rankings. The keyword cues, internal links, headings, and supporting paragraphs that made a page rank in the first place need to survive the rebuild, even if the design around them changes. Where copy genuinely needs to be refreshed, we refresh in place after the migration has stabilised, not as part of the cutover. This separates “did the redesign break things” from “did the rewrite break things” — two questions that are difficult to answer simultaneously.
Schema Migration
Machine-readableStructured data tends to be the first casualty of a platform change. The old site had Article schema, BreadcrumbList, FAQPage, LocalBusiness, Product, or Review markup tuned to its templates; the new platform either omits it, generates a different version, or implements it incorrectly. We audit the existing schema, port it to the new templates with the same coverage, validate every page type against Google’s structured-data tests, and confirm rich-result eligibility post-launch. For sites that depend on AI search visibility, this step is non-negotiable — schema is how LLMs decide which page to cite.
Post-Launch Monitoring
VerificationThe first 30 days after cutover are the diagnostic window. We watch Search Console daily for crawl errors, indexation drops, mobile-usability flags, and structured-data warnings. We track keyword rankings against the pre-migration baseline through Ahrefs and the position-tracking we set up before launch. We monitor server logs to confirm Googlebot is reaching the new URLs and not getting stuck in redirect loops. If something starts moving in the wrong direction, we catch it within days rather than discovering it the following month when the organic-traffic dashboard finally turns red.
Recovery Plans
ContingencyA short post-launch dip is normal — Google needs to recrawl and reprocess the new structure, and that takes time. A genuine ranking loss looks different, and we have a documented playbook for it. The recovery process starts with diagnosis: was a redirect missed, did a template lose its canonical tag, did internal links break, did robots.txt block the new URLs, did the staging site accidentally get indexed? Once the cause is identified, the fix is usually surgical. We have run this play often enough to know what to look at first and where the surprises tend to live.
Domain Changes
Re-brandMoving from one domain to another — a re-brand, a corporate restructure, a consolidation of multiple sites — is among the highest-risk migration scenarios because every URL changes at once. We handle the Search Console Change of Address process, configure a hostname-level 301 redirect rule that preserves the URL path, port the disavow file and link-acquisition history, update structured-data identifiers and social-graph tags, and notify the high-authority backlinks that matter. We have moved sites between domains in both English and Chinese markets without measurable equity loss; the discipline is the same.
HTTPS Transition
ProtocolMost modern sites already run on HTTPS, but a surprising number still have legacy HTTP redirects, mixed-content warnings, or HSTS configurations that miss subdomains. A clean HTTPS migration redirects every HTTP URL to its HTTPS counterpart at the server level, resolves mixed-content references in templates and content, configures HSTS with a sensible max-age, updates internal links and canonical tags to use the secure protocol, and verifies the HTTPS property in Search Console. For sites running both protocols by accident, we consolidate without breaking the link profile that has accumulated on the legacy URLs.
Crawl. Map.
Redirect. Watch.
Migrations succeed or fail in the four weeks before launch and the four weeks after. Our methodology is built around that reality — heavy preparation, deliberate cutover, and patient post-launch verification. The dramatic part is the launch itself; the unglamorous part is what makes the launch survive.
Pre-migration crawl and inventory
Weeks before cutover, we crawl the existing site, pull traffic and link data from Ahrefs and Search Console, and build the master URL map. We also baseline the current rankings, the existing schema coverage, and the redirect-chain inheritance. Without this baseline, “did rankings drop after migration” becomes an unanswerable question — and an unanswerable question is one that quietly resolves against you.
Redirect map before code freeze
The redirect map is delivered to the development team before the new site is feature-complete, not as an afterthought once launch is two days away. We test the rules against the staging environment, confirm every old URL resolves to the planned new one with a clean 301, and identify the edge cases — pagination, faceted URLs, parameter strings, language variants — that tend to slip through generic rewrite rules.
Cutover with monitoring already running
We do not switch DNS and walk away. The position-tracking, log monitoring, and Search Console verification are configured before launch so they start gathering data the moment the new site is live. Daily checks for the first two weeks; weekly checks for the next month; full reconciliation against the baseline at the 30 and 60-day marks. If something is going to go wrong, we want to be the ones who notice.
Patience for the recrawl window
Google takes time to recrawl, reprocess, and reflect a new site structure — typically two to six weeks for the indexation to stabilise. Short-term volatility is normal and not the same as a ranking loss. We separate the noise from the signal, advise against panicked rollbacks during the recrawl window, and only escalate when the diagnostic data confirms a real problem rather than the temporary turbulence every migration produces.
Anyone moving
a site that already ranks.
SEO migration is the right engagement for any business about to change its website meaningfully — new platform, new design, new domain, restructured architecture, or a consolidation of multiple sites into one. The smaller the existing search footprint, the lower the stakes; the larger the footprint, the more decisive the planning becomes.
A few recurring profiles where the migration is the moment everything is at stake.
- i Re-platforming projectsMoving from a legacy CMS to WordPress, from WordPress to a headless stack, from a custom build to a platform like Shopify or WooCommerce. The URL structure usually changes, the templates change, and the schema coverage has to be rebuilt from scratch.
- ii Re-brands and domain changesThe riskiest of all migrations because every URL on the site is a new URL. The redirect rule has to be precise at the path level, the Search Console Change of Address has to be filed, and the link-acquisition history needs to be ported deliberately.
- iii Redesigns with new information architectureA new site map collapses, splits, or renames pages. Without a careful URL map, equity gets stranded on URLs that no longer exist or fragmented across new pages that individually rank for nothing.
- iv Site consolidationsMerging two or three properties into one, sunsetting subdomains in favour of a single primary site, or absorbing an acquired company’s web presence. Each of these creates a many-to-one redirect map that needs care to consolidate equity rather than dilute it.
- v Migrations that have already gone wrongSites that launched without a redirect map, lost rankings in the first month, and need a recovery engagement. We can usually rebuild the missing redirects, restore the lost canonical signals, and recover most of the original positions — though prevention is always cheaper than recovery.
If your redesign or replatform is being driven by a web design agency that is not also handling SEO continuity, this is the engagement that fills that gap. The two run in parallel — the design-and-build team focuses on the new experience, and we make sure the search equity arrives at the new site intact. Where the build itself sits with us, see Web Design & Development for the full project picture.
Curious how Google sees your site?
Send us your URL. We’ll send back a Premium SEO Report, prepared by hand, within 48 hours — domain authority, keyword rankings, backlinks, competitor gap, and the migration-readiness checks worth running before any redesign begins.
No sales call required.
Migrations are where ranking gains quietly die. The redesign launches, the team celebrates, and four weeks later the traffic is gone — taken not by an algorithm but by a redirect that was never written.— The Aureole Practice —
Questions we get
about migration.
If a question is missing here, the contact link at the foot of the page goes straight to the person who would answer it. No ticket queues, no funnels.
i When in the redesign timeline should an SEO migration begin?
ii How long should we expect rankings to be unstable after launch?
iii Can you handle the migration even if a different agency is doing the redesign?
iv What if rankings have already dropped after a recent migration?
noindex, an unprotected staging environment that got indexed, or a content rewrite that erased the keyword signals the page used to carry. Once the cause is identified, most fixes are straightforward — the harder part is the patience to let Google recrawl and re-credit the corrected URLs, which can take several more weeks after the fixes are deployed. We are honest about what is recoverable and what is not before any work begins.Where migration
fits in the whole.
An SEO migration sits inside a larger redesign or replatforming project. The link below returns to the parent service; the pills extend laterally to sister sub-disciplines and to the build-side service that often runs in parallel.
Parent service
Sister sub-disciplines
Adjacent services & platforms
Ready to migrate
without losing ground?
Start with a free SEO report — or reach out to scope a migration engagement around your redesign timeline. Either way, you’ll hear back from the team that does the work, not a sales department.