Discussion starter: an international SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Indexing
- International SEO
Auto-translated UGC such as reviews and forum posts in other languages: indexable or noindex? What did you observe?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
Niraj Raut
My default is to show automatically translated reviews and posts to users, clearly labelled, but keep the translations out of the index unless they have been reviewed or are clearly useful as standalone pages. Google’s spam policies on scaled content abuse include content produced through automated transformations, translation among them, where little value is provided to users. Machine-translated user content indexed at scale can easily fall into that pattern: thin, duplicative pages in languages the community never wrote in. At the same time, translated reviews can genuinely help international shoppers and travellers. The balance is to use translation for the user experience, index original-language content, and index translated versions only where they are part of a well-built, reviewed localised page.
Options compared
Approach User benefit Search risk Show translations on demand, original indexed High Low Translated versions on separate URLs, noindexed High Low Translated versions indexed, clearly labelled, within localised pages with substantial local content High Moderate; depends on quality and value Machine-translated threads or reviews published as standalone indexed pages at scale Low to moderate High When indexing translations can make sense
- The translated content sits within a page that is otherwise genuinely localised, such as a product or hotel page in the local language with local prices and details.
- Translations are labelled as machine-translated, with access to the original.
- Quality has been checked, at least by sampling, for the language in question.
- There is demand in that language and not enough native content to serve it.
When to keep them out of the index
- Forum threads translated wholesale into many languages as separate pages.
- Translations whose quality has not been checked, especially for languages with complex grammar or specialist vocabulary.
- Pages that would duplicate the same thread across dozens of language versions with no other local content.
Implementation
- Label translated content clearly and offer a way to see the original.
- Where translations are on separate URLs and indexed, use hreflang between genuine language versions and self-referencing canonicals.
- Where translations are shown dynamically on the original page, keep the original language as the indexed text.
- Sample translation quality regularly, and remove languages where quality is poor.
Hypothetical example:
A hotel booking site shows reviews in their original language by default, with a “translate” button that displays a labelled machine translation. Its localised hotel pages in German and French include a selection of translated reviews alongside native-language reviews, local pricing and descriptions written for the market. A community forum it acquired, however, had published every thread in eight machine-translated versions as separate indexed pages. Most were never indexed or received no impressions. The site noindexes the forum translations, keeps original-language threads indexable, and adds a translate button for readers. Forum visibility in the original language improves as crawl and quality signals concentrate on the originals.
Watch for this:
Machine translations of user content can garble meaning in ways that mislead, for example turning a complaint into praise or changing a safety warning. For content where accuracy matters, show the original alongside and do not present the translation as authoritative.
Native-language content is worth encouraging
Translations fill gaps, but native-language contributions are more valuable for local users and for search. Platforms can encourage them by inviting reviews in the user’s own language, supporting local-language communities with local moderators, and surfacing native content first on localised pages, with translations as a supplement. As native content in a language grows, the case for indexing translated content in that language weakens, and translations can move to an on-demand option.
Measure before expanding
If you do index translated content, track indexing rates and impressions for translated pages by language, and compare engagement and conversion with native-language pages. Languages where translated pages are indexed and used can be kept; languages where they sit unindexed or attract no engagement are signals to stop. Let evidence from each language decide, rather than enabling every language by default.
Show machine translations to users with clear labels, index original-language content, index translations only within genuinely localised pages of checked quality, keep wholesale translated copies of threads and reviews out of the index, and expand language by language based on evidence.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.