In this guide · 7 sections
Short answer
Google doesn't penalise translation itself; its spam policy targets many auto-generated or auto-translated pages with little value. Give each language its own URL, link versions with hreflang, keep one language per page, avoid auto-redirects, and have a fluent speaker review key pages.
What Google says about translated and AI content
Google's spam policies define scaled content abuse as many pages generated mainly to manipulate rankings rather than help users, 'no matter how it's created'. One of its examples is scraping content and generating many pages through automated transformations 'like synonymizing, translating, or other obfuscation techniques' where little value is provided.
So the issue is not the translation tool. It is publishing a lot of thin, unreviewed pages. Google's guidance on generative AI content says to focus on accuracy, quality and relevance, warns that AI output may contain inaccuracies, and says it is critical to fact-check and review AI-generated content before publishing, including titles, meta descriptions, structured data and image alt text.
Likely fine
- Your own pages translated for real customers who read that language
- Translations reviewed for accuracy, with local terms and prices correct
- A reasonable number of pages that match your services
- Titles and descriptions written properly in each language
Likely a problem
- Hundreds of auto-translated pages published in one go, never read by anyone
- Translated copies of other sites' content
- Pages mixing two languages side by side
- Machine-translated legal, medical or pricing wording nobody checked
Our guide to Google's policy on AI content covers the wider rules.
Set up language versions the way Google expects
Google's multilingual sites guide gives clear rules. These are the ones that trip up small business sites most.
| Rule | What Google says | What it means for you |
|---|---|---|
| Separate URLs | Use different URLs for each language version rather than cookies or browser settings | example.sg/ and example.sg/zh/ (or /ms/), not a toggle that swaps text on one URL |
| One language per page | Google uses the visible content to detect language, not the lang attribute or URL | Menus, headings and body text all in the same language |
| No side-by-side translations | Avoid side-by-side translations; translating only boilerplate creates a bad experience | Don't put English and Chinese paragraphs on the same page |
| No auto-redirects | Don't redirect users based on what you think their language is | Show a language switcher link instead |
| hreflang | Use hreflang to help Google link to the right language version | Tag each page with its alternates |
If you're planning a Chinese version, our bilingual English and Chinese website guide covers fonts, layout and which pages to translate first.
hreflang in plain English
hreflang tags tell Google that two or more pages are the same content in different languages, so it can show the right one in search results. Google's localized versions page sets the rules.
Pick your language codes
Use ISO 639-1 language codes, optionally with a region: en, zh (or zh-Hans for Simplified Chinese), ms. Add a region like en-SG only if you have different versions per country.
List every version on every page
Google says each language version must list itself and all other versions. The English page lists en and zh; the Chinese page lists the same two.
Use full URLs
Alternate URLs must be fully qualified, including https://.
Add an x-default
Google recommends an x-default for visitors whose language doesn't match, usually your main English page or a language selector.
Check for missing return links
Google lists missing return links among the most common mistakes: if page X points to Y, Y must point back to X, or the annotations may be ignored.
Many multilingual plugins and website platforms add hreflang tags for you once languages are set up. Check the page source after publishing to confirm every version is listed.
A cost-effective workflow: AI draft, native check
You don't need a full professional translation of every page. You do need a fluent speaker to check the pages that sell.
| Page type | Approach | Why |
|---|---|---|
| Home, services, pricing, contact | AI draft, then full native review | These pages win or lose the customer |
| Legal: terms, privacy, refunds | Professional translation or keep English with a note | Wording errors have legal consequences |
| FAQs, blog posts | AI draft, native spot-check of key claims | Lower risk; review titles and descriptions |
| Product descriptions (many) | AI draft with a glossary, sample review | Consistency matters more than style |
| Old or low-traffic pages | Don't translate yet | Avoid thin pages nobody needs |
A short glossary (your brand name, service names, units, how you write prices and addresses) fed to the translation tool improves consistency. Our comparison of DeepL, Google Translate and ChatGPT for translation covers which tool suits which language.
What machine translation costs
Translation itself is cheap. Review time is the real cost.
- Google Cloud Translation (NMT): first 500,000 characters a monthApplied as a US$10 monthly creditFree
- Google Cloud Translation (NMT) beyond thatCharged on input characters per target languageUS$20 per million characters
- Translation LLM (Google Cloud)Google says this is cost-equivalent with NMTUS$10 per million input + US$10 per million output characters
- Native-speaker review of key pagesUsually the biggest costYour staff time or a freelancer's rate
Approximate, as of October 2026, from Google Cloud Translation pricing (USD). Website plugins and SaaS translation tools charge differently.
Google's Cloud Translation pricing means a typical 10 to 20 page small business site fits within the free monthly allowance for one language. Most owners use a website plugin or an AI chat tool instead, but the point holds: the translation is cents, the checking is hours.
Do it yourself or get help?
Translating a small site yourself is realistic if your platform supports separate language URLs and hreflang, and a fluent speaker can review the key pages. The common mistakes are a language toggle on a single URL, untranslated titles and descriptions, and auto-redirects by browser language.
Our Business Website (S$1,490) builds up to 6 pages with on-page SEO and a sitemap; a second language can be added when you supply or approve the translated copy. For an existing site, the Speed & SEO Fix (S$390) fixes titles, descriptions and headings, sets up the sitemap and Google Search Console, and cleans up broken links, which is where language-version errors usually show up.
Frequently asked questions
Not because they are translated. Google's spam policy on scaled content abuse targets many pages created mainly to manipulate rankings with little value, and gives auto-translating scraped content as an example. Translated versions of your own useful pages, reviewed for accuracy and set up with separate URLs and hreflang, are normal multilingual content.
Yes. Google recommends different URLs for each language version rather than using cookies or browser settings to change the language on one URL. Common patterns are subfolders like /zh/ and /ms/. Link the versions with hreflang and add a visible language switcher instead of automatically redirecting visitors.
hreflang is a tag that tells Google which pages are the same content in different languages, so the right version appears in search results. You need it if you have two or more language versions. Each page must list itself and all alternates with full URLs, and Google suggests an x-default for unmatched languages.
It's better not to. Google says it detects a page's language from its visible content and recommends one language for content and navigation on each page, avoiding side-by-side translations. Make separate English and Chinese pages linked with hreflang, and let visitors switch with a language link.
For a first draft, often yes, especially between English and Chinese or Malay. Google's guidance says AI output can contain errors and should be fact-checked before publishing, including titles and descriptions. Have a fluent speaker review the pages that sell, and use professional translation for legal pages such as terms and refund policies.