Cross-Language Duplicate Content

TL;DR — Translating a page into another language does not create duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. in Google’s eyes — a German page and its English version are different content, full stop. The thing people call “cross-language duplicate content” is mostly a myth. The real risk is the opposite: same-language pages for different countries (a US, UK, and Australia version) that are nearly identical, with no real differences. Those Google can treat as duplicates.

The myth in one line

You’ll hear that if you translate your content into Spanish, French, and German, Google will flag all those versions as duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. That’s not true, and it’s never been true. Google’s own documentation says translated pages are only considered duplicates if the main content stays untranslated. Once you actually translate the words, they’re different content.

Google determines the language from the visible content, not from hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., the HTML lang attribute, or the URL.

That makes sense if you think about it: a search engine that treated translations as duplicates would be punishing every multilingual site on the web — and hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., the whole system Google built for multilingual sites, would make no sense.

What’s actually at risk

The real problem is the mirror image of the myth. Say you’re an English-language store and you make three copies of a page:

• example.com/us/ for the United States
• example.com/uk/ for the United Kingdom
• example.com/au/ for Australia

If those three pages are basically identical — same words, same prices, no real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. — then that is genuine duplicate content. They’re all in the same language, and there’s nothing meaningfully different between them. Google may decide they’re duplicates, group them together, and pick just one to show. Your carefully planned per-country setup can quietly collapse into a single page.

So what fixes it?

Not more tags. The fix is real differences:

• Different currency and pricing (USD vs. GBP vs. AUD).
• Different spelling and wording (color/colour, and local phrasing).
• Different shipping, returns, tax, and legal text.
• Genuinely different examples or products where they apply.

If your country pages are truly different, they’re not duplicates. If they’re clones with a flag swapped in the corner, no amount of hreflang will force Google to keep them all separate.

Where hreflang fits

hreflang is not a duplicate-content fix. It’s a way of telling Google, “these pages are versions of each other — show the right one to the right person.” It can help Google swap in your UK page for a UK searcher even inside a duplicate group, but it’s a hint, not a command, and it doesn’t stop the grouping from happening. The way to keep separate country pages is to make them genuinely different.

Want the deeper version — how Google’s clustering actually works, why a page can “disappear” from Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. while still ranking, and the real data on how often hreflang breaks? Switch to the Advanced tab.

Troubleshooting duplicate-content symptoms across locales

A translated page is reported as a duplicate

Symptom: an audit groups two different-language URLs together. Likely cause: the main content was never translated, only navigation and boilerplate changed, or the tool is comparing markup rather than language. Fix: inspect the rendered main content; complete the translation where it remains the same and keep legitimate translations on separate self-canonical URLsHow search engines pick one canonical URL among duplicates and consolidate signals onto it..

A regional page disappears from canonical reporting

Symptom: Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. reports one same-language country page as the canonical for another. Likely cause: the regional pages are near-identical, so Google clustered them. Fix: confirm whether the intended URL is still being swapped for the right audience; if the market truly needs a separate page, localize currency, availability, legal details, and search intent rather than adding more tags.

Hreflang is correct but the wrong regional URL appears

Symptom: a different same-language country version is shown in search. Likely cause: hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is only a hint and weak content differentiation or canonical conflicts outweigh it. Fix: align self-canonicals, repair reciprocal annotations, and make the regional distinction substantive; consolidate variants that do not need to differ.

Localized URLs canonicalize to the source-language page

Symptom: translated pages declare the original URL as canonical and fail to remain independently indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. Likely cause: a shared template applies a cross-language canonical. Fix: use self-canonicals for genuine translated alternates and connect them with reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. instead.

TL;DR — “Cross-language duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.” is mostly a myth: Google’s docs say localized versions are only duplicates if the main content stays untranslated, so real translations are different content. The genuine risk is same-language, different-country near-duplicates (en-US/en-GB/en-AU with no localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native.) — those get clustered and one canonical is picked, which can undo your geotargetingConfiguring a site or URL to target users in a specific country.. hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. doesn’t prevent clustering; it’s a swap signal inside a cluster, and a hint at that. In my study of 374,756 hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.-using domains, 67% had at least one hreflang issue. Watch the Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. trap: a consolidated regional page can vanish from canonical reporting while still being served correctly. The fix is real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. or consolidation, not more tags.

The myth, and why it’s backwards

The head term “cross-language duplicate contentThe mostly-mythical idea that translating content into different languages creates duplicate content. It doesn't — translations are different content to Google. The real risk is the mirror image: near-identical same-language pages across country variants (en-US/en-GB/en-AU), which Google may cluster and consolidate.” carries a myth baked into it — the assumption that translating a page into another language creates duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. It doesn’t, and Google is unusually direct about it. In its localized-versions guidance, Google states that “Localized versions of a page are only considered duplicates if the main content of the page remains untranslated.” Translate the main content and the pages are different content, period.

This is the whole premise hreflang is built on. Google says to “Use hreflang to tell Google about the variations of your content, so that we can understand that these pages are localized variations of the same content.” It’s a mapping tool for legitimately different alternates — not a patch for a duplication problem that, for genuine translations, doesn’t exist. (And don’t conflate hreflang with language detection: Google “doesn’t use hreflang or the HTML lang attribute to detect the language of a page; instead, we use algorithms to determine the language.”)

Matt Cutts said the same thing about untranslated English across ccTLDsCountry-code top-level domain like .de or .co.uk — a strong geotargeting signal. back in 2011: as reported by Search Engine Roundtable, running the same English content across .com, .fr, and .de is not an issue for Google — and if you can, hire a translator and implement hreflang, but there’s no need to panic. This has been Google’s consistent position for well over a decade.

The one nuance: boilerplate-only translation

The “main content remains untranslated” test has a trap in it. If you translate only the template — the menu, nav, footer, sidebar boilerplate — but leave the main body copy in the original language, you haven’t actually translated the page. Google’s test is about the main content, not the chrome around it. In my Ahrefs canonicalization guide I call this out as a distinct duplicate pattern: the case where menus and repeated page text are translated but the main content is not. Half-translating a page doesn’t get you out of the duplicate bucket — it’s whether the main content changed that matters, not whether something on the page changed.

When you’re auditing for this, check the rendered, visible page — not just the source markup. Google determines a page’s language from what’s actually visible to users, not from hreflang, the HTML lang attribute, or the URL. Evidence for this claim Google says it determines page language from visible content rather than hreflang, the HTML lang attribute, or the URL. Scope: Google Search language detection, not browser or accessibility behavior. Confidence: high · Verified: 2026-07-14 Google: Make page language obvious A template that swaps lang="fr" into the <html> tag while the main content block still renders in English hasn’t translated anything Google’s language detection or duplicate-content check cares about — pull up the live page and read the main content block itself.

The real risk: same-language, different-country near-duplicates

Here’s the scenario the myth distracts from. You have multiple pages in the same language targeting different countries — en-US, en-GB, en-AU, or de-DE/de-CH — and they’re near-identical, with no real localization of currency, spelling, regulation, shipping, or examples. That is genuine duplicate content.

Google’s multi-regional sites guidance addresses this head-on: “if you have multiple pages in the same language as part of a multi-regional site (for instance, if both example.de/ and example.com/de/ show similar German language content), pick a preferred version and use the rel=“canonical” element and hreflang tags to make sure that the correct language or regional URL is served to searchers.” Note the framing: Google isn’t telling you the pages aren’t duplicates — it’s telling you to manage the duplication with canonical + hreflang.

How the clustering actually works

On Google’s Search Off the Record podcast (Episode 16), the Search Relations team walked through exactly this mechanic using a German/Swiss-German example. John Mueller: “we have, at the same time, systems that try to understand when content is duplicated, and we try to put them into one cluster of pages, and then sometimes, the German and the Swiss page will get into the same cluster. But with hreflang, we can show the proper URL, at least.” Martin Splitt added that this generally isn’t a problem — “it makes sense that these are put together in the same dup cluster… because it’s the same content, essentially.”

Read that carefully, because it’s the cruxChrome User Experience Report — Google's public dataset of real-world (field) performance data from eligible Chrome users. It's the official field-data source behind the Core Web Vitals program. of the whole topic: hreflang works inside the clustering, not against it. Google decides the pages are duplicates, clusters them, picks a canonical — and hreflang’s job is to help swap the served URL to the right one for the searcher. Gary Illyes described that swap as a ranking component: if you search in one language and the wrong-language page would come up, Google swaps in the right result. But the clustering still happened. hreflang didn’t prevent it; it just steered within it.

This is why I’ve been blunt in my canonicalization guide: hreflang does not solve duplication on international sites. Google will generally try to swap to show the correct version, but it’s not guaranteed, and this setup often breaks. In my Pubcon 2017 international SEO talk I put the failure in plain terms: how can you have A→B and B→A reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. if Google already thinks A=C and A isn’t even indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.? Once Google has deduped the pages, the hreflang cluster you built has nothing solid to hang on.

One caveat on the mechanics above: the cluster/swap explanation comes from Google’s Search Relations team talking through it on a podcast, not from a written spec, and the exact internal plumbing isn’t something Google documents step-by-step. Treat it as the clearest official explanation of the behavior, not a guaranteed implementation detail that never changes. For the durable, current rule, anchor on Google’s own multi-regional sites guidance and canonical URL guidance — pick a preferred version, align canonical and hreflang — and treat the podcast color as why that guidance exists, not as a separately verifiable mechanism.

The Search Console reporting trap

This is the part that panics practitioners, and it’s a genuinely underserved insight. Because Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. reports on the canonical URL, a consolidated same-language regional page can look like it disappeared even though it’s still being served correctly. On SOTR Ep. 16, Martin Splitt described exactly this: in the reporting it can look like “what happened to the Swiss page? That has disappeared” — because it’s now a duplicate of the German page — but that doesn’t mean Google isn’t still showing the Swiss page to people in Switzerland.

So if a regional page vanishes from your canonical/indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. reporting, don’t assume deindexingDeindexing means getting a URL to stop appearing in Google's search results. There's no single delete button — the right method depends on whether you own the page, whether removal is temporary or permanent, and whether the content should still exist.. In the same-language-cluster case, the page can be folded into another locale’s cluster for reporting purposes while still ranking for its intended audience. The practical diagnostic: if a locale page keeps losing to another locale’s version in canonical reporting, or the wrong country’s URL shows in a market’s SERP, that’s the symptom of same-language clustering — not a hreflang syntax bug, and not something more hreflang tags alone will necessarily fix. Confirm what’s actually being served (fetch the URL from the target market, or check rankings there directly) rather than relying on the canonical report alone — Search Console’s exact reporting behavior here isn’t spelled out in Google’s written docs, so verify against what’s live before you conclude anything.

Is there a penalty? No.

There’s no duplicate-content penalty here, and there never was. John Mueller, in a 2021 tweet reported by Search Engine Roundtable: “There’s no duplicate content penalty for something like that, but concentrating your site’s value on fewer pages generally makes it easier for those pages to be more visible.” That second clause is the real cost — not a penalty, but dilution. Splitting authority across near-identical clones makes each one weaker.

Worth being precise about what “no penalty” covers, though: this is about ordinary canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. — Google consolidating near-identical locale pages and picking one to rank, in good faith. It’s a different question from Google’s separate spam policies around scaled, low-value content or doorway pagesDoorway pages are pages or sites built to rank for specific search queries that then funnel users to a different destination instead of being useful in their own right. Google treats them as spam. built to manipulate rankings across country/language variants. That’s a manipulative-intent problem, not a same-language-clustering problem, and it’s evaluated separately. A site with honestly near-duplicate en-US/en-GB pages made without intent to deceive isn’t in penalty territory; a site mass-producing thin locale variants purely to capture more search real estate is a different case.

Bing covers similar ground, worth noting separately since it’s Bing’s own guidance, not Google’s. In its December 2025 duplicate-content post, Bing states that localization creates duplicate content when regional or language pages are nearly identical and don’t provide meaningful differences for users in each market — and its fix is directionally similar to Google’s: differentiate meaningfully (terminology, examples, regulations, product details), use hreflang where applicable, and canonicalize variations that don’t represent a distinct search intent. Bing also says AI systems cluster near-duplicate URLs into one representative page, which is worth flagging as Bing’s own AI-search observation rather than a confirmed Google behavior. (Note that Bing barely uses hreflang in the first place — it leans on the content-language signal — so on Bing the differentiation matters even more than the tagging.)

What the data says: hreflang breaks a lot

If you’re leaning on hreflang to keep your regional variants straight, know how fragile it is in the wild. In my Brighton SEO 2023 study of 374,756 domains, 67% of domains using hreflang had at least one issue — missing x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\", missing self-referencing tags, referencing redirected or broken pages, missing reciprocal tags, pointing to non-canonical URLs, and more. hreflang is one of roughly 20 canonicalization signals, and a broken cluster just means Google ignores the pairing and falls back to normal duplicate handling. So if your defense against same-language consolidation is a hreflang cluster, and two thirds of clusters in the wild are broken, that defense is shakier than most people assume. Even Mueller has said he’s often surprised when people get hreflang right, given all the complexity.

How to actually fix it

1. Decide whether the variants genuinely differ. If en-US and en-GB really have different currency, pricing, shipping, legal text, and spelling — good, they’re not duplicates. If they’re clones, that’s your problem, not your tags.
2. Localize for real, or consolidate. The fix is either genuine localization (currency, spelling, regulatory content, examples) or fewer pages. Sometimes the right technical answer is one well-differentiated page, not three clones plus hreflang. Mueller’s “concentrate value on fewer pages” applies directly.
3. Align canonical + hreflang + x-default so they don’t contradict. Each locale should self-reference its canonical; the hreflang cluster should reference every locale including itself; x-default should point at a sensible fallback. The classic self-inflicted wound — my “Mistake #5” from my hreflang guide — is hreflang pointing at a page whose rel=canonical says it’s non-authoritative. Contradictory signals get you ignored. This cuts the other way too: don’t cross-canonicalize a genuine translation back to the source-language page just to quiet a duplicate-content worry that doesn’t apply to it. Google’s canonical URL guidance is specific here — a page’s canonical should be in the same language as the page itself, or the best available substitute if no same-language canonical exists. Canonicalizing a translated page to a different-language original doesn’t fix anything; it just tells Google the localized URL isn’t the one to show, which can knock it out of that market’s results entirely.
4. Diagnose in Search Console, but read it correctly. A regional page missing from canonical reporting may be consolidated, not deindexed. Confirm what’s actually being served to the target market before you “fix” a non-problem.

How this connects to the rest of the cluster

This piece owns the duplicate-content angle; its siblings own the adjacent decisions. Whether you even need a per-country variant is the language-vs-country-targeting question. The tag mechanics — reciprocal clusters, valid ISO codes, the three implementation methods — belong to hreflang, and the fallback value has its own x-default treatment. And the difference between merely translating words and truly adapting a page for a market is the translation-vs-localization distinction — which is exactly what turns a near-duplicate country clone into genuinely different content. Machine-translation quality is a separate risk again; don’t conflate thin auto-translation with the cross-language duplicate myth.

AI summary

A condensed take on the Advanced version:

• The myth is backwards. Google does not treat translations as duplicate content. Per Google’s docs, localized versions are only duplicates “if the main content of the page remains untranslated.” Translate the main content and the pages are different content.
• hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.’s whole premise is mapping legitimately different language/locale alternates — it is not a duplicate-content fix.
• The real risk is the mirror image: same-language, different-country near-duplicatesThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. (en-US/en-GB/en-AU, de-DE/de-CH) with no real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. of currency, spelling, regulation, or content. Those are genuine duplicates.
• Boilerplate-only translation still fails the test. It’s whether the main content changed, not whether the menu/nav is translated.
• Google clusters near-duplicates and picks one canonical. hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. works inside the cluster (a swap signal), not against it — it doesn’t stop the clustering, and it’s a hint, not a directive.
• Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. trap: a consolidated regional page can “disappear” from canonical reporting while still being served correctly to its market. Don’t mistake consolidation for deindexingDeindexing means getting a URL to stop appearing in Google's search results. There's no single delete button — the right method depends on whether you own the page, whether removal is temporary or permanent, and whether the content should still exist. — but confirm what’s actually live rather than assuming; the exact swap/reporting mechanics come from a Google podcast explanation, not a written spec.
• No penalty (Mueller, 2021) for ordinary consolidation, but concentrating value on fewer pages makes them more visible. That’s separate from Google’s spam policies around manipulative scaled or doorway content, which are a different, intent-based question. Bing frames a similar reality in its own guidance and adds that AI systems cluster near-duplicates too.
• Data: in my 374,756-domain study, 67% of hreflang-using domains had at least one issue — so leaning on hreflang to preserve variants is fragile.
• The fix is real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. or consolidation, not more tags — plus aligning canonical + hreflang + x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\" so they don’t contradict, and never cross-canonicalizing a real translation back to a different-language original.

Official documentation

Primary-source documentation from the search engines.

Google

• Tell Google about localized versions of your page — the source of the core myth-bust: translated main content isn’t duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling., and what hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is actually for.
• Managing multi-regional and multilingual sites — the same-language-different-region case (example.de/ vs. example.com/de/) and the canonical + hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. fix; also the localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. signals Google looks at (local language and currency, addresses, phone numbers).
• Search Off the Record, Episode 16 — “How serving works, hreflang, and more” — the clearest official walkthrough of same-language clustering, the swap mechanism, and the Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. reporting trap.

Bing / Microsoft

• Does Duplicate Content Hurt SEO and AI Search Visibility? (Dec 2025) — Bing on when localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. creates duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling., how to differentiate meaningfully, and how AI systems cluster near-duplicate URLs.

Quotes from the source

On-the-record statements from Google and Bing. Each link is a deep link that jumps to the quoted passage on the source page (podcast lines are timestamped, since the transcript is a PDF with no page anchor).

Google — translated content is not duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. (the myth-bust)

• “Localized versions of a page are only considered duplicates if the main content of the page remains untranslated.” — Google Search Central docs. Jump to quote
• “Use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. to tell Google about the variations of your content, so that we can understand that these pages are localized variations of the same content.” Jump to quote
• “Google doesn’t use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. or the HTML lang attributeThe HTML lang attribute is a global attribute — most importantly set on the <html> element (<html lang=\"en\">) — that declares the natural language of THIS document's content using a BCP 47 language tag (en, es, en-US, pt-BR). It's distinct from hreflang, which points to alternate-language URLs. Google ignores lang for language detection; Bing uses it as a fallback targeting signal; and it drives accessibility (screen-reader pronunciation) and the browser auto-translate prompt. to detect the language of a page; instead, we use algorithms to determine the language.” Jump to quote

Google — the genuine same-language-different-region case, and the fix

• “…if you have multiple pages in the same language as part of a multi-regional site (for instance, if both example.de/ and example.com/de/ show similar German language content), pick a preferred version and use the rel=“canonical” element and hreflang tags to make sure that the correct language or regional URL is served to searchers.” — Google Search Central docs. Jump to quote
• “Other signals to identify the intended audience of your site can include local addresses and phone numbers on the pages, the use of local language and currency, links from other local sites, or signals from your Business Profile (where available).” Jump to quote

Google — how the clustering and swap work (Search Off the Record, Ep. 16)

• John Mueller: “we have, at the same time, systems that try to understand when content is duplicated, and we try to put them into one cluster of pages, and then sometimes, the German and the Swiss page will get into the same cluster. But with hreflang, we can show the proper URL, at least.” — SOTR Ep. 16, ~00:26:59.
• Martin Splitt: “it makes sense that these are put together in the same dup cluster, or duplication cluster, because it’s the same content, essentially.” — SOTR Ep. 16, ~00:27:23.
• Martin Splitt, on the reporting trap: the Swiss page can look like it “has disappeared because it’s now a duplicate of the German page, but that doesn’t mean that we are not showing the Swiss page to people in Switzerland.” — SOTR Ep. 16, ~00:27:35.
• John Mueller, on hreflang’s difficulty: “I’m often surprised when people get things right with regards to hreflang because of all of the complexity.” — SOTR Ep. 16, ~00:17:50.

Google — no penalty (via Search Engine Roundtable’s embedded tweet)

• John Mueller (May 2021): “There’s no duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. penalty for something like that, but concentrating your site’s value on fewer pages generally makes it easier for those pages to be more visible.” Read the coverage

Is this actually a duplicate-content problem — or a legitimate translation?

Work top to bottom. Most “cross-language duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.” worries dissolve at Step 1.

Step 1 — Are the pages in different languages or the same language?

• Different languages (English vs. German vs. Spanish, main content genuinely translated) → Not a duplicate-content problem. These are different content to Google. Use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. to map the alternates and move on. Stop here.
• Same language, different country/region (en-US vs. en-GB vs. en-AU) → possible real duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. Go to Step 2.

Step 2 — Is the main content translated, or just the boilerplate? (for the different-language path, sanity-check this)

• Only the menu/nav/footer is translated, main body copy unchanged → still effectively duplicate. Google’s test is about the main content. Translate the body or you’re not out of the bucket.
• Main content genuinely translated → different content, not a duplicate.

Step 3 — Do the same-language country pages genuinely differ? Check the substance: currency, pricing, spelling conventions, shipping/returns, tax, legal/regulatory text, product availability, examples.

• Yes — real, maintained differences → not duplicates. Keep them separate; align canonical + hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. + x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\" so signals don’t contradict.
• No — near-identical clones → genuine duplicate content. Go to Step 4.

Step 4 — Localize or consolidate?

• The market justifies real localized content → localize for real (currency, spelling, legal, examples). Then the pages aren’t duplicates.
• The market doesn’t justify unique content → consolidate. Fewer, stronger pages beat a sprawl of clones; concentrating value makes them more visible.

Reality check on hreflang: at no step does adding hreflang convert duplicates into non-duplicates. hreflang helps Google serve the right URL from a cluster; it never stops the clustering. If your only “fix” is more tags, you haven’t fixed the duplication.

Common myths and mistakes

The recurring ways this topic goes wrong — and what to do instead.

1. “Google penalizes translated content as duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling..” Why it’s wrong: Google’s docs say translated main content isn’t duplicate at all, and there’s no duplicate-content penalty mechanism to begin with (Mueller, 2021). Do instead: translate freely, map the alternates with hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., and stop worrying about a penalty that doesn’t exist.

2. “hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. prevents duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling..” Why it’s wrong: hreflang works inside Google’s clustering, not against it — “we try to put them into one cluster… but with hreflang, we can show the proper URL, at least.” It’s a swap signal, and a hint, not a directive. Do instead: treat hreflang as version-swapping, not de-duplication. Prevent duplication with genuine content differences or fewer pages.

3. “If my hreflang is correct, Google will always show the exact URL I specified.” Why it’s wrong: hreflang is a hint. Google can and does ignore it when other signals (content similarity, canonical, site structureWebsite structure (site architecture) is a site's visible hierarchy, navigation, breadcrumbs, and URL organization — how pages relate and how people and search engines move between them. Internal linking is the primary signal Google reads to understand that structure, not URL folders.) conflict — and in my study, 67% of the hreflang-using domains in the study had at least one issue anyway. Do instead: align every signal (canonical, internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them., hreflang, x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\"), then verify what Google actually serves.

4. “Same-language regional pages need heavy translation to avoid duplicates.” Why it’s wrong: en-US and en-GB are already the same language — there’s nothing to translate. What they need is localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native., not translation. Do instead: differentiate on currency, spelling, shipping, legal/regulatory content, and examples — real differences, not linguistic ones.

5. “Translating only the menu and nav is enough.” Why it’s wrong: Google’s duplicate test is about the main content. Boilerplate- only translation leaves the main content untranslated, so it still trips the test. Do instead: translate the main content itself, not just the template around it.

6. “hreflang to a non-canonical page is fine.” Why it’s wrong: if rel=canonical says a page is non-authoritative while hreflang points at it as a distinct target, you’ve sent Google contradictory signals — my “Mistake #5.” Contradictions get ignored. Do instead: each locale self-references its canonical; the hreflang cluster references every locale including itself.

7. “My UK page disappeared from Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., so it’s been deindexed.” Why it’s wrong: in the same-language-cluster case, a regional page can vanish from canonical reporting because it’s folded into another locale’s cluster, while still being served to the right market (per Google’s own podcast). Do instead: confirm what’s actually served to the target market before treating consolidation as deindexingDeindexing means getting a URL to stop appearing in Google's search results. There's no single delete button — the right method depends on whether you own the page, whether removal is temporary or permanent, and whether the content should still exist..

8. “Machine-translated content is automatically duplicate content.” Why it’s wrong: MT quality and thin-content concerns are a different risk, not the cross-language duplicate myth. Google judges translated content on user value, not by whether a machine produced it. Do instead: keep the two issues separate — worry about MT quality, not MT-as-duplication.

Worked examples

Four scenarios that separate the myth from the real risk.

1. Full translation — English, German, Spanish (not a duplicate) A SaaS marketing site with its main content genuinely translated into German and Spanish. Different words, same meaning.

• Verdict: not duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. These are different content to Google.
• What to do: map the three with reciprocal hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others.; nothing else needed for duplication. The myth stops here.

2. Boilerplate-only “translation” (still effectively duplicate) A page where the nav, footer, and sidebar are translated into French, but the main article body is left in English.

• Verdict: the main content is untranslated, so it can still be treated as effectively duplicate — this is the trap in Google’s “main content remains untranslated” test.
• What to do: translate the main body, or don’t ship the “French” page at all.

3. en-US vs. en-GB vs. en-AU clones (genuine duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.) An English store spins up three country folders that are byte-for-byte identical — same USD prices, same copy, same everything, just a different flag icon.

• Verdict: genuine duplicate content. Same language, no real differences. Google may cluster them and pick one canonical, quietly collapsing the setup.
• What to do: localize for real (GBP/AUD pricing, spelling, shipping, legal), or consolidate to fewer pages. hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. won’t save clones.

4. de-DE vs. de-CH, properly localized (not a duplicate) A German-language site with a Germany version and a Switzerland version — different pricing in EUR vs. CHF, Swiss-specific shipping and legal text, and Swiss High German spelling conventions (e.g. no ß).

• Verdict: genuinely differentiated same-language pages — not clones. Keep them separate.
• What to do: self-referencing canonical per locale, a reciprocal hreflangIf page A lists page B as an alternate, B must list A back — or Google ignores the pair. cluster (de-DE, de-CH), and a sensible x-defaultx-default is the reserved hreflang value that points to a fallback URL — the page Google shows when a user's locale doesn't match any of your other hreflang tags. It is optional and does not mean \"English.\". Signals aligned, no contradictions.

The through-line: different language is almost never the problem; same language with no real differences almost always is.

Test yourself: Cross-Language Duplicate Content

Five quick questions on the myth, the real risk, and how hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. actually fits. Pick an answer for each, then check.

Resources worth your time

My related writing

• Google Uses ~40 Canonicalization Signals — my canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. guide, including why hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. doesn’t solve international duplication and the boilerplate-translation duplicate pattern.
• Hreflang: The Easy Guide for Beginners — implementation, the reciprocal/self-referencing rules, and the “hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. to non-canonical” mistake.
• Duplicate, Google Chose Different Canonical Than User — the exact GSCA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. status you’ll hit when a locale page gets consolidated, and how to align signals.
• The Beginner’s Guide to Technical SEO — where duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. and international setups fit in the bigger picture.

My speaking

• The most common hreflang issues across 374,756 domains — Brighton SEO 2023 (slides · video) — the study behind the 67%-of-domains-have-an-issue stat, framing hreflang as one of ~20 canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. signals.
• You’re Going To Screw Up International SEO — Pubcon Vegas 2017 (SlideShare) — why hreflang breaks after Google has already deduped your pages, and the implementation chaos around it.

Official

• Google — Tell Google about localized versions of your page — the myth-bust straight from the source.
• Google — Managing multi-regional and multilingual sites — the same-language-different-region case and the canonical + hreflang fix.
• Bing — Does Duplicate Content Hurt SEO and AI Search Visibility? (Dec 2025).

From around the industry

• Search Off the Record, Ep. 16 — How serving works, hreflang, and more (Google Search Relations) — the clustering, the swap mechanism, and the Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. reporting trap, in Google’s own words.
• Internationalized Sites Even With Same English Content Not Always Treated As Duplicate Content By Google (Search Engine Roundtable, Barry Schwartz) — Matt Cutts (2011), John Mueller’s “no penalty” tweet (2021), and Gianluca Fiorelli’s caution.
• Hreflang, International SEO & Duplicate Content: How To Fix It (thegray.company) — one of the better competing pieces; correctly separates multilingual (no risk) from same-language-different-region (real risk).
• The myth of the duplicate content penalty (Search Engine Land) — the broader “no penalty” reality this topic sits inside.
• 6 Common Hreflang Tag Mistakes Sabotaging Your International SEO (Search Engine Journal) — the recurring implementation errors, including hreflang-to-non-canonical.
• r/TechSEO — the community for hreflang and duplicate-content debugging.

Cross-Language Duplicate Content

The mostly-mythical idea that translating content into different languages creates duplicate content. It doesn't — translations are different content to Google. The real risk is the mirror image: near-identical same-language pages across country variants (en-US/en-GB/en-AU), which Google may cluster and consolidate.

Parent concept: Duplicate Content · Related: Duplicate Content, Hreflang, Canonicalization

Cross-Language Duplicate Content

Cross-language duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. is the widely repeated idea that Google treats the same content translated into different languages as duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. It doesn’t. Google’s documentation is explicit that localized versions of a page are only considered duplicates if the main content of the page remains untranslated — a fully translated German page and its English original are different content to Google’s systems. That’s the entire premise hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is built on: it maps legitimately different language/locale alternates to each other, it isn’t a duplicate-content fix.

The real risk hiding behind the term is almost the opposite scenario: same-language duplication across near-identical country/region versions. An en-US, en-GB, and en-AU version of a page that are byte-for-byte or near-identical — no real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. of currency, spelling, regulation, or content — is genuine duplicate content. Google’s systems may cluster those pages and pick one canonical version to show, which can undermine the geotargetingConfiguring a site or URL to target users in a specific country. intent even when hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is implemented correctly.

hreflang doesn’t stop the clustering; it’s a signal that can help Google swap in the right URL for the right searcher within a duplicate cluster, but it isn’t guaranteed and it often breaks. The fix for genuine same-language duplication is real localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. or consolidation — not more tags.

Parent concept: Duplicate Content · Related: Duplicate Content, Hreflang, Canonicalization

Changelog