Does a 1:1 domain migration truly transfer ALL ranking signals?

What does a 1:1 domain migration actually mean?

A simple domain migration, or 1:1 migration, refers to the transfer of a website from one domain name to another without any changes to the structure or content. Each URL from the old domain corresponds exactly to one URL on the new domain.

Unlike complex migrations that involve simultaneous redesigns, changes in hierarchy, or mergers of sites, the 1:1 migration is the most straightforward: olddomain.com/page-a becomes newdomain.com/page-a, end of story.

What specific ranking signals are involved?

When Mueller talks about “all ranking signals”, he is referring to all the indicators that Google uses to evaluate and rank your pages. This includes the PageRank passed on through backlinks, authority accumulated over time, user engagement signals, and even historical performance data.

Google has invested years of engineering to ensure that 301 redirects transfer these signals almost seamlessly. The promise is that your new domain inherits all of the SEO capital from the old one — if you follow the best practices.

Why does Google emphasize that it works “generally very well”?

The word “generally” is not trivial. It implicitly acknowledges that failures can occur, often due to human implementation errors rather than technical limitations of Google.

Migrations that partially fail almost always share common issues: improperly configured redirects, robots.txt files blocking the crawl of the new domain, contradictory canonical tags, or complete lack of post-migration monitoring. Google can transfer the signals — but you must empower it to do so correctly.

• 1:1 migration: each old URL redirects to a unique and equivalent new URL
• Complete signal transfer: PageRank, authority, performance history, engagement data
• Permanent 301 redirects: the required method to notify Google of the permanent move
• “Generally very well”: acknowledges that implementation errors can undermine the process
• Rigorous preparation necessary: Google's assertion does not exempt you from having a detailed migration plan and tight post-migration monitoring

Does this statement really reflect field observations?

Let's be honest: practitioners' experiences confirm that well-executed 1:1 migrations do indeed go smoothly in the majority of cases. But this majority is not 100%, and the exceptions are often painful.

Testimonies of traffic drops post-migration abound — but when you dig deeper, you almost always find a configuration error: chain redirects, forgotten important pages, excessive server response delays. Google transfers the signals, yes, but only if you provide a technically flawless migration plan.

What grey areas does Mueller not address?

The statement remains vague about the timing of the transfer. “All signals are transferred” says nothing about the speed. In practice, there is often a floating period of 2 to 6 weeks where positions fluctuate while Google re-crawls, re-indexes, and consolidates signals between the old and new domain.

[To be verified]: Mueller also does not specify what happens if you keep the old domain accessible without a redirect during a transitional period or if you stop redirects too soon. The optimal duration for maintaining redirects remains a debated topic — some recommend 6 months, others a minimum of a year.

In what cases might this rule not fully apply?

If your 1:1 migration comes with major technical changes — simultaneous transition from HTTP to HTTPS, complete template redesign, changes in loading speed — it becomes challenging to isolate the impact of the pure domain migration.

Another blind spot: domains with a problematic history. If your new domain has previously been used and bears penalties or a toxic backlink profile, the signal transfer from your clean old domain could be tainted by that legacy. Google never explicitly states this.

What should you set up concretely before migrating?

The first non-negotiable step: thoroughly map out all the URLs of the old domain that receive organic traffic or quality backlinks. A complete crawl with Screaming Frog or Oncrawl, combined with Search Console and Google Analytics data, will provide you with a solid foundation.

Next, prepare a 1:1 redirect plan in table format (old URL → new URL) and implement it server-side with permanent 301 redirects. Test this plan in a staging environment before the big day — a misconfigured redirect multiplied by thousands of URLs can ruin a migration.

What critical mistakes should be absolutely avoided?

The number one mistake: redirecting all pages to the homepage of the new domain. That's SEO suicide. Google detects these massive redirects as irrelevant and may choose not to transfer signals, or even deindex the old URLs without valuing the new ones.

The second classic pitfall: blocking the crawl of the new domain with a restrictive robots.txt or forgotten noindex tags after the development phase. If Google cannot crawl and index the new site, it obviously cannot transfer the signals. Check, double-check, and have a third party verify.

How can you monitor that the transfer of signals is going smoothly?

Set up daily monitoring for at least 8 weeks post-migration: key positions in a rank tracker, organic traffic segmented in Analytics, 404 errors, and chain redirects in Search Console.

Also monitor the crawl rate: Google should progressively decrease its crawling of the old domain and intensify it for the new one. If the old domain continues to be crawled extensively 4 weeks after migration, it’s a warning sign — your redirects may not be detected correctly.

• Comprehensive crawl of the old domain to identify all URLs to redirect
• Documented and staged 1:1 redirect plan
• Permanent 301 redirects implemented server-side (not in JavaScript)
• Robots.txt and meta robots verification on the new domain
• Address change declaration in Google Search Console
• Daily monitoring of positions, traffic, errors, and crawl rate for at least 8 weeks