Hreflang and duplicate content: stop language versions competing
Short answer Fully translated pages are not duplicate content. Google only merges language versions when the main text is left untranslated, or when two pages share a language, like US and Canadian English. Give each version a canonical tag pointing to itself, link all versions both ways with hreflang, and check URL Inspection to see which page Google picked.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callDo translated pages count as duplicate content?
No, if the main text is translated. Google's rule:
"Localized versions of a page are only considered duplicates if the main content of the page remains untranslated." (Google Search Central: Tell Google about localized versions of your page)
So a Spanish service page and its English original don't compete. There is also no penalty here: duplicates get grouped, and Google shows one of them (see duplicate content). The risk is the wrong one showing up, or one version dropping out of results.
Language versions really do collide in two cases:
| Case | What Google does |
|---|---|
| Only the menu and footer are translated; the body stays in English | Treats the pages as duplicates and may show just one (Google Search Central: What is URL canonicalization) |
| Same language, different country: a US page and a Canadian page in English, or Quebec and France pages in French | Groups them as regional duplicates unless you label them; Google asks for both canonical tags and hreflang (same page) |
Same language for the US and Canada: how to keep both pages
Label them, and let each page claim itself. Google's instruction for regional variants:
"For regional variants in the same language (for example, a piece of content for the USA and the UK that's accessible at different URLs but in the same language), use both canonicalization and hreflang to help Google better understand which regional URL to show in search results." (Google Search Central: What is URL canonicalization)
In practice, for /us/ and /ca/ pages:
- Each page's canonical tag points to itself (Google calls this a self-referential canonical and recommends it, per its canonical URL guide).
- Both pages carry the same hreflang set: en-US, en-CA, and an x-default for everyone else.
- Make the pages really differ where the countries do: prices in USD or CAD, taxes, phone numbers, licences, service areas. Google lists local addresses, phone numbers and currency among the signals of who a page is for (Google Search Central: Managing multi-regional and multilingual sites).
If the two pages are word for word the same, Google may still pick one as canonical. Canonical tags are "a hint, not a rule" (Google Search Central: What is URL canonicalization). The hreflang labels help the right URL show in each country even then.
Hreflang and canonical tags: the rules that stop conflicts
Most clashes come from the two tags pointing in different directions. Google's rules:
| Rule | Source |
|---|---|
| Point each page's canonical to a page in the same language, never to the English original | "If you're using hreflang elements, make sure to specify a canonical page in the same language, or the best possible substitute language if a canonical page doesn't exist for the same language." (Google: How to specify a canonical URL) |
| Links must go both ways | "If two pages don't both point to each other, the tags will be ignored." (Google: Localized versions) |
| Each version lists itself and every other version | Google: Localized versions |
| Don't use noindex to pick a version | It "will completely block the page from Search" (Google: How to specify a canonical URL) |
| Use full https:// URLs in the hreflang set | Alternate URLs "must be fully-qualified" (Google: Localized versions); list HTTPS, not HTTP, versions (Google: How to specify a canonical URL) |
| Don't auto-redirect visitors by language | Such redirects "could prevent users (and search engines) from viewing all the versions of your site"; offer a language switcher instead (Google: Managing multi-regional and multilingual sites) |
| A canonical tag with an hreflang attribute does nothing | Canonical tags "with hreflang, lang, media, and type attributes are not used for canonicalization" (Google: How to specify a canonical URL) |
A helpful side effect: when Google picks a canonical, it prefers URLs that sit in a working hreflang group over ones left out (Google: How to specify a canonical URL). A page missing from the group is the one more likely to drop.
Hreflang codes that break silently
A wrong code doesn't raise an error. Google just ignores it.
| Code | Valid? | Why |
|---|---|---|
| es-US, en-CA, fr-CA | Yes | Language first, then country |
| es-419 (Latin American Spanish) | No | Google names it as not supported (Google: Localized versions); use es, or es-US for Spanish speakers in the US |
| en-UK | No | The country code for Britain is GB; UK has no effect (same page) |
| US or CA alone | No | "Specifying the region alone is not valid" (same page) |
| zh-Hant, zh-Hans | Yes | Script codes for Traditional and Simplified Chinese (same page) |
Google also ignores the folder name: /es/ or es.example.com tells it nothing about the audience without hreflang (same page).
How to check if Google merged your language versions
Use URL Inspection in Search Console. Google's troubleshooting guide says to compare the Google-selected canonical with yours (Google Search Central: Fix canonicalization issues).
- Inspect the translated or regional URL.
- Read "Google-selected canonical". If it is the page itself, that version stands on its own.
- If it shows another language or country version, fix the cause: untranslated body, one-way hreflang, or a canonical pointing elsewhere.
- Click Request Indexing so Google looks again (same page).
Google names "language variants without localized annotations" as one of the most common canonical problems (same page). More on the report: Google Search Console for a small business.
Example
A roofer with US and Canadian pages
Two English pages, /us/roof-repair/ and /ca/roof-repair/, identical except the price. URL Inspection shows the Canadian page's chosen canonical is the US page. Fix: self-canonicals on both, an en-US and en-CA hreflang pair, and CAD prices, the provincial licence and a Canadian phone number on /ca/.
A clinic whose French pages point to English
Its site plugin set every French page's canonical to the English page. French pages disappear from results. Fix: each French page points its canonical to itself.
A restaurant with a half-translated Spanish menu
Only the buttons were translated; dish names and descriptions stayed in English. Google treats /es/menu as a copy of /menu. Fix: translate the descriptions, or drop the /es/ page.
FAQ
Does hreflang fix duplicate content?
Not on its own. It tells Google which version suits which searcher. If the main text is untranslated, the pages are still duplicates, and Google may still show only one.
Should translated pages have a canonical to the original?
No. Each translation's canonical points to itself. Pointing it to the English page tells Google the translation is a copy, and the translation can drop from results.
Do I need hreflang if each page is fully translated?
It is not required; Google can find language versions without it. Google still says it is usually best to label them, so each searcher lands on their own language.
HTML tags, sitemap or HTTP header: which is best?
Google says the three methods are equivalent. Pick the one your website platform makes easiest.
Is automatic translation duplicate content?
Not as duplicate content. But Google's spam policy lists mass-made pages from automated translating that add little value as scaled content abuse. See multilingual website SEO.
Different for you?
- You are adding a second language from scratch, or serve Quebec: Multilingual website SEO.
- Your duplicates are in one language (http, www, tracking links): Duplicate content.
- A version shows "Crawled, currently not indexed": Page not indexed in Search Console.
- You want the site built in two languages: Website agent.
- You want each version found in search and AI answers: SEO & GEO agent.