Duplication6 min readEntry updated
Multilingual duplication on adult sites: when language versions compete, and how to stop it
Translated pages are not duplicates in themselves, but multilingual sites still manage to compete with themselves. Half-translated pages, near-identical regional versions and canonicals pointing across languages are the usual causes. This entry explains how to tell the difference and fix each one.
01Translation is not duplication
Google's guidance on localised versions is clear that pages in different languages are only treated as duplicates when the main content has not been translated. A properly translated French page and its German twin are separate pages serving different people. Trouble starts when translation is partial, or when several versions share one language.
02Five situations that cause trouble
| Situation | What it looks like | Fix |
|---|---|---|
| Half-translated pages | Menu, footer or main copy still in the original language | Finish the translation of the main content |
| Same language, several regions | French pages for France, Belgium and Switzerland that are almost identical | Link with hreflang; merge if nothing useful differs |
| Canonical across languages | German page declares the English page as canonical | Self-referencing canonical on every version |
| Parameter versions | Same page reachable with ?lang=, ?currency= and a clean URL | One clean URL per version; parameters canonicalised |
| Gated duplicates | Explicit copy of an open page sitting behind the age check | Keep gated pages out of the index and out of hreflang sets |
03Same language, several markets
This is the most common real duplication. If your French pages for France, Belgium and Switzerland differ only in a line or two, search engines may pick one to show everywhere. Give each version a reason to exist, such as local prices, delivery or legal details, and connect them with hreflang using region codes. If nothing useful differs, a single French version is usually the better choice. Codes and tagging are explained in our hreflang entry.
04The adult-site version of the problem
Adult sites sometimes publish an open, safe-for-work page and a more explicit twin behind the age check with almost the same text. Keep the gated twin out of the index, out of sitemaps and out of hreflang, so it never competes with the open page. The structure decisions behind this are covered in our entry on international structure.
05Finding duplication early
- Search Console: look for pages marked as duplicates where Google chose a different canonical.
- Crawl each language version and flag pages with large blocks of the original language.
- Compare regional versions in the same language for real differences.
- Check every canonical points to its own language.
The ongoing work sits under multilingual SEO.
06Canonical tags across languages
Each language version should carry a canonical tag pointing to itself. Pointing the French page's canonical to the English page tells search engines the French page is a copy to ignore, which removes it from French results. This is one of the commonest errors on multilingual sites, often introduced by a theme or plugin default.
07Partly translated pages
Pages with translated headings but English body text, or translated text with English reviews and menus, send mixed signals about their language. Search engines may treat them as duplicates of the English page or rank them poorly in both languages. Finish the translation of a page before publishing it, and keep untranslated sections, such as user reviews, clearly separate.
08Reviews and user content in several languages
Customer reviews are often written in the reviewer's language. Showing them as written, with a note of the language, is honest and avoids machine-translated reviews that read badly. If you translate reviews automatically, label them as translated and keep the original available. Never invent or edit reviews in any language.
09Parameters and language switching
Sites that switch language with a parameter, such as ?lang=fr, or with a cookie, often end up with the same URL showing different languages, which search engines cannot index separately. Each language needs its own stable URL. If your platform uses parameters, map them to clean folder URLs before launching more languages.
10Gated twins and duplicate content
When an open page and a gated page cover the same product with similar text, search engines may treat them as duplicates. Keep the gated version out of the index, mark it clearly with the adult rating if it is explicit, and make the open page the one that carries the descriptive text. Apply the same pattern in every language.
11A quarterly duplication check
- Crawl each language version and list pages with identical or near-identical titles.
- Check canonical tags on a sample of pages in every language.
- Look in Search Console for pages where Google chose a different canonical.
- Search a sentence from a key page in quotes to see which versions appear.
12Fixing what you find
Most duplication fixes are simple once found: correct a canonical, finish a translation, merge regional pages that add nothing, or give each version genuinely local details. Change one thing at a time and check the effect in Search Console after a few weeks. Hreflang, which ties the versions together, is covered in our hreflang guide.
13Why this matters more for adult sites
Adult sites often have more near-duplicate pages than others: product variants by size and colour, regional versions in shared languages, open and gated versions of similar content, and archives of older products. Each of these, multiplied across languages, can leave search engines with thousands of similar pages to choose between. The result is that the page you want rarely ranks, while crawl time is spent on pages that do not matter. Tidying duplication often lifts a multilingual site more than adding new content.
14Product variants across languages
A product sold in five colours and three sizes can become fifteen pages in each language if every variant has its own URL. Usually one page per product, with variants selected on the page, is better for shoppers and for search. Where variants genuinely need their own pages, such as a different material, give each its own descriptive text in every language rather than repeating the parent page.
15Regional versions: merge or differentiate
If your French pages for France and Belgium differ only in a flag, merge them into one French version with clear delivery and price information for each country, and redirect the regional URLs. If they differ in real ways, such as prices, payment methods or legal terms, make those differences visible on the page and mark the versions with regional hreflang. The middle ground, near-identical pages with nothing to choose between them, is the one to avoid. Structure options are compared in our guide to international site structure.
16When to call it done
Duplication work is finished for now when each language shows a sensible number of indexed pages, Search Console reports few pages where Google chose a different canonical, and test searches in each market return the right language version. Recheck after every redesign, platform change, plugin update or new market, since those are the moments duplication returns. The site-level service is on multilingual SEO.
17References
Official and research sources referred to above, linked to their home pages.
QQuestions
Will our French and German pages be treated as duplicates?
Not if they are properly translated. Google treats localised versions as duplicates only when the main content is left untranslated.
Should the French page carry a canonical to the English one?
No. Every version names itself as canonical, and hreflang does the job of tying the languages together.
Is it wrong to have French pages for France and Belgium?
Not at all, if they differ in useful ways such as prices or delivery. Link them with hreflang; if they are identical, one version may be enough.