Google Search Console Site Migration: How to Use the Change of Address Tool

You've moved your website to a new domain and now you need Google to understand what happened. Without properly notifying Google through Search Console, you risk losing months of ranking progress while the search engine slowly figures out your site has moved. The Change of Address tool exists specifically to accelerate this transition, but only if you use it correctly and at the right time in your seo site migration process.

This guide walks through exactly when and how to use Google Search Console's Change of Address tool, what happens behind the scenes when you submit the request, and the critical prerequisites that determine whether Google accepts your migration signal. We'll also cover the less-discussed scenarios where this tool doesn't apply and what to do instead.

What Is the Google Search Console Change of Address Tool?

The Change of Address tool is a specific feature within Google Search Console designed for site-level domain migrations. It tells Google that your entire site has permanently moved from one domain to another.

Think of it as filing a forwarding address with the post office. You're notifying Google that all future search traffic should be directed to your new location, and you're asking them to transfer the search equity from your old domain to the new one.

When This Tool Actually Works

The Change of Address tool only applies to complete domain changes where:

• You're moving from one root domain to another (example: oldsite.com to newsite.com)

• You're changing protocols (http:// to https://)

• You're switching subdomains (www.site.com to site.com or vice versa)

• Every page on the old domain has a corresponding destination on the new domain

• You control both domains and have verified both properties in Search Console

At Sharkly, we've seen businesses attempt to use this tool for partial migrations, subdirectory moves, or content consolidations. Those scenarios require different approaches entirely.

When You Cannot Use This Tool

The Change of Address tool explicitly does not work for:

• Moving only part of your site (example: oldsite.com/blog to newsite.com/resources)

• Changing URL structure while staying on the same domain (example: site.com/page to site.com/new-page)

• Merging multiple sites into one

• Moving from a subdirectory to a subdomain or vice versa on the same root domain

For these situations, you still need redirects and proper URL mapping, but Google treats them as standard crawl and reindex operations rather than address changes.

What Must Be in Place Before You Submit a Change of Address

The Change of Address tool is not a migration strategy. It's a notification mechanism that only works after you've completed the actual technical migration work.

Verified Properties in Search Console

You must have both the old domain and the new domain verified as separate properties in Search Console. Google won't let you submit a change of address unless it can confirm you control both sites.

This means adding and verifying the new domain property weeks before your migration goes live, not the day you flip the switch.

Server-Level 301 Redirects

Every URL on your old domain must redirect to the corresponding URL on your new domain using permanent 301 redirects. Google's crawler needs to follow these redirects and confirm they're working before the Change of Address tool will process your request.

Redirect mapping is where most migrations fail. You need one-to-one URL correspondence wherever possible. The internal link preservation site migration process depends on maintaining these relationships throughout your site architecture.

New Site Must Be Live and Crawlable

Your new domain needs to be publicly accessible with no crawl blocks, no noindex tags on migrated pages, and no authentication walls preventing Googlebot from accessing content. If your new site returns 404 errors or shows "coming soon" pages, the change of address will fail.

We recommend running a full crawl of your new domain using Screaming Frog or a similar tool before submitting the change of address. Look for server errors, redirect chains, and missing pages that should have migrated.

How Do You Submit a Change of Address in Google Search Console?

Once your redirects are live and both properties are verified, the actual submission process takes less than two minutes.

Step-by-Step Submission Process

Log into Google Search Console and select the property for your old domain. Navigate to Settings in the left sidebar, then scroll to the Change of Address section.

Click "Submit a change of address" and Google will present a dropdown showing all verified properties you own. Select your new domain from this list.

Google will run validation checks immediately. The tool verifies that:

• Both properties are verified under your account

• 301 redirects are in place from old URLs to new URLs

• The new site is accessible and returning 200 status codes

• No existing change of address is active for either property

If validation passes, click Submit. If it fails, Google provides specific error messages explaining what needs to be fixed.

Timing Your Submission

Submit the change of address immediately after your redirects go live. Don't wait days or weeks. The sooner you notify Google, the faster they'll begin transferring signals from your old domain to your new one.

Understanding when is the best time to launch your migration affects everything from traffic impact to recovery speed, but once you've launched, the Change of Address tool should be one of your first actions.

What Happens After You Submit a Change of Address Request?

Google doesn't instantly flip a switch and transfer all your rankings. The Change of Address tool accelerates the natural process of discovering and processing your redirects, but it still takes time.

Signal Transfer Timeline

Over the next several weeks, Google will:

• Prioritize crawling your old domain to discover all redirects

• Index the corresponding pages on your new domain faster than normal

• Begin showing your new domain URLs in search results instead of old ones

• Transfer ranking signals, backlink equity, and other quality indicators from old URLs to new URLs

The timeline varies based on your site's size and crawl budget. Small sites with strong crawl frequency may see the transition complete in 2-3 weeks. Larger sites can take 2-3 months for full signal transfer.

What You'll See in Search Results

During the transition period, search results become messy. You'll see a mix of old and new URLs appearing in Google. Some queries will show your new domain while others still display the old one.

This is normal. Google updates its index incrementally as it recrawls and reprocesses your redirects. The Change of Address tool tells Google to treat this as a unified entity rather than two separate sites competing for rankings.

Changes to Search Console Data

Your Search Console reports will show declining impressions and clicks for the old property as Google transfers traffic to the new domain. The new property should show corresponding increases.

Total traffic across both properties combined often dips slightly during migration, then recovers once the transition completes. At Sharkly, we've analyzed thousands of migrations and found that sites with proper redirect mapping and immediate Change of Address submission typically recover to pre-migration traffic levels within 60-90 days.

How Long Does a Change of Address Request Last?

Google maintains the change of address mapping for 180 days. After six months, the tool automatically expires and Google treats the two domains as separate entities again.

This doesn't mean your redirects stop working. Your server-level 301 redirects should remain in place indefinitely. The 180-day window refers only to the preferential treatment Google gives to crawling and processing those redirects.

Why the Six-Month Window Exists

Six months gives Google ample time to discover all your redirects, transfer ranking signals, and update its index. After that period, the redirects themselves carry the signal transfer burden without needing special handling from the Change of Address tool.

If you're still seeing the old domain appear in search results after 180 days, the problem isn't the expired Change of Address. It's either incomplete redirect coverage or technical issues preventing Google from following your redirects properly.

Can You Cancel a Change of Address Request?

Yes. If you need to reverse a migration or made a mistake, you can cancel the change of address through the same Settings panel where you submitted it.

Navigate to Settings in your old domain property, find the active change of address notification, and click Cancel. Google stops preferentially crawling redirects and treating the domains as a unified entity.

What Happens After Cancellation

Canceling doesn't undo signal transfer that already occurred. Pages on your new domain that already received ranking signals will keep them. Google simply stops accelerating the remaining transfer process.

If you're genuinely reversing a migration and moving content back to the original domain, you'll need to implement redirects in the opposite direction and potentially submit a new change of address pointing from new to old.

This scenario is rare and messy. Avoid it by thoroughly testing your migration before making it live.

What Is the "Other Sites Moving to This Site" Notification?

Sometimes you'll see a message in Search Console stating "Other sites moving to this site" with a list of domains. This appears in your new domain's property when Google detects incoming redirects from other domains.

This notification is informational. It confirms Google has recognized the migration signals even if you haven't submitted a formal Change of Address request.

When This Appears Without Action on Your Part

If you're consolidating multiple old domains into a single new domain, you might see several domains listed here. Each one represents a separate set of redirects Google discovered.

For true site consolidations involving multiple source domains, you cannot use the Change of Address tool. That tool only supports one-to-one domain migrations. Instead, rely on proper 301 redirects and Google's natural crawl and index update process.

What If You're Migrating URL Structure Without Changing Domains?

Many migrations involve restructuring URLs while keeping the same domain. Examples include moving from HTTP to HTTPS on the same domain, changing URL parameters, or reorganizing site architecture.

The Change of Address tool doesn't apply here. Google treats these as standard site updates requiring redirects and recrawling, but not domain-level migration signals.

Protocol Changes Require the Tool

There's one exception. Moving from HTTP to HTTPS on the same domain does qualify for Change of Address. You'll need both HTTP and HTTPS versions verified as separate properties in Search Console, then submit a change of address from the HTTP property to the HTTPS property.

This scenario is technically a protocol migration rather than a pure domain change, but Google treats it the same way for Change of Address purposes.

How Do You Monitor Migration Success After Submitting?

The Change of Address tool submission is just the beginning. Active monitoring over the following 90 days determines whether your migration succeeds or fails.

Key Metrics to Track

Watch these indicators across both your old and new Search Console properties:

• Impressions and click trends in the Performance report

• Index coverage status showing which pages Google has successfully crawled and indexed on the new domain

• Crawl stats showing Googlebot activity on both domains

• Manual actions or security issues that might have transferred from the old domain

Your old domain should show steadily declining impressions as Google replaces those URLs with new domain URLs in search results. The new domain should show corresponding increases.

What to Do When Traffic Drops More Than Expected

Some traffic decline during migration is normal. Drops exceeding 20-30% that persist beyond 4-6 weeks indicate a problem.

Common culprits include:

• Incomplete redirect coverage leaving orphaned pages on the old domain

• Redirect chains or loops that prevent Google from reaching final destinations

• New pages blocked by robots.txt or noindex tags

• Lost xml sitemap migration process steps that prevent discovery of new URLs

• Server performance issues on the new domain causing timeout errors

Run a fresh crawl of both domains to identify technical issues. Compare crawl results against your URL mapping document to find pages that didn't migrate correctly.

What About Subdomain Migrations and Other Edge Cases?

Not all migrations fit the clean old-domain-to-new-domain pattern. Subdomain changes, subdirectory moves, and partial migrations each require different handling.

Subdomain to Root Domain (or Vice Versa)

Moving from subdomain.example.com to example.com qualifies for the Change of Address tool if you're migrating the entire subdomain. Verify both as separate properties in Search Console, implement redirects, then submit the change of address.

The same applies in reverse when moving from a root domain to a subdomain.

Subdirectory Migrations

Moving content from example.com/blog to newsite.com/resources is not a site-level migration. You cannot use the Change of Address tool because you're only moving a portion of the old domain.

Handle this with careful redirect mapping and potentially separate URL submission through sitemaps. Google will discover and process the redirects through normal crawling, but without the accelerated timeline that Change of Address provides.

Moving to a Different Server or CMS

If you're migrating to a new server or content management system while keeping the same domain, the Change of Address tool doesn't apply at all. This is a technical infrastructure change, not a domain migration.

Your focus should be on maintaining identical URLs before and after the server move, or implementing redirects if URL structure must change. Search Console will update naturally as Google recrawls your site on the new infrastructure.

Common Change of Address Tool Errors and How to Fix Them

Google's validation checks catch most issues before allowing submission. Understanding these error messages saves debugging time.

"You Don't Own the New Site"

This means the new domain isn't verified in Search Console under your account. Add and verify the property before attempting the change of address again.

"No Redirects Found"

Google cannot detect functional 301 redirects from your old domain to your new domain. Check that redirects are live at the server level and returning proper HTTP status codes.

Redirects implemented via JavaScript, meta refresh tags, or client-side methods don't count. Google requires server-level HTTP 301 redirects for Change of Address to work.

"New Site Not Accessible"

The new domain is returning errors, blocked by robots.txt, or otherwise inaccessible to Googlebot. Verify the new site loads correctly and isn't blocking crawlers.

"Change Already in Progress"

Either the old domain or new domain is already involved in an active Change of Address request. You cannot have overlapping migrations. Wait for the existing request to expire or cancel it before submitting a new one.

Do You Need Additional Tools Beyond Change of Address?

The Change of Address tool handles domain-level migration signals, but it doesn't replace the full technical migration process.

You still need comprehensive redirect mapping, updated internal links on your new domain, XML sitemap submission for the new property, and careful monitoring of crawl and index coverage. The tool accelerates Google's discovery and processing of your migration but doesn't eliminate the underlying technical work.

At Sharkly, our AI-powered platform analyzes your specific site structure and generates customized migration recommendations based on thousands of successful transitions. We've found that migrations combining proper technical execution with immediate Change of Address notification recover fastest and experience the smallest traffic dips during transition periods.

Whether you're planning a domain change, protocol migration, or complex site consolidation, understanding how and when to use Google Search Console's Change of Address tool significantly impacts your migration outcome. Get the technical foundation right first, then use the tool to accelerate Google's understanding of what you've done.