How does Google really transfer signals when changing domains?

What exactly does it mean when Google says it "attempts to transfer" signals?

The verb "attempts" used by Google is not trivial. It confirms that a domain change offers no guarantee of maintaining rankings. Google will do its best to associate the old domain with the new one, but this process remains imperfect.

The transferred signals mainly include the PageRank passed through backlinks and content understanding. Google will crawl the 301 redirects, identify that domain A has become domain B, and gradually adjust its indexes. This is not an instantaneous switch.

Why does this statement emphasize official guidelines?

Failed domain migrations are one of the major causes of irreversible organic traffic losses. Google reminds us that without rigorous setup (complete redirects, updating Search Console, temporarily maintaining the old domain), the transfer partially fails.

The official guidelines cover the granularity of URL-by-URL redirects, verification of properties in Search Console, and the timing of deactivating the old domain. Ignoring even one point can fracture the transfer of signals.

What timeline should one expect for this signal transfer?

Google never provides a precise timeline, but field observations suggest that the main transfer stretches over 3 to 6 months. During this period, both domains coexist in the index with a gradual preference for the new one.

Some signals transfer quickly (content, structure), while others transfer slowly (accumulated authority, domain trust). Some may never fully transfer if the backlink profile is not naturally updated by referring sites.

• Partial transfer: Google implicitly acknowledges that some signals will be lost, regardless of the quality of execution.
• Role of 301 redirects: they are the main mechanism that allows Google to establish the match between the old and new domains.
• Importance of timing: keeping the old domain active too long dilutes signals, while stopping it too soon cuts them off abruptly.
• Dependence on backlinks: if third-party sites never update their links, part of the PageRank will remain attached to the redirects rather than the target domain.
• Monitoring Search Console: coverage and performance reports are essential to detect non-redirected URLs or mapping errors.

Is Google's approach consistent with what is observed in the field?

Yes, but with a critical nuance: the term "attempts" is an admission that Google guarantees nothing. Successful migrations exist, but they require surgical preparation. Cases of catastrophic migrations are common, often due to chain redirects, approximate mappings, or premature deactivation of the old domain.

There are regular indications of traffic losses ranging from 20% to 40% during the first 3 months, even with a technically perfect migration. Google takes time to reallocate trust, and some signals (domain age, crawl history) never really transfer. [To be verified]: Google does not specify whether behavioral signals (historical CTR, bounce rate) are transferred or reset.

What are the gray areas that Google doesn’t mention here?

The statement remains deliberately vague on the exact mechanisms. For instance, it doesn’t say anything about the fate of non-redirected URLs (404 generated), the impact of a simultaneous URL structure change, or what happens if the old domain is left active indefinitely with duplicate content.

Another blind spot: the transfer of penalties. If the old domain had manual or algorithmic actions (historical Penguin, Panda), can these negative signals follow? Google never makes this clear, but field cases suggest that yes, under certain conditions.

In what cases does this transfer logic completely fail?

Major failures occur when redirects are not 1:1 URL by URL, but bulk to the homepage or a few generic URLs. Google interprets this as content disappearance, not migration. The transfer of signals is then minimal.

Another scenario of failure: migrating to an already existing domain with its own SEO history. Google may struggle to merge signals from two distinct entities, especially if they cover divergent themes. The resulting algorithmic confusion can last for months.

What must be done before launching the migration?

Start with a comprehensive audit of indexed URLs on the old domain. Use Search Console, crawl the site with Screaming Frog or Oncrawl, and export all URLs generating organic traffic. Every URL from the old domain must have an exact match on the new one.

Prepare a URL-by-URL mapping file. No bulk redirects to the homepage. Ensure the new domain is technically ready: loading speed, crawlable structure, absence of bugs. A migration to a technically inferior site amplifies losses.

What critical mistakes must absolutely be avoided?

Never disable the old domain before Google has fully indexed the new one and transferred most signals. This usually takes a minimum of 6 to 12 months. Cutting too soon leads to a sudden drop as Google loses the source of the redirects.

Avoid chain redirects (A → B → C). Each jump dilutes the transferred PageRank. Redirects must point directly from the old to the new domain, with a permanent 301. Test each redirect manually on a representative sample before launch.

How to monitor and adjust after the domain change?

Set up both properties (old and new domain) in Search Console and officially declare the change of address through the dedicated tool. Daily monitor coverage reports to detect 404s, soft 404s, and non-redirected URLs.

Track the evolution of impressions and clicks on both domains. Traffic should gradually shift from the old to the new. If after 3 months you see no transfer, this is a sign of a major technical problem (unseen redirects, misconfigured canonicals, accidental noindex).

• Create a comprehensive URL-by-URL mapping before the migration (no orphan URLs)
• Implement permanent 301 redirects, no 302 or meta refresh
• Declare the change of address in Search Console for both properties
• Keep the old domain active with redirects for a minimum of 12 months
• Daily monitor coverage and indexing reports for both domains
• Manually check a sample of redirects after deployment (code 301, correct target)