
Duplicate content on different domains means the same or nearly identical text lives on two or more separate websites, not just multiple pages on one site. It happens through syndication, scraping, shared product feeds, or franchise and international domains. Google doesn't penalize this directly, but the duplicate copies split rankings, links, and crawl budget between domains.
Duplicate content on different domains is when the same block of text, whether a full article, a product description, or a service page, shows up on two or more domains that Google crawls and indexes separately. That's different from duplicate content on a single site, where the same page might just be reachable through two URLs. Across domains, Google has to decide which independent website "owns" the content, and it usually only lets one version rank well for any given search.
This isn't a rare edge case. Matt Cutts, Google's former head of webspam, once estimated at a search conference that roughly 25 to 30 percent of all content on the web is duplicate in some form. Most of that is not spam or theft; it's syndicated news, repeated product listings, and template-driven pages that were never meant to compete with each other in the first place.
A handful of situations account for almost every case of cross-domain duplication:
Duplicate content on different domains doesn't trigger a direct Google penalty. Google's Search Central documentation states plainly that duplicate content on a site "is not grounds for action on that site unless it appears that the intent of the duplicate content is to be deceptive and manipulate search engine results." But it still costs you: Google's algorithms pick one version to rank and largely filter the rest out of results, so your backlinks, clicks, and crawl budget end up split across copies instead of concentrated on one page.
The practical effect is usually that the domain with more authority, more internal links, or a clearer canonical signal wins, and the other domain's copy quietly disappears from most searches for that content. If you want the full breakdown of the penalty myth and what Google actually does, see our guide to the duplicate content penalty.
Pick one domain as the canonical source, then either 301 redirect the duplicate domain to it or add a cross-domain rel=canonical tag on every duplicate page pointing to its match on the preferred domain. Which one you use depends on whether the duplicate domain needs to stay live (canonical) or whether you're retiring it for good (redirect). For content you don't fully control, such as scrapers, a takedown request replaces both options.
| Method | Best for | How it works |
|---|---|---|
| 301 redirect | Retiring a duplicate domain entirely, such as after a rebrand or acquisition | Sends visitors and search engines from the old domain straight to the matching page on the new one |
| Cross-domain rel=canonical | Syndication and product feeds, where both domains stay live | Tag in the page head points to the preferred URL without redirecting anyone |
| Noindex | A low-value duplicate you want to keep online for users but out of search results | Meta robots tag removes the page from the index without consolidating ranking signals |
| Rewrite and differentiate | Franchise pages, location pages, and manufacturer descriptions | Adds unique local detail so the pages stop being near-duplicates of each other |
| Content removal request | Scraped or stolen content you don't control | Formal request to Google (and the host) to remove the infringing copy from search results |
Franchise networks and multi-location businesses run into this constantly: corporate hands every location the same template, and the only thing that changes between domains is the city name. Google can end up choosing one location's page to rank and suppressing the rest, which is the opposite of what a multi-location business needs. Our franchise SEO strategy guide covers the full playbook, but the short version is to write real, location-specific detail: staff names, local landmarks, hours, reviews, and photos, so each domain earns its own reason to rank rather than competing with its sister locations.
If individual location domains don't need to rank independently, a cross-domain canonical back to a central location-finder page is often simpler than trying to make every page unique.
Country-specific domains create a related but distinct problem. Hreflang tags tell Google which regional version of a page to show which audience, but hreflang alone doesn't fix duplication if the underlying translations are thin or machine-generated with no local adaptation. That's a narrower, tag-specific issue we cover separately in our guide to hreflang duplicate content; this article is about the broader cross-domain problem, which also includes syndication, scraping, and shared product data that has nothing to do with hreflang at all.
First confirm your original was published first, using the index coverage dates in Search Console or a lookup on the Wayback Machine. Then file a removal request through Google's content removal tool, which typically gets the scraped page removed from search results within a few days without needing legal action. If the scraper keeps reposting, contact the site's web host directly, since most hosts will suspend accounts for repeated, documented infringement.
A cross-domain rel=canonical tag is a link element placed in the head of a duplicate page that points to the preferred URL on a different domain, not just a different page on the same site. Google added support for this in December 2009 specifically so publishers and syndication partners could consolidate ranking signals without redirecting traffic away from the duplicate. It's a strong signal, according to Google's own canonicalization documentation, but not an absolute guarantee: Google can still choose a different canonical if other signals, like internal links or a sitemap, point elsewhere.
Run your key pages through a plagiarism checker like Copyscape or an SEO tool like Siteliner to find exact-match text elsewhere online. Ahrefs' Site Explorer can show which other domains rank for your exact phrasing, and a simple Google search of a distinctive sentence in quotation marks will often surface scrapers within seconds. If you syndicate content on purpose, keep a short log of which domains have permission, so an unexpected match is easy to tell apart from an authorized one.
For a broader technical health check that catches duplication alongside crawl, indexing, and structure issues, run through our SEO audit checklist before assuming a ranking drop has a single cause. Strong topical structure also matters here: pages that are built around clear semantic SEO principles are less likely to accidentally overlap with each other in the first place, and knowing the fundamentals of content optimization helps you write location or region pages that stay unique by design instead of by accident.
What is duplicate content on different domains? It is when the same or nearly identical text, product listings, or articles appear on two or more separate domains instead of just multiple pages on one site. It happens on purpose through syndication or shared product feeds, or by accident through scraping, copied templates, or old sites left live after a migration. Google indexes and ranks each domain separately, so the duplicate copies end up competing with each other.
Does Google penalize duplicate content on different domains? No, not as a direct penalty. Google's own Search Central guidance states duplicate content is not grounds for action on a site unless the intent is to be deceptive and manipulate search results. The real cost is indirect: your pages split rankings, backlinks, and crawl budget with the duplicate copy elsewhere.
Is content syndication considered duplicate content? Yes, technically it is duplicate content, but Google treats it as legitimate as long as it is disclosed honestly. Use a cross-domain rel=canonical tag on the syndicated copy pointing back to your original, or ask the publisher to add one, so search engines know which version to rank. Without that signal, the syndicating site, often with more authority, can outrank the original source.
How do you fix duplicate content across domains you own? Pick one domain as the canonical version and either 301 redirect the duplicate domain to it, or add a cross-domain rel=canonical tag on every duplicate page pointing to its matching page on the preferred domain. Redirects are the stronger choice when you're retiring a domain entirely; canonical tags work when both domains need to stay live.
What is a cross-domain canonical tag? It is a rel=canonical link element placed in the head of a duplicate page that points to the preferred URL on a different domain, not just a different page on the same site. Google added support for this in December 2009 so publishers and syndication partners could consolidate ranking signals without redirecting traffic away. It is a strong signal, not a guarantee, so Google can still choose a different canonical if other signals disagree.
How do you handle scraped or stolen content on another domain? First confirm your original was published first, using Search Console's index coverage dates or the Wayback Machine. Then file a removal request through Google's content removal tool, which usually gets the scraped page removed from search results within days, and contact the site's host directly if the scraper ignores it.
Does duplicate content on different domains hurt both sites or just one? Usually just the domain Google decides is not the canonical source, though both can suffer if the split is unclear. Google's ranking systems pick one version to show in results, often based on authority, internal links, and canonical signals, and filter the other out of most searches, so the weaker domain effectively becomes invisible for that content.
How is duplicate content on different domains different from hreflang duplicate content? Hreflang duplicate content is a narrower, technical case: near-identical pages in different languages or regions that use hreflang tags to tell Google which version to show which audience, and problems arise from broken return links or misconfigured tags. Cross-domain duplicate content is broader and covers syndication, scraping, and franchise or product-feed duplication that has nothing to do with hreflang at all.
How do you detect duplicate content across different domains? Run your key pages through Copyscape or Siteliner to find exact matches elsewhere online, and use Ahrefs' Site Explorer or a Google search of an exact phrase in quotes to check whether a competing domain ranks for your wording. For content you syndicate on purpose, keep a simple log of which domains have permission so an unexpected match is easy to spot.
Can two different domains legally use the same content? Yes, if the content owner licenses or syndicates it deliberately, which is common in press releases, guest posts, and franchise agreements. The SEO risk isn't legality, it's ranking dilution. Use a cross-domain canonical tag or a clear originally-published-on attribution link so search engines and readers both know which domain is the source.
Start by finding out whether you actually have a cross-domain duplication problem: run your most important pages through a plagiarism checker and check Search Console for pages that dropped out of the index unexpectedly. Then match the fix to the cause, canonical for syndication, redirects for retired domains, unique detail for franchise and international pages, and a removal request for scrapers. If you'd rather have someone else run that audit and fix what it finds, request a free SEO audit from Rankite.
Get a free, no-obligation SEO audit and a 30-minute strategy session. We'll show you exactly where the growth is hiding.
Fill out the form and we'll get back to you within one business day. Prefer email? Write to us directly at contact@rankite.com.