How can you effectively handle duplicate content uploaded to the wrong domain?

Why should you remove the content instead of leaving it online?

Leaving duplicate content on two different domains creates artificial cannibalization. Google must then choose which version to index and display in the search results. If you accidentally uploaded a complete article to domaine-test.com instead of domaine-principal.com, Google may well decide to index the wrong version.

Immediately removing the incorrect content restores clarity for the crawlers. You eliminate the risk that Google considers one of the versions as the default canonical one, while you have no control over that choice. This is particularly critical if the wrong domain has lower authority or a poorly optimized architecture.

When does a 301 redirect become necessary?

If the error is detected within a few hours, a simple removal suffices. Google will not have had time to index the incorrect page or assign it ranking signals. However, if several days or weeks have passed, the erroneous page may have accumulated external backlinks, social shares, or organic traffic.

The 301 redirect then transfers these signals to the correct URL. Without a redirect, you will permanently lose the link equity gained during that period. Google sees the 301 as a permanent signal: "this content has moved, transfer all attributes to the new address." It is the only way to recover the accumulated SEO value from the wrong URL.

What happens if you let both versions coexist?

Google will detect the duplicate content and apply its own deduplication filter. In practice, it will choose a canonical version based on its own criteria: crawl freshness, domain authority, and the quality of backlinks pointing to each version. You have no guarantee that the correct version will be retained.

Worse, if both versions accumulate contradictory signals (different backlinks, varied anchors), Google may dilute the relevance of each. As a result, neither will rank properly. Prolonged coexistence may even trigger a manual review if Google suspects an attempt at manipulation.

• Immediate removal of the incorrect content if detected within 24-48 hours
• Mandatory 301 redirect if the incorrect page has been crawled and accumulated signals
• Monitor Search Console to ensure Google has properly deindexed the old URL
• Update external backlinks when possible to point directly to the correct URL
• Clean the XML sitemap to exclude any reference to the incorrect URL

Does this recommendation cover all scenarios of failed migration?

Mueller's statement targets a specific case: accidental upload to the wrong domain. This is a common scenario in agencies when juggling staging environments, client sites, or test domains. The solution (removal + 301) is logical in this context.

But what about partial migrations where only a section of the site was mistakenly migrated? Or cases where incorrect content was modified before detecting the error? [To be verified]: Google does not specify if the 301 must point to an identical URL or if a "close" target page is sufficient. Field experience shows that Google tolerates a 301 to a thematically equivalent page, but this remains unclear.

Is Google’s definition of "long enough" clearly established?

Mueller mentions to implement a 301 "if it lasted long enough," without specifying a threshold. In the field, it is observed that Google crawls new content within 24-72 hours on sites with a high crawl frequency. For a less active site, this period can extend to a week.

[To be verified]: no official data quantifies "long enough." As a precaution, consider that a crawled and indexed page justifies a 301, even if it existed only for 48 hours. The main risk is not so much the duration but the accumulation of signals: a single quality backlink to the wrong URL is enough to justify a redirect.

Should you prefer the 301 or the canonical tag in this case?

Google recommends a server-side 301, not a canonical tag. The canonical is a "weak" signal: Google can choose to ignore it if it detects inconsistencies (backlinks massively pointing to the non-canonical version, for example). The 301 is a "strong" and permanent signal.

Using a canonical on the wrong page pointing to the right one may seem tempting, but it's counterproductive: you leave the wrong URL accessible, thus crawlable and potentially indexable. The 301 permanently removes the incorrect version from Google's pipeline. It is a clear, binary choice, without ambiguity.

What concrete steps should you take if you detect this kind of error?

First step: assess the severity of the situation. Open the Search Console for both concerned domains. Check if the incorrect page appears in the index (site: command or Coverage tab). If it is not indexed, a simple removal suffices. If it is indexed, move immediately to the next step.

Second step: implement the server-side 301. Depending on your technical stack, use .htaccess (Apache), nginx.conf, or your CMS's redirection rules. Test the redirect with a tool like Screaming Frog or Redirect Path to ensure it returns an HTTP 301 code and not a 302 or a chain of redirects. Once activated, submit the old URL for removal in Search Console to speed up the deindexation process.

What mistakes should you absolutely avoid?

Never use a temporary 301 (yes, it doesn't officially exist, but some buggy setups produce intermittent 302s). The 302 does not reliably transfer SEO signals. Google may interpret a 302 as a temporary redirect and continue to crawl the old URL indefinitely.

Avoid also leaving the old URL with a 404 or 410 error if it has accumulated backlinks. Some believe that a 410 (Gone) speeds up deindexation, but you then lose all acquired signals. The 404 is acceptable only if the incorrect page was never crawled and no backlinks point to it. When in doubt, prefer the 301.

How can you verify that the correction has worked?

Monitor the Search Console for 2-4 weeks. The old URL should disappear from the index (Coverage section) and the new one should maintain or increase its impressions. Use the URL inspection tool to force a new crawl of the correct version and accelerate the process.

Also check that important external backlinks have been updated. Contact important referring sites to ask them to correct the link. Google will follow the 301, but a direct link to the correct URL is always preferable: it avoids an extra hop and reinforces the relevance signal.

• Check the indexing of the incorrect page in Search Console (site: or Coverage)
• Implement a permanent server-side 301 (not canonical, not 302)
• Test the redirect with Screaming Frog or an equivalent tool
• Submit the old URL for accelerated removal in Search Console
• Crawl the entire site to detect any internal links pointing to the old URL
• Monitor the evolution of indexing and impressions for 2-4 weeks