Do 301 redirects really transfer 100% of link signals to a new domain?

Why does Search Console still show backlinks on the old domain?

When you migrate a site to a new domain, Search Console continues to report backlinks pointing to the old domain for an indefinite period. This is normal: these links physically exist on other sites and still point to your old URL.

Google cannot change these links at the source. Third-party site owners often have no reason to update their links. Search Console reflects this reality: it shows you where backlinks actually are, not where you would like them to point.

Are link signals really transferred to the new domain?

According to this statement, yes. The link signals— mainly referring to PageRank and authority—are indeed transferred to the new domain if the redirects are correctly implemented.

Specifically, when Googlebot encounters a link to your old domain, it follows the 301 redirect and treats the link as if it points directly to the new URL. The SEO juice therefore passes to the new domain, even if the link trace remains visible on the old one in Search Console.

What constitutes a "properly configured" redirect according to Google?

This is where the statement becomes vague. Google does not detail the criteria for a "properly configured" redirect. It is assumed it involves permanent 301 redirects, quick to process, with no chains of multiple redirects.

A chain of redirects (A → B → C → D) slows down crawling and can lead to a progressive dilution of signals. Similarly, a temporary redirect (302) is not meant to transfer PageRank sustainably. Google has never publicly confirmed that a 301 transfers 100% of SEO juice, but field observations suggest a transfer close to that value.

• Search Console continues to show backlinks on the old domain after migration, which is expected behavior.
• Link signals pass to the new domain via permanent 301 redirects.
• A properly configured redirect must be permanent, quick, without chains, and point to the correct target page.
• Google does not specify the exact transfer rate of PageRank via 301, but field tests show a near-total transfer.
• The duration for keeping redirects is not specified here, but a practitioner consensus recommends at least 12 months.

Is this statement consistent with field observations?

Yes, overall. Well-executed domain migrations show a transfer of rankings and organic traffic to the new domain within weeks to months. If signals were not transferred, we would see a systematic collapse of traffic.

However, no migration is pain-free. There is always temporary volatility in rankings and sometimes a slight erosion of traffic during the transition phase. Google needs to reindex the new URLs, recalculate signals, and adjust its ranking models. This statement overlooks these transient effects.

What nuances should be added to this claim?

[To be verified] Google never quantifies the percentage of signals transferred. Saying "signals are transferred" does not guarantee a 100% transfer. Public data is lacking to assert that a 301 retains the entirety of PageRank.

Furthermore, this statement implies that any properly configured redirect is sufficient. This is inaccurate. A successful migration also involves: a page-to-page redirect plan (no catch-all redirect to the homepage), internal link management on the new domain, an updated XML sitemap, and tight monitoring of 404 errors.

In what cases does this rule not fully apply?

If you redirect an entire domain to a single page (homepage of the new domain), Google will likely not transfer all signals. Individual redirects are necessary that respect the intent of the original page.

Similarly, if your old domain had manual or algorithmic penalties, they may carry over during migration. Google has never officially confirmed that penalties transfer, but documented cases exist. A migration is not a magic reset for a penalized site.

What should you actually do during a domain migration?

Prepare a page-to-page redirect plan before the switch. Every important URL from the old domain should redirect to the corresponding URL of the new one, not to a generic page. Use permanent 301 redirects exclusively.

Update your XML sitemap with the new URLs and submit it in the Search Console of the new domain. Also, configure the change of address property in Search Console: this tool explicitly notifies Google of your migration and speeds up processing.

What mistakes should be avoided during and after migration?

Never redirect all pages to the homepage of the new domain. Google detects this pattern and may ignore the redirects. Every page must have its logical destination.

Avoid redirect chains (A → B → C). Googlebot may stop after a few hops, and processing time increases. Ensure your redirects point directly to the final destination.

Do not remove redirects too soon. Keep them active for at least 12 months, ideally 18 to 24 months if your site has many old backlinks. Third-party search engine bots and users take time to update their references.

How can you check if the redirects are working properly?

Use a crawler like Screaming Frog or Sitebulb to test all URLs of the old domain. Ensure that each redirect returns a HTTP 301 status, not 302 or 307.

In the Search Console of the new domain, monitor the evolution of indexing and impressions. You should see a gradual increase in impressions on the new domain while the old one declines. Also, watch for 404 errors: they indicate URLs forgotten in your redirect plan.

• Implement permanent 301 redirects on a page-by-page basis, no generic redirect to the homepage.
• Set up the change of address in Search Console to officially notify Google.
• Ensure there are no redirect chains (A → B → C) that dilute signals.
• Keep redirects active for a minimum of 12 months after migration.
• Crawl the old domain to validate that each important URL redirects correctly.
• Monitor indexing and 404 errors in the Search Console of the new domain for 3 to 6 months.