site migration best practice | Lillian Purge

site migration best practice

I run a digital marketing agency and I also own businesses where a website going down or losing visibility is not an inconvenience, it is a direct hit to revenue, enquiries and trust. From experience, site migrations are one of the highest-risk activities in SEO. Done well, they unlock growth, improve performance and future-proof a business. Done badly, they can wipe out years of hard-earned visibility almost overnight.

In my opinion, most site migration problems are not caused by technical complexity. They are caused by underestimating what a migration actually is. A site migration is not just moving pages from one place to another. It is changing how search engines like Google understand your entire business.

This article explains site migration best practice in clear practical terms. It is written from real-world experience migrating hundreds of sites across industries including ecommerce, local services, education and regulated sectors. It focuses on what actually matters, what commonly goes wrong and how to approach migrations calmly and methodically so you protect traffic, rankings and trust.

what a site migration really means in seo terms

A site migration is any significant change that affects how search engines crawl, index or interpret your website.

From experience, many people think a migration only counts when you change domain names. In reality, migrations include far more than that. Changing URLs, changing site structure, changing CMS platforms, switching from HTTP to HTTPS, redesigning navigation, merging content or even large scale content rewrites can all trigger migration-level risk.

In SEO terms, a migration resets assumptions. Google has to relearn what pages exist, how they relate to each other and which ones matter most. If you do not guide that process clearly, Google fills in the gaps itself, often in ways you do not want.

why migrations are risky even when intentions are good

Most site migrations are started with positive intentions.

From experience, businesses migrate because they want a better design, faster performance, improved conversion or easier management. The problem is that SEO risk is rarely visible during planning.

You can build a beautiful new site that performs perfectly from a design perspective and still lose half your organic traffic because search engines no longer recognise it in the same way.

SEO risk comes from change, not from mistakes alone. Even correct changes need to be managed carefully.

the biggest myth about site migrations

The biggest myth I encounter is this.

If we do everything right, rankings will not change.

From experience, this is unrealistic. Even perfect migrations usually cause short term fluctuation. Rankings may dip temporarily, impressions may drop and traffic may wobble.

The goal of site migration best practice is not zero movement. The goal is controlled movement and fast recovery.

Anyone promising no impact at all is either inexperienced or not being honest.

migrations fail most often at the planning stage

Most SEO damage during migrations happens before a single line of code is moved.

From experience, failures usually begin with poor planning. SEO is brought in too late, URL decisions are made without mapping, content is removed without evaluation and timelines are rushed.

Once a site is live, fixing these mistakes is far harder and far more expensive.

In my opinion, planning is the most important phase of any migration. It deserves as much time as development.

understanding the type of migration you are doing

Not all migrations are equal.

From experience, the level of risk depends on what is changing. A simple HTTPS migration is lower risk than a full domain and CMS change combined with content restructuring.

Understanding the scope of change helps set the right expectations and safeguards.

If multiple major changes are happening at once, risk multiplies, not adds.

why url changes are the highest risk element

URLs are the primary identifiers for pages in search engines.

From experience, changing URLs is the single most risky part of a migration. When a URL changes, Google treats it as a new page unless guided otherwise.

If URLs change without proper redirection, all accumulated authority and relevance tied to the old URL is lost.

Even small URL changes such as adding or removing trailing slashes can cause problems if not handled correctly.

the role of 301 redirects and why they matter

301 redirects are the backbone of migration SEO.

From experience, a correct 301 redirect tells search engines that a page has permanently moved and that its value should be transferred to the new location.

Without redirects, Google sees a dead page and a new page, not a continuation.

Redirects should always be one-to-one where possible. Every important old URL should point directly to its most relevant new equivalent.

Redirect chains and blanket redirects create confusion and loss of value.

why redirect mapping must be done manually

Automated redirects are tempting.

From experience, automatically redirecting everything to the homepage or category pages is one of the fastest ways to lose rankings.

Search engines expect relevance continuity. A page about boiler repair should redirect to a page about boiler repair, not to a generic services page.

Manual redirect mapping forces you to think about content relevance and intent. This is not busywork, it is critical SEO protection.

content audits should happen before migrations

Content audits are often skipped.

From experience, this is a mistake. Before migrating, you need to understand what content exists, what performs well and what is expendable.

Removing content blindly because it feels old or irrelevant can remove pages that still attract traffic or authority.

A proper audit looks at traffic, impressions, backlinks and relevance. Decisions are then made intentionally, not emotionally.

why deleting content is riskier than improving it

Many migrations involve content reduction.

From experience, deleting content entirely carries more risk than updating or consolidating it.

If a page has any search history or external links, deleting it without replacement can cause a drop in visibility that affects the whole site.

In many cases, improving content or merging it into a stronger page with proper redirects preserves value better than removal.

site structure changes affect how google understands importance

Site structure tells search engines what matters.

From experience, migrations often change navigation, internal linking and hierarchy without considering SEO implications.

If important pages become harder to reach or are buried deeper, their perceived importance drops.

Search engines rely heavily on internal linking to understand priority. A new structure must preserve or improve that signal.

internal linking must be reviewed post migration

Internal links are often broken or outdated after migrations.

From experience, relying solely on redirects to fix internal links is poor practice. Redirects should be a safety net, not a crutch.

Internal links should be updated to point directly to new URLs. This strengthens crawl efficiency and relevance.

Clean internal linking is a strong post migration signal of quality.

why canonical tags must be handled carefully

Canonical tags tell Google which version of a page is preferred.

From experience, migrations often introduce incorrect or duplicated canonical tags, especially when templates change.

Incorrect canonicals can cause Google to ignore new pages entirely or continue favouring old URLs.

Every canonical should be reviewed to ensure it points to the correct live page.

hreflang and international sites increase complexity

International sites add another layer of risk.

From experience, hreflang errors during migrations can cause pages to rank in the wrong countries or disappear altogether.

Hreflang relationships must be preserved exactly. Even small mistakes can break language targeting.

International migrations should always be tested thoroughly before launch.

technical seo checks must happen before and after launch

Technical SEO is not optional during migrations.

From experience, issues like noindex tags left on live pages, blocked resources, broken sitemaps or crawl errors cause major visibility loss.

A full technical audit should be done on staging and again immediately after launch.

Do not assume that what worked on staging is still correct on live.

xml sitemaps are migration accelerators not guarantees

Sitemaps help Google discover URLs.

From experience, updated XML sitemaps should be submitted immediately after launch to reflect new URLs.

This does not force indexing but it improves crawl efficiency.

Sitemaps should include only canonical, indexable URLs. Including junk URLs creates noise.

the role of google search console in migrations

Google Search Console is essential during migrations.

From experience, it is the primary tool for monitoring indexing, errors and performance changes.

Search Console should be set up for the new site immediately. Old properties should be kept active to monitor legacy behaviour.

Ignoring Search Console during a migration is like flying blind.

performance monitoring must focus on patterns not days

After launch, performance monitoring often causes panic.

From experience, daily fluctuations are normal. What matters is trend direction over weeks and months.

Initial drops followed by gradual recovery are common even in good migrations.

Judging success too early leads to unnecessary changes that can make things worse.

why traffic dips do not always mean failure

Traffic dips are emotionally hard.

From experience, many migrations show a temporary dip as Google reprocesses the site.

If fundamentals are correct, traffic usually returns and often exceeds previous levels.

The key is not to overreact. Stability and patience are critical.

content parity matters more than design parity

New designs often change layouts.

From experience, removing large amounts of text or explanatory content for aesthetic reasons hurts SEO.

Search engines value content depth and context. A visually cleaner page that lacks substance may perform worse.

Design should enhance content, not replace it.

page titles and headings should not be rewritten casually

Titles and headings are strong relevance signals.

From experience, changing them drastically during migrations can confuse search engines.

Unless there is a clear strategic reason, titles should be preserved or evolved carefully.

Wholesale rewrites during migration increase risk unnecessarily.

mobile performance must be tested thoroughly

Google uses mobile first indexing.

From experience, migrations often introduce mobile issues that are not obvious on desktop.

Text size, spacing, navigation and load speed must be tested on real devices.

Mobile problems cap recovery and can suppress rankings long term.

page speed improvements should be real not theoretical

Many migrations promise faster performance.

From experience, promised improvements do not always materialise.

Actual page speed should be measured before and after. Slower sites post migration often struggle to recover.

Speed is a user experience and SEO factor. Improvements must be tangible.

security changes must be validated

HTTPS migrations are common.

From experience, mixed content issues, certificate errors or incorrect redirects undermine trust and indexing.

Security warnings reduce click through rates immediately.

HTTPS must be implemented cleanly and completely.

analytics must be reconfigured correctly

Analytics often breaks during migrations.

From experience, tracking codes are lost, duplicated or misconfigured.

Without accurate data, evaluating migration success becomes impossible.

Analytics should be checked immediately after launch.

legacy urls can linger longer than expected

Old URLs often continue to receive traffic or links.

From experience, redirects must remain in place long term, often for years.

Removing redirects too early causes slow leaks in authority.

Redirects are not temporary fixes. They are part of site history.

backlinks should be reviewed and preserved

Backlinks are a major authority signal.

From experience, migrations that do not account for backlink destinations lose value.

Important linked pages should be prioritised in redirect mapping.

Where possible, high value backlinks can be updated manually by contacting linking sites.

why migrations often expose hidden seo problems

Migrations act like stress tests.

From experience, issues that existed quietly before often surface afterwards.

This is not always because the migration was bad, but because Google is reassessing the site.

Addressing these issues strengthens the site long term.

communication matters during migrations

Internal communication is often overlooked.

From experience, teams panic when traffic dips without understanding what is happening.

Clear communication about expected behaviour prevents knee jerk decisions.

Stakeholders should be educated on realistic timelines.

when to intervene and when to wait

Knowing when to act is critical.

From experience, genuine technical errors should be fixed immediately. Normal ranking fluctuations should be observed calmly.

Over intervention often causes more harm than good.

Patience is part of best practice.

migrations are opportunities as well as risks

Migrations are not just defensive.

From experience, they are opportunities to improve structure, clarity and performance.

When handled well, migrations often lead to long term gains beyond recovery.

This requires intentional optimisation, not just preservation.

seo migrations are business migrations

A site migration affects more than SEO.

From experience, it affects sales journeys, trust perception and brand clarity.

SEO best practice must align with business goals, not exist in isolation.

This alignment reduces risk and increases upside.

why cutting corners costs more later

Rushed migrations feel cheaper.

From experience, they almost always cost more in lost traffic and recovery work.

Proper planning and execution is more efficient than emergency fixes.

SEO debt accumulates quickly after poor migrations.

building a migration checklist mindset

Best practice comes from discipline.

From experience, successful migrations follow checklists, reviews and sign offs.

This reduces reliance on memory and assumptions.

Process protects performance.

post migration seo is as important as pre migration seo

The work does not stop at launch.

From experience, monitoring, fixing and optimising post launch is where recovery is secured.

Ignoring post migration SEO leads to slow decline.

Migration is a phase, not an event.

why site migrations should be rare not routine

Frequent migrations increase risk.

From experience, unnecessary platform changes or redesigns cause cumulative damage.

Sites should evolve incrementally where possible.

Stability builds trust.

final thoughts

From experience, site migration best practice is about respect. Respect for how search engines learn, respect for how users behave and respect for the value your existing site has built over time.

If there is one key takeaway from this article, it is this. A site migration is not a reset button, it is a continuation.

When migrations are planned carefully, executed methodically and monitored patiently, they protect visibility and often unlock growth.

When they are rushed or treated casually, they undo years of effort in weeks.

Approach migrations with humility, discipline and clarity, and SEO will reward you for it.