--- title: "Does machine translation hurt SEO? What Google says" description: "Google's policies don't ban machine translation. They target pages made at scale with little value. What that means for your site, and where review fits." url: "https://www.langrelay.com/blog/does-machine-translation-hurt-seo" --- 1. [Home](https://www.langrelay.com/) 2. [Blog](https://www.langrelay.com/blog) 3. Does machine translation hurt SEO? What Google says ArticleMultilingual SEO # Does machine translation hurt SEO? What Google says Google's policies don't ban machine translation. They target pages made at scale with little value. What that means for your site, and where review fits. [Chris Jayden](https://www.langrelay.com/about) Founder Published 6 October 2026 Reading time 6 min read ![A family paddles a canoe across an autumn lake toward a boathouse whose doors carry green and orange leaf tiles.](https://www.langrelay.com/_emdash/api/media/file/01M4ET3XZ2ZMGMKCCGQ7PZDBDJ.webp) On this page 1. What Google's policies say, with dates 2. Two very different things called "machine translated" 3. A widget that translates in the browser 4. Translated pages on their own URLs 5. Where machine translation causes problems 6. Terms that change from page to page 7. Titles and descriptions left behind 8. Pages that are half translated 9. Translating everything because it is cheap 10. Tone and register that do not fit 11. Where does review fit? 12. Should machine translated pages be noindexed? 13. How LangRelay handles this Machine translation does not hurt SEO by itself. Google's spam policies are aimed at pages produced in bulk to manipulate rankings while giving readers little, and automated translation is one of the techniques they name for that. A translated page that reads well, answers the same question as the original and sits on its own URL is judged like any other page. What hurts is publishing the output without anyone checking it. Translating in a way search engines cannot see usually does no harm, but it gains you nothing in search either. ## What Google's policies say, with dates Three Google documents cover this, all read on 2026-10-06. The spam policies, last updated on 2026-08-28, define scaled content abuse as "when many pages are generated for the primary purpose of manipulating search rankings and not helping users". One of the listed examples is "Scraping feeds, search results, or other content to generate many pages (including through automated transformations like synonymizing, translating, or other obfuscation techniques), where little value is provided to users". Translation appears there as a way to disguise copied content. The test is the last clause: whether the pages give readers anything. The guidance on generative AI content, last updated on 2026-10-01, is written about generative AI in general and does not mention translation. We read it as applying to AI translation, since a model writes the translated text. It says: "It is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." It then extends that review to metadata, naming `` elements, meta descriptions, structured data and image alt text, because those can appear in search results. The 2023 post that set out Google's position on AI content says that using automation, AI included, to generate content mainly to manipulate rankings breaks its spam policies, and also that "not all use of automation, including AI generation, is spam". Read together, Google's test is whether the page is useful, however the translation was produced, and Google expects a person to have checked AI output before it went live. ## Two very different things called "machine translated" ### A widget that translates in the browser A translation widget or a browser-side script swaps the text after the page loads, usually based on a button or the visitor's browser language. The URL stays the same for every language. Google's documentation explains why this often stays invisible to search: Googlebot "usually originates from the USA" and "sends HTTP requests without setting Accept-Language in the request header". Google recommends "using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page". Google's page on locale-adaptive sites adds that Googlebot also crawls from IP addresses outside the USA, but it still sends no `Accept-Language` header, and it recommends separate locale URLs with hreflang. A crawler that never clicks the language button sees the original language only. So a widget seldom harms your rankings, and it seldom helps them either. Your German visitors can read the page, but Google has no German page to show German searchers. ### Translated pages on their own URLs A plugin or proxy that serves `/de/` pages in the HTML gives Google something to index. Where those pages live (a subdirectory, a subdomain or a country domain) is a separate choice, compared in [subdomain vs subdirectory for a multilingual website](https://www.langrelay.com/blog/subdomain-vs-subdirectory-multilingual-seo). Each translated page can rank in its language and is judged on its own quality, so a good translation can win traffic and a poor one can lose it. ## Where machine translation causes problems ### Terms that change from page to page A product called "Workspace" in English becomes three different German words across ten pages, or a brand name gets translated. Readers lose trust, and the pages no longer match what people search for. ### Titles and descriptions left behind The body is translated and the `<title>` and meta description are still English, or were translated without regard to the words people search with. Google's AI guidance names these fields specifically. ### Pages that are half translated Google warns that translating only the boilerplate of a page "while keeping the bulk of your content in a single language" can create a bad experience when the same content shows up many times in search with different boilerplate. Its documentation also asks for one language for content and navigation on each page, without side-by-side translations. ### Translating everything because it is cheap Translating thin pages into five languages gives you five times as many thin pages. Start with the pages that answer something people in that market search for. ### Tone and register that do not fit A German page that addresses business customers with the informal "du", or a Spanish page that switches between "tú" and "usted", reads as careless even when every word is correct. ## Where does review fit? A review step belongs between the translation and the published page. A reviewer who knows the language and the business checks: 1. Product names, brand terms and anything that must stay in the original language. 2. The title, meta description and image alt text, against the queries people in that market use. 3. Numbers, prices, dates and units. 4. Legal and safety text, word for word. 5. The register: formal or informal address, used the same way throughout. 6. Links, so they lead to pages in the same language. A glossary handles most of the first point, and a style decision on formality settles the fifth before the first page is translated. ## Should machine translated pages be noindexed? Google's spam policy says that if you host content that falls under scaled content abuse, you should "exclude it from Search". That is about content that gives readers little, whatever made it. If you have published raw machine translation that you would not stand behind, adding `noindex` to those pages until someone has reviewed them is a reasonable precaution. Leave a page you noindex out of your hreflang set as well, because the set should only list versions that can appear in results. The [hreflang guide](https://www.langrelay.com/guides/hreflang) covers the rest of the set's rules, and [hreflang and canonical tags](https://www.langrelay.com/blog/hreflang-and-canonical-tags) covers how each version's canonical fits with it. ## How LangRelay handles this LangRelay's AI translation follows the formality register you choose for each language where the distinction exists, and on paid plans your glossary, including terms to keep in the original language. By default a translation then goes live as soon as it is ready, and free checks hold a page with untranslated text, the wrong language or a changed price. To approve every page yourself, choose Ask me first. The WordPress plugin serves only approved, live translations, in the page's HTML, under a subdirectory such as `/de/`. Until a page's translation in a language is live, the plugin leaves that language out of the page's hreflang set, so search engines are never pointed at an untranslated page. If the language is already live on other pages, the page's URL under that prefix shows the original content in the meantime. Titles and meta descriptions are translated with the rest of the page and go live with it. Relay, LangRelay's agent, drafts changes you ask for in plain language. Relay reviews any page you ask it to, the way a language expert would, and tells you the cost in AI credits before it starts. The [translation quality](https://www.langrelay.com/translation-quality) page covers the glossary and review tools, and [multilingual SEO](https://www.langrelay.com/multilingual-seo) covers what the plugin outputs for search. For non-WordPress sites, the script embed translates in the browser and makes no SEO claim, for the reasons in the widget section above. If you are weighing machine translation for a site that already ranks in one language, [book a demo](https://www.langrelay.com/book-a-demo) and bring a page that matters. ## Sources The pages this one cites, with the day each was read. 1. 01[Spam policies for Google web search (Google Search Central, last updated 2026-08-28)](https://developers.google.com/search/docs/essentials/spam-policies)developers.google.com, checked 6 October 2026 2. 02[Google Search's guidance on using generative AI content on your website (Google Search Central, last updated 2026-10-01)](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content)developers.google.com, checked 6 October 2026 3. 03[Google Search's guidance about AI-generated content (Google Search Central Blog, 2023-02-08)](https://developers.google.com/search/blog/2023/02/google-search-and-ai-content)developers.google.com, checked 6 October 2026 4. 04[Managing multi-regional and multilingual sites (Google Search Central, last updated 2025-12-10)](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)developers.google.com, checked 6 October 2026 5. 05[How Google crawls locale-adaptive pages (Google Search Central, last updated 2025-12-10)](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages)developers.google.com, checked 6 October 2026 [Chris Jayden](https://www.langrelay.com/about) Founder, LangRelay Chris Jayden is the founder of LangRelay. Chris has worked on websites of every size, from large e-commerce stores to small sites with a handful of pages, and started LangRelay after years of translating them the hard way. On this page 1. What Google's policies say, with dates 2. Two very different things called "machine translated" 3. A widget that translates in the browser 4. Translated pages on their own URLs 5. Where machine translation causes problems 6. Terms that change from page to page 7. Titles and descriptions left behind 8. Pages that are half translated 9. Translating everything because it is cheap 10. Tone and register that do not fit 11. Where does review fit? 12. Should machine translated pages be noindexed? 13. How LangRelay handles this Share - [Share on LinkedIn (opens in a new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.langrelay.com%2Fblog%2Fdoes-machine-translation-hurt-seo) - [Share on X (opens in a new tab)](https://x.com/intent/post?url=https%3A%2F%2Fwww.langrelay.com%2Fblog%2Fdoes-machine-translation-hurt-seo&text=Does%20machine%20translation%20hurt%20SEO%3F%20What%20Google%20says) See it on your site A 30-minute walkthrough on one of your pages. [Book a demo](https://www.langrelay.com/book-a-demo) - AI translation - machine translation - multilingual SEO - translation review ## Keep reading - Feature ### [Website Translation Quality: Glossary, Voice and AI Review](https://www.langrelay.com/translation-quality) Set a glossary and brand voice per language. Free checks hold a page with untranslated text, the wrong language or a changed price. Relay reviews on request. Book a demo ## See LangRelay on your own site Book 30 minutes with the team. We translate one of your pages live and walk through review, publishing and multilingual SEO. [Book a demo](https://www.langrelay.com/book-a-demo)[See pricing](https://www.langrelay.com/pricing)