How long should you really keep a redirect after a domain migration?

Why is this minimum duration of one year important?

When you migrate a site from one domain to another, Google needs time to recalibrate all the signals: incoming links, content history, accumulated authority, user behavior. The 301 redirect serves as a gateway that tells the engine, 'this content now lives here.'

The one-year timeframe is not arbitrary. Field observations show that Google recrawls sites at varying frequencies based on their popularity, content freshness, and crawl budget allocated. A less active site may take several months before all its pages are recrawled and all backlinks are reevaluated in their new context.

What happens if you cut off redirects too soon?

Cutting redirects before the transfer is complete is like cutting the umbilical cord while it's still growing. Bots still following old backlinks encounter 404 errors, which gradually dilutes the authority you thought you had transferred.

Worse yet: the old domain becomes available again. If someone buys it and publishes spam or questionable content, the backlinks you had accumulated over the years will suddenly point to this new owner. Google can then associate your new domain with this troubled history through cross-links and old mentions.

Why does Google recommend keeping redirects 'as long as possible'?

The real reason is less about the technical transfer and more about protection against post-migration abuse. An abandoned domain becomes a target for malicious actors who exploit its residual authority and existing backlinks.

By keeping the redirect indefinitely, you control what happens in that old space. All visitors and bots are automatically redirected to your new address, and the old domain cannot be reused against you. It’s as much a reputational safeguard as a technical gesture.

• 12 months minimum to transfer authority and allow Google to recrawl the entire site
• Ideally indefinitely to prevent a third party from purchasing the old domain and exploiting your backlinks
• Monitor the Search Console to ensure that old URLs are no longer generating significant organic traffic before considering a cutoff
• Renew the old domain annually for a fee of a few dozen euros, a negligible price given the risk
• Document the migration in an internal file with the date of the redirects' implementation to anticipate any future decisions

Is this one-year recommendation consistent with field observations?

Yes and no. One year is a reasonable minimum for average sites, but the reality is more nuanced. For large sites with hundreds of thousands of pages and a limited crawl budget, complete transfer can take much longer. Google can take 18 months to recrawl all URLs of a low-priority site.

Conversely, a small well-crawled site with few pages can stabilize its traffic in 3-4 months. Monitoring the Search Console and Analytics becomes essential: as long as the old domain is generating impressions or organic clicks, it remains active in the index. [To be verified] Google does not publish any precise data on average consolidation time by site size.

What are the concrete risks if you cut off after exactly 12 months?

The first risk is the loss of residual authority. Even after a year, some niche backlinks or those from inactive sites may still point solely to the old domain without being updated. Cutting the redirect turns these links into dead ends.

The second, more insidious risk: someone buys your old domain. Expired domain marketplaces are monitored by black hat SEOs who look for domains with clean link profiles. They may attach PBNs, pharma spam, or worse. Your old backlinks then become pollution vectors for their own use, and Google may trace troubling connections between the old and new domains if any traces remain.

Under what circumstances can you consider cutting before a year?

Honestly? Very rarely. If the old domain never had authority, no backlinks, no traffic, and the migration involved a brand-new site, you could cut after 6 months with little risk. However, this scenario is marginal.

If you must let go of the old domain for budgetary reasons (expensive domain, complicated renewal), make sure that the Search Console shows no impressions on the old domain for at least 3 consecutive months. Even then, you're taking a gamble. The annual cost of a .com or .fr is trivial compared to the risk, so the question shouldn't even arise.

What should you do concretely after a domain migration?

Set up 301 redirects from day one, ideally at the server level (Apache, Nginx) or via a CDN to ensure performance and reliability. Don’t rely on WordPress plugins that may falter or slow down the site. Test a sample of old URLs to ensure that each redirect points correctly to the right target page, not systematically to the homepage.

Next, declare the address change in the Search Console using the dedicated tool. This notification accelerates the process on Google's side, but it doesn't replace the technical redirects. Simultaneously, update all backlinks you control directly: your social profiles, forum signatures, mentions in directories or partnerships.

How can you verify that the authority transfer is progressing well?

Monitor two metrics in the Search Console: impressions and clicks on the old domain (separate property) should gradually decrease, while those on the new domain increase. If after 3 months you still see 30% of the traffic on the old domain, it means Google hasn't fully transitioned yet.

For backlinks, use Ahrefs, Majestic, or Semrush to check that detected links are progressively pointing to the new domain. Some tools take time to refresh their index, but if after 6 months you still see 80% of the backlinks on the old domain, restart a crawl or contact webmasters of referring sites to manually update the most strategic links.

What mistakes should you absolutely avoid during this period?

Never remove the old domain from the Search Console until you're sure that Google has transitioned everything. You would lose visibility on any potential problems (crawl errors, residual indexing). Also, do not leave any active duplicate content on the old domain during the transition: everything must redirect, nothing should remain accessible for reading.

Another classic pitfall: forgetting to redirect subdomains, cross HTTPS/HTTP protocols, or versions with/without www. A sloppy migration leaves dozens of orphaned URL variants that dilute signals. Use Screaming Frog or Sitebulb to audit all possible combinations and ensure they all redirect properly.

• Maintain 301 redirects for at least 12 months, ideally indefinitely
• Declare the address change in the Search Console on the day of migration
• Test a representative sample of old URLs to validate redirects
• Monthly monitor impressions/clicks on the old domain via Search Console
• Audit the backlink profile every 3 months to detect non-updated links
• Renew the old domain annually to avoid it falling into the public domain