How to prepare Search Console before a migration | Lillian Purge

How to prepare Search Console before a migration

I have worked on a wide range of website migrations over the years, from small business sites and ecommerce platforms through to education, public sector, and content-heavy publishers, and in my opinion preparing Google Search Console properly before a migration is one of the most important steps that is also one of the most commonly rushed or skipped. When that happens, teams lose visibility at the exact moment they need clarity most.

A site migration is not just a technical exercise. It is a period where Google is actively reassessing your site, your URLs, your structure, and your signals. Search Console is the one place where you can see that reassessment happening. If it is not prepared correctly before the migration, you end up flying blind. You may not notice problems early. You may misinterpret what you are seeing. Worse still, you may assume everything is fine until rankings and traffic drop weeks later.

In this article I want to explain how to prepare Search Console before a migration in a way that gives you confidence, control, and context. This is written from first-hand experience of migrations that went smoothly because Search Console was prepared properly, and migrations that went badly because it was not. Everything here is grounded in real-world UK SEO practice and focused on practical steps rather than theory.

Why Search Console preparation matters before anything changes

Before a migration, Search Console is your baseline.

It is the record of how Google currently understands your site. Which pages are indexed. Which queries drive impressions. Which URLs attract clicks. How crawling behaves. Where errors already exist.

Once the migration happens, that baseline is gone. You cannot recreate it accurately after the fact. From experience, teams that skip this step often struggle to answer simple questions later, such as what exactly changed, or whether a drop is migration-related or seasonal.

Preparing Search Console before a migration is about capturing truth before disruption.

Understanding Search Console’s role in a migration

Search Console does not migrate your site for you. It does not automatically protect rankings. What it does is give you visibility into how Google processes the changes you make.

Google Search Console shows you how Google crawls, indexes, and surfaces your pages. During a migration this behaviour changes rapidly. Pages drop out of the index. New URLs appear. Redirects are followed. Canonicals are reassessed.

If Search Console is not set up correctly beforehand, you lose the ability to see these changes clearly.

Ensuring you have the right property type

The first and most critical preparation step is confirming that you are using the correct property type.

For migrations, a Domain property is almost always the right choice. It gives you a complete view of all protocols, subdomains, and URL variations under the domain.

From experience relying only on URL prefix properties before a migration leads to fragmented data. You may miss how Google is interacting with alternative versions of your URLs, which is exactly the kind of behaviour that becomes important during migrations.

If you do not already have a Domain property verified, do this well before the migration.

Verifying access and permissions

Before a migration, confirm who has access to Search Console and at what level.

Too often only one person has full permissions. If that person is unavailable during the migration, decision-making slows down or stops entirely.

From experience migrations are smoother when multiple trusted stakeholders have full or owner access. This allows developers, SEO leads, and project managers to view the same data and respond quickly.

Do not wait until launch day to discover you cannot see the reports you need.

Capturing performance benchmarks

One of the most valuable things you can do before a migration is capture performance benchmarks.

Look at at least the last three to six months of data in the Performance report. Export impressions, clicks, average position, and top queries.

From experience this benchmark becomes your reference point. When something changes after migration, you can compare against known patterns rather than guessing.

This is especially important for sites with seasonality, where month-on-month comparisons can be misleading.

Identifying top-performing pages and queries

Before migrating, identify which pages matter most.

These are not always the pages you expect. Use Search Console to find pages with the highest impressions and clicks, not just the highest conversions.

From experience these pages deserve special attention during migration. Their URLs, internal links, and redirects should be handled with care.

If you lose visibility on these pages, the impact is felt quickly.

Reviewing current index coverage

The Indexing or Pages report shows you what Google currently indexes and what it excludes.

Before migration, review this report carefully.

Note which pages are indexed, which are excluded intentionally, and which exclusions may already be problems. This gives you a clear picture of your site’s health going into the migration.

From experience migrating an already messy index without understanding it first multiplies problems rather than resets them.

Documenting existing errors and warnings

Every site has some level of errors or warnings in Search Console.

Before migration, document what already exists. This includes crawl errors, mobile usability issues, and Core Web Vitals warnings.

From experience this prevents misattributing old issues to the migration later. If a warning existed before launch, it is not caused by the migration.

Clear documentation avoids unnecessary panic and finger-pointing.

Checking mobile usability status

Mobile usability is particularly sensitive during migrations.

Design changes, template updates, and new layouts often introduce mobile issues that were not present before.

From experience knowing your current mobile usability status helps you spot regressions quickly. If mobile issues appear after migration that were not present before, you know where to focus.

Reviewing Core Web Vitals trends

Core Web Vitals should be reviewed before migration, not just after.

Look at overall trends rather than individual URLs. Is performance stable, improving, or already struggling.

From experience migrations often affect performance. If Core Web Vitals were already weak, migration can push them into problem territory.

Knowing your starting point helps you interpret changes accurately.

Auditing existing internal linking signals

Search Console’s Links report shows how Google sees your internal linking.

Before migration, review which pages are most linked internally.

From experience these pages are perceived as important by Google. Losing internal links to them during migration can cause disproportionate ranking drops.

This insight should inform migration planning, especially navigation and content restructuring.

Reviewing external link profiles by page

The Links report also shows which pages attract external links.

Before migration, identify pages with strong backlink profiles.

From experience these pages should be protected carefully. URL changes without correct redirects or canonical alignment can dilute years of earned authority.

Search Console helps you prioritise which URLs must be handled perfectly.

Checking canonical interpretation

Search Console often shows which canonical Google has selected for a page.

Before migration, review these selections, especially for pages where Google’s chosen canonical does not match your intended one.

From experience unresolved canonical issues before migration often become worse afterwards.

Fixing or documenting them in advance prevents confusion later.

Understanding current crawl behaviour

The Crawl Stats report shows how often Google crawls your site and which types of requests it makes.

Before migration, review this data to understand normal crawl levels.

From experience sudden changes in crawl rate after migration are expected, but knowing your baseline helps you distinguish healthy reprocessing from potential problems.

Ensuring XML sitemaps are clean and current

Before migration, make sure your existing XML sitemaps are accurate.

They should include only canonical, indexable URLs that actually exist.

From experience migrating with messy sitemaps creates unnecessary noise. Google continues requesting URLs that are about to change, increasing crawl load during a sensitive period.

Clean sitemaps reduce friction during transition.

Removing obsolete sitemaps

Many sites accumulate old sitemaps over time.

Before migration, remove obsolete or redundant sitemaps from Search Console.

From experience leaving them in place causes Google to crawl URLs that should no longer matter, slowing down discovery of new ones.

Simplifying inputs before migration leads to cleaner outputs after.

Aligning Search Console with analytics tracking

Search Console and analytics should be aligned before migration.

Confirm that domains, protocols, and filters match. Discrepancies between the two are easier to resolve before changes than after.

From experience misalignment creates confusion during migration analysis, especially when traffic appears to drop in one tool but not the other.

Creating annotation and documentation habits

Search Console does not have built-in annotations, but you should create your own documentation.

Record the planned migration date, scope, and expected changes.

From experience this documentation is invaluable when reviewing data weeks or months later. Memory fades. Data remains.

Clear notes prevent misinterpretation.

Setting up the new property in advance

If the migration involves a new domain or subdomain, set up the new Search Console property in advance.

Verify ownership, even if the site is not live yet.

From experience doing this early allows you to submit sitemaps immediately after launch and monitor indexing from day one.

Waiting until after launch wastes critical early insight.

Preparing for temporary fluctuations

Part of preparing Search Console is preparing your mindset.

Migrations almost always cause temporary fluctuations. Pages drop out of the index. Impressions dip. Rankings move.

From experience teams that expect immediate stability often overreact.

Preparing Search Console properly helps you distinguish normal reprocessing from genuine issues.

Deciding what success looks like

Before migration, define what success looks like in Search Console terms.

Is it returning to baseline impressions within a certain time. Is it seeing new URLs indexed cleanly. Is it maintaining performance on key pages.

From experience having agreed criteria prevents emotional decision-making when data shifts.

Understanding the limitations of Search Console data

Search Console data is sampled and delayed.

It does not show everything instantly. It does not always show exact numbers.

From experience understanding these limitations prevents unnecessary stress. You are looking for trends and patterns, not precision.

Preparation includes setting realistic expectations.

Communicating preparation to stakeholders

If multiple stakeholders are involved, share what you have prepared in Search Console.

Explain what will be monitored, what changes are expected, and what would trigger action.

From experience this transparency builds trust and reduces panic when metrics fluctuate.

Avoiding last-minute setup

One of the worst mistakes is setting up Search Console properly after the migration has already started.

At that point you have already lost your baseline.

From experience preparation should happen weeks, not days, before launch.

Search Console is not a fire extinguisher. It is a monitoring system.

Using Search Console to reduce migration risk

When prepared properly, Search Console reduces migration risk significantly.

You can spot redirect failures early. You can see indexing gaps. You can track which pages Google is prioritising.

From experience this visibility turns migrations from stressful events into manageable processes.

Common preparation mistakes to avoid

The most common mistakes I see include relying only on URL prefix properties, failing to export baseline data, ignoring internal links, and assuming sitemaps will fix everything.

Avoiding these mistakes is often the difference between a smooth migration and months of recovery work.

Preparing for post-migration monitoring

Preparation does not end at launch.

Before migration, plan how often Search Console will be checked after launch, and who is responsible.

From experience daily checks in the first week, then weekly reviews, strike a good balance between vigilance and overreaction.

My practical advice from experience

If I were advising a team about to migrate a site, I would say this.

Set up a Domain property well in advance.
Export and understand your baseline data.
Identify and protect your most important pages.
Clean up existing issues before adding new complexity.
Prepare documentation and expectations, not just tools.

Search Console preparation is not optional. It is foundational.

Final thoughts

I think preparing Search Console before a migration is one of the most valuable investments of time you can make.

It does not prevent every issue, but it gives you clarity, confidence, and control when things change.

From experience migrations that are supported by well-prepared Search Console setups recover faster, suffer less volatility, and generate far less stress.

SEO migrations are not about guessing. They are about observing and responding. Search Console is where that process begins.