Transferring an established website to a brand-new domain is one of the most nerve-wracking procedures in digital marketing. When you switch domains, you are asking Google to transfer years of hard-won authority, trust, and historical search equity to a completely unproven address. If you execute the move blindly, you risk weeks of traffic collapse, orphaned URLs, and severe ranking drops. Google Search Console is your primary control room throughout this transition, giving you direct lines of communication to Google’s indexing systems and the diagnostic data needed to verify whether search engines understand your new architecture.
Executing an orderly site move in Search Console is not just a matter of clicking a button after your developers complete their redirects. It requires a disciplined, multi-stage workflow: setting up comprehensive Domain property verifications, configuring the Change of Address tool correctly, running spot checks with the URL Inspection tool, and accurately interpreting the data Google feeds back to you. Crucially, engineering a clean transition means knowing how to separate what Googlebot requests at a server level from what Google actually indexes. Here is how to manage the technical Search Console workflow for an eligible domain migration from start to finish.
Domain Property Verification: Preparing Your Verification Bedrock
Before touching any migration tools, you must ensure your properties are verified in Search Console with full administrative rights. Many teams make the mistake of relying solely on URL-prefix properties (such as https://example.com or https://www.example.com) when preparing for a migration. While URL-prefix properties remain useful for diagnosing specific directories, relying on them exclusively for a site move creates dangerous blind spots.
A Domain property groups together all protocols (HTTP and HTTPS), subdomains (such as www, shop, or blog), and root paths under a single umbrella. To monitor a domain-level migration effectively, you must configure and verify DNS-level Domain properties for both your legacy domain and your target domain:
- Old Domain Property: Set up a Domain property (e.g.,
oldbrand.co.uk) verified via a DNS TXT record at your domain registrar or DNS management provider. - New Domain Property: Set up a matching Domain property (e.g.,
newbrand.com) using DNS TXT record verification. - Complementary URL-Prefix Properties: Retain or create URL-prefix properties for the primary production URLs of both the old and new sites (for instance,
https://www.oldbrand.co.uk/andhttps://www.newbrand.com/). Certain legacy features and sitemap submission workflows operate most reliably when backed by explicit URL-prefix records alongside your master Domain property.
Both properties must be verified under the same Google account, and that account must hold Owner permissions on both domains. If one property is managed by an agency profile and the other by a client profile without matching verified ownership, Search Console will prevent you from initiating migration signals.
The Change of Address Tool: Eligibility and Pre-Flight Checks
Google’s Change of Address tool is a purpose-built feature inside Search Console designed to inform Google that your site has permanently moved to a new domain name. Submitting this request tells Google to accelerate the update of its index, shifting canonical signals and ranking weights from the old URLs to the new URLs far more rapidly than passive crawling alone could achieve.
However, the Change of Address tool has strict eligibility boundaries that many site owners misunderstand. Knowing whether your migration qualifies is a central part of sensible website migration risk management, preventing you from trying to apply the tool to unsupported architectural changes.
When the Tool Can Be Used
- Domain-to-domain moves: Moving from
oldbrand.comtonewbrand.com. - Subdomain-to-subdomain moves: Moving from
shop.brand.comtostore.brand.com. - Subdomain-to-root moves: Moving from
shop.brand.comtobrand.com.
When the Tool Cannot Be Used
- Protocol migrations: Moving from HTTP to HTTPS on the exact same domain. Google handles protocol updates automatically when 301 redirects and HTTPS canonicals are introduced.
- Subdirectory-only relocations: Moving from
example.com/uk/toexample.com/en-gb/, or moving a blog fromexample.com/blog/toexample.com/news/. The Change of Address tool operates strictly at the host level, not the subfolder level. - Domain consolidation: Merging three distinct legacy brands into one single new portal using the tool simultaneously on all properties can create routing conflicts unless handled as discrete, one-to-one domain migration requests.
Essential Pre-Flight Requirements
Do not attempt to activate the Change of Address tool until your server infrastructure is fully deployed and verified. Before opening the tool, ensure the following checks are complete:
- One-to-One 301 Redirects: Every critical legacy URL must return an HTTP 301 permanent redirect pointing directly to its equivalent page on the new domain. Wildcard redirects that dump every visitor onto the new homepage will fail Google’s internal validation tests.
- Self-Referential Canonicals on the Target: Every destination page on the new domain must have an absolute, self-referential canonical tag pointing to its own URL on the new domain.
- XML Sitemaps Live on Both Ends: Ensure the new domain has comprehensive, error-free XML sitemaps submitted in Search Console. Leave the old domain’s XML sitemaps active in Search Console as well; this gives Googlebot an explicit map of old URLs to re-crawl and discover the 301 redirects.
To view where this fits within your wider preparation, refer to our comprehensive website migrate checklist, which covers the entire deployment journey from technical baselines to post-launch governance.
Executing and Confirming the Change of Address
Once DNS cutover is complete and redirects are firing cleanly, navigate to the legacy domain’s Search Console property. Go to Settings and select Change of Address.
The interface will prompt you to select your target property from a drop-down menu of verified sites. Once selected, Search Console runs an automated pre-check validation. During this test, Google picks sample URLs across your old site and attempts to fetch them, checking whether they return valid 301 redirects to the new domain. If Google discovers redirect loops, broken chains, 404 errors, or pages blocked by robots.txt, the validation will fail, displaying specific URL errors you must resolve.
If the validation passes, confirm the move. A persistent notification banner will immediately appear across both the old and new Search Console properties stating that the site is currently moving. This notification remains active for roughly 180 days (six months). During this window, you must keep the old domain registered, its DNS live, and its SSL certificates valid so that Googlebot and lingering external referral traffic continue to hit valid 301 redirects without encountering security warnings.
URL Inspection Checks: Deep Verification at Page Level
While the Change of Address tool coordinates the overall domain shift, you cannot rely purely on aggregate confirmation. You need to use the URL Inspection tool to conduct systematic spot checks on your highest-value category pages, top-performing product pages, and primary lead generators.
Inspect both sides of the migration equation—the old URL and the new destination URL—to verify how Googlebot evaluates each page.
Checking the Old URL
Paste the old URL into the search bar at the top of the old domain’s property. The inspection output should confirm:
- Crawl Status: Successfully fetched, returning an HTTP 301 (or 308) redirect code.
- Indexing Status: The page will be listed as non-indexed, categorised appropriately as “Page with redirect”.
- Google-selected Canonical: Inspecting the redirect often shows that Google recognises the destination URL on the new domain as the canonical version.
Checking the New URL
Switch to your new domain’s property and inspect the target URL. Run a Test Live URL check to confirm:
- HTTP Response: Returns a clean 200 OK status without unexpected interstitial redirects.
- User-declared Canonical: Matches the exact URL requested, including correct protocol and trailing slash handling.
- Google-selected Canonical: Should match your user-declared canonical. If Google lists the old URL or a different variant here, your internal linking, redirect mapping, or external link equity may still be creating ambiguity.
- Rendering & Resources: Review the “View Crawled Page” screenshot and HTML tab to make sure CSS, JavaScript, and main content render cleanly without being blocked by robots directives.
For your top 10 to 20 business-critical pages, clicking “Request Indexing” on the new URLs within the URL Inspection interface can help prompt an initial crawl cycle, though broad re-indexing across your catalogue must be driven by your XML sitemaps and redirect topology.
Distinguishing the Page Indexing Report from Crawl Stats
During a domain migration, one of the most common mistakes marketing teams and developers make is treating the Page Indexing report (formerly Index Coverage) and the Crawl Stats report as interchangeable health indicators. Confusing these two features leads to poor diagnoses, unwarranted panic, or overlooking genuine server-level failures.
These reports track completely different phases of Google’s pipeline. Crawl Stats shows you what Googlebot is fetching from your server over the network. The Page Indexing report shows you what Google has evaluated and accepted into its searchable database.
| Feature Dimension | Crawl Stats Report (Settings > Crawl Stats) | Page Indexing Report (Indexing > Pages) |
|---|---|---|
| Pipeline Stage | Network activity, raw HTTP transport, and server-level response monitoring. | Information extraction, canonicalisation, quality assessment, and index inclusion. |
| Data Latency | Near real-time (usually lags by only a few hours to 24 hours). | Delayed by several days (typically reflects state from 2 to 5 days prior). |
| Primary Question Answered | “Is Googlebot successfully requesting pages and navigating redirects without crashing the server?” | “Which specific URLs are eligible to appear in Google search results right now?” |
| Expected Move Behaviour (Old Site) | High initial spike in crawl requests, heavily dominated by 301 responses, tapering down over months. | Steady drop in “Indexed” pages; rapid increase in “Page with redirect” exclusions. |
| Expected Move Behaviour (New Site) | Aggressive spike in requests by purpose: split between “Discovery” and “Refresh” (200 responses). | Gradual climb in valid “Indexed” URLs; short-term presence of “Crawled – currently not indexed” during processing. |
| Critical Red Flags | Spikes in 5xx server errors, DNS failures, connection timeouts, or surging average response times. | “Duplicate without user-selected canonical”, high percentages of “Discovered – currently not indexed”, soft 404s. |
How to Read Crawl Stats During a Site Move
To inspect Crawl Stats, open Settings and click Crawl Stats. During the first two to four weeks post-migration, scrutinise this report daily across three primary dimensions:
- Crawl Requests by Response: On your legacy property, you should see 301 redirects jump to represent 90% or more of all activity. If you see a rising volume of 404s or 500s, Googlebot is hitting unmapped pages or your old host is choking under the redirect load. On the new property, you want to see predominantly 200 responses.
- Host Status: Check the Host Status indicators at the top of the report. This card monitors three critical points of failure: Bot access (robots.txt), DNS resolution, and Server connectivity. If any of these show red warning ticks during a migration, Googlebot will throttle its crawl rate immediately, stalling your entire move.
- Crawl Requests by Purpose: Google categorises crawls into Discovery (finding newly surfaced URLs) and Refresh (re-crawling known URLs). A healthy new domain will show high Discovery crawl volumes initially as it consumes your sitemaps, gradually balancing out with Refresh crawls as pages settle into the index.
How to Read the Page Indexing Report During a Site Move
The Page Indexing report reflects Google’s actual evaluation of your content. Because this report lags behind Crawl Stats, you must not panic if your new domain shows low indexed counts on Day 2 or Day 3. What matters is the direction of the trend lines over two to six weeks.
Keep a close eye on these specific statuses on your new domain:
- Page with redirect: If you are moving to a brand-new architecture, verify that your new URLs are not chaining or generating unnecessary internal redirects.
- Crawled – currently not indexed: In a migration, this status means Googlebot fetched the new URL, evaluated its content, but has not yet committed it to the search index. A brief surge here is normal while Google determines whether the page is a true duplicate of the old authority signal or an independent asset. However, if this number stays stubbornly high after three weeks, it often indicates quality concerns, thin templating, or weak internal linking.
- Duplicate without user-selected canonical: This error indicates that your CMS or template is serving duplicate variants of your pages without clear canonical directives, confusing Google during the transition.
Diagnosing and Resolving Common Search Console Migration Anomalies
Even with careful preparation, domain moves can encounter obstacles. When issues arise, Search Console is where the symptoms first appear. Here is how to diagnose and resolve the three most common post-move migration errors.
1. Stalled Indexation on the New Domain
If Crawl Stats on the new site show healthy request counts for 200 OK pages, but the Page Indexing report shows a flatlined count of indexed URLs alongside high numbers of “Discovered – currently not indexed”, your crawl queue is backed up. Googlebot knows the pages exist, but its processing pipeline has deprioritised rendering and indexing them.
Remediation: Confirm that your XML sitemaps are cleanly categorised and split by content type (e.g., products, categories, blog posts) so you can isolate which templates are stalling. Inspect your internal linking structure: ensure category pages link contextually to deeper products rather than relying entirely on JavaScript-rendered faceted navigation. Finally, verify that your old domain’s 301 redirects point directly to their final destination, without passing through intermediate hops or protocol conversions that bleed crawl budget.
2. Split Ranking and Canonical Clashes
Occasionally, Search Console’s Performance report will reveal that both the old domain and the new domain are actively generating impressions for the same target keywords weeks after the move. When you inspect the new URL, you may see that Google has listed the old URL as the “Google-selected canonical”.
Remediation: This indicates mixed signals. Check whether external backlinks, hardcoded internal links within your templates, or external platform feeds still reference the old domain. If the content on the new domain was heavily redesigned or reduced during the move, Google may not view the two pages as identical matches. Align the text, title tags, and structured data on the new page more closely with the original page to help Google complete the canonical consolidation.
3. High Server Response Times and 503 Spikes
When Google processes a Change of Address request, its crawling frequency often spikes sharply as it tries to re-index both sites at once. If your hosting infrastructure on either the old or new domain lacks sufficient caching or concurrency headroom, Crawl Stats will reveal an abrupt spike in average response time, accompanied by 503 Service Unavailable errors.
Remediation: Googlebot will back off automatically if it detects that its crawl requests are slowing down your server, delaying your migration by weeks. Upgrade server resources or adjust CDN edge-caching rules immediately to handle the crawl traffic. For the legacy domain, consider moving all redirect logic onto an edge network or Cloudflare worker so that redirect lookups do not hit your origin web server at all.
Maintaining the Setup for Long-Term Equity Retention
A domain migration is not complete the moment your new URLs start driving traffic. Google’s Change of Address tool maintains an active signal for roughly six months, but the underlying redirect infrastructure must remain in place for much longer. Keep the old domain registered, maintain its DNS records, and ensure its SSL certificates auto-renew for a bare minimum of one full year—ideally retaining the domain indefinitely.
If you decommission the old domain or let its registration lapse after six months, external backlinks pointing to your original URLs will break immediately. Worse still, if a competitor or domain broker acquires your expired legacy domain, they can remove your 301 redirects or repurpose the historical link equity for themselves. Treat your Search Console migration workflow as a structured handover: set up comprehensive Domain properties, validate your routes with the Change of Address tool, run rigorous URL inspections, and use Crawl Stats and Page Indexing reports together to ensure your site retains its search equity for the long haul.