Does Google really transfer all signals during a domain migration?

What does "signal transfer" really mean?

When Google talks about signal transfer, it refers to the mechanism by which all ranking attributes of the old domain are supposed to migrate to the new one. This includes accumulated PageRank, thematic authority, trust history, and most importantly, the backlink profile.

The promise is appealing: you change your domain name, but Google treats the new site as if it inherits all the longevity and reputation of the old one. In theory, you're not starting from scratch. But this transition relies entirely on the correct detection of 301 redirects and the consistency of your migration plan.

Why does Mueller emphasize official guidelines?

Because even the smallest technical error sabotages the transfer. A 302 redirect instead of a 301, a chain of redirects, orphan pages not redirected, or a too abrupt URL structure change, and Google loses track. The bot crawls the old domain, finds nothing, then discovers the new one without understanding the relationship.

Google's official guidelines cover the implementation of permanent redirects, maintaining the XML sitemap, notifying the address change in Search Console, and keeping both domains online temporarily. Ignoring even one of these points drastically lengthens the floating period and increases organic traffic losses.

Is the transfer immediate and complete?

No. This is where Google's statement becomes misleading by omission. The transfer of signals takes time—often several weeks, sometimes months depending on the site's size and crawl frequency. During this period, you will see position fluctuations, pages temporarily disappearing from the index, and traffic fluctuations.

Moreover, the transfer is never 100% perfect. Some backlinks will never be recrawled, other sites will take months to update their links, and Google may decide to reevaluate certain signals in the new context. Expect to lose between 5% and 20% of your organic visibility permanently, even with a technically flawless migration.

• Permanent 301 redirects: the only recognized method for maintaining link equity
• Notification in Search Console: speeds up the acknowledgment of the address change
• Temporary maintenance of the old domain: gives bots time to recrawl everything
• Structural consistency: avoid changing the structure, CMS, and domain simultaneously
• Post-migration monitoring: track indexing, rankings, and crawl errors for at least 6 months

Is this statement consistent with real-world observations?

Yes and no. In principle, Google does transfer signals, and 301 redirects work. This is verified daily on well-executed migrations. However, Mueller's statement overlooks the actual timeframes and the partial nature of the transfer.

In practice, even on exemplary migrations with all best practices followed, there is typically a temporary decrease of 15% to 40% in organic traffic during the first 4 to 8 weeks. The site gradually recovers, but rarely beyond 90-95% of the initial level before 3 to 6 months. [To be verified]: Google provides no official figures on the actual transfer rate or average consolidation times.

What factors slow down or degrade the transfer?

The crawl frequency of your site is crucial. A site crawled daily recovers in a few weeks. A site with a limited crawl budget, visited once a week, will take months. Google needs to recrawl each page of the old domain to discover the 301, then recrawl the new domain to index the new URLs.

Next, the third-party backlinks. Google follows the 301s, but a direct link to the new domain is always better than a link to the old one that redirects. However, you have no control over how quickly external sites update their links. Some may never do it. Result: part of your link equity remains locked in permanent redirects, losing a bit of value with each jump.

Finally, the context changes. If you migrate from a .fr to a .com, or from an exact match domain to a brand domain, Google may reevaluate thematic relevance. The same applies if you simultaneously change CMS, URL structure, or internal linking. Each additional variable increases the risk of signal loss.

Should you maintain 301 redirects indefinitely?

Yes. This is a commonly misunderstood point. Google recommends keeping redirects for at least one year, but in reality, they should be maintained indefinitely if you want to avoid any loss of equity. Some backlinks are only recrawled every 6 or 12 months. If you cut the redirects after one year, those links become dead and their value disappears.

The only situation where you might consider disabling the old domain is if you have manually contacted all high-authority sites to update their links, and you are willing to permanently lose dormant or abandoned backlinks. However, financially, renewing a domain name costs just a few euros per year, while rebuilding organic authority costs thousands.

What should you do before launching the migration?

Map out all indexed URLs from the old domain. Complete export from Search Console, crawl via Screaming Frog or equivalent, exhaustive list of pages receiving organic traffic in Analytics. Each URL from the old domain must have a clear destination on the new one, either 1:1 if the structure is identical, or to the most relevant equivalent page if you are restructuring.

Prepare a detailed redirect plan in table form with three columns: old URL, new URL, HTTP code (301). Test this plan in a staging environment before going live. A single error in a redirect regex can lead thousands of pages to a 404 or an infinite loop.

What mistakes should you absolutely avoid?

Never redirect all pages from the old domain to the homepage of the new one. This is a classic mistake of rushed migrations. Google detects this pattern, considers that relevance is not preserved, and only transfers a fraction of the signals. Each page must point to its directly thematic counterpart.

Don’t change CMS, URL structure, and domain at the same time. If you must change everything, break it down into two phases: first the technical overhaul on the old domain, stabilization for 2-3 months, then migration to the new domain. Otherwise, you multiply the variables and lose diagnostic capability if something goes wrong.

Don’t forget to declare the address change in the Search Console of the old domain. This function exists precisely to inform Google of the migration. Without it, the bot treats the old and new domains as two distinct entities for much longer. And keep both Search Console properties active for at least 6 months to monitor progress.

How to monitor and optimize the transition?

Monitor daily indexing of the new URLs via Search Console of the new domain. Look at the number of indexed pages, crawl rate, and 4xx and 5xx errors. If indexing stalls or key pages are missing after 2 weeks, force their crawl using the URL inspection tool.

Compare the positions of your priority keywords before and after migration with a rank tracking tool. Quickly identify pages that are losing ground abnormally. If a page drops 50 positions while the redirect is correct, it’s often a signal that Google has reassessed its relevance in the new context: check the content, Title/H1 tags, and internal linking.

Some complex migrations require sharp expertise and constant monitoring to avoid irreversible traffic losses. If you manage a high-stakes commercial site or your team lacks experience in domain migrations, support from a specialized SEO agency can secure the operation and speed up the return to normal. Migration errors cost far more in lost revenue than an audit and professional follow-up.

• Establish a comprehensive 1:1 redirect plan between the old and new domain
• Set up permanent 301 redirects on the server side (Apache, Nginx, CDN)
• Declare the address change in Search Console of the old domain
• Keep the old domain active with redirects for at least 12 months
• Monitor indexing and positions daily for the first 8 weeks
• Contact high-authority sites for manual updates of backlinks