Translate a website with AI: what to check first
In short. To translate a website with AI, let the machine produce the first draft and a person who knows your business review every page with a price, an offer or a legal term. Give each language its own address, link the versions with hreflang, and translate pages in order of how much they earn. Adding one language with us starts from 290 €, for an agreed list of pages and words.
Owners ask whether they can translate a website with AI and be done in an afternoon. The honest answer is that the machine is fast and the risk is in what you do not read. This guide explains where an AI draft is safe, where it is not, what Google actually says about language versions, and what a reasonable launch looks like for a small site. It does not quote a market price per word, because we have no first-hand figure and none is published by a source we could check.
How does AI translate a website?
It produces a draft quickly, and the draft needs a reader. A modern translation model handles ordinary sentences well. It handles badly the things a small business sells on: a condition that applies only in certain cases, a price with a unit, the exact name of a service, a legal term, a joke or a local phrase. These are also the places where an error costs money, because a visitor reads a promise you did not make.
The practical rule is to sort your pages by risk before you translate anything. A “who we are” page tolerates a light edit. A page with prices, delivery or cancellation terms does not. Treat the AI output as a first draft by a fast assistant who has never met your customers.
Which pages should be translated first?
Start with the pages where a foreigner decides to contact you or buy. Do not translate the whole site just because you can.
| Page type | Risk of a wrong translation | Review needed |
|---|---|---|
| Home page and main service pages | Medium, the offer is described | Read by a person who knows the business |
| Prices, delivery, cancellation, terms | High, a wrong word is a promise | Line-by-line check against the source |
| Contact form and its messages | High, a failed form loses an enquiry | Test the form in the new language |
| Blog and old news | Low, but many pages | Translate only what still earns |
| Legal pages | High | Specialist or your adviser, not a machine alone |
A small site often earns most of its enquiries from five or six pages. Translating those well is worth more than translating forty pages badly.
What does Google say about language versions?
Give every language its own address and link the versions to each other. In Google’s guidance on localized versions, each localized version should have its own URL, and the versions are declared with hreflang annotations, which can sit in the page, in an HTTP header or in the sitemap, and which Google treats as equivalent methods. Three details matter in practice. Each language version must list itself as well as the others. The links must be reciprocal, because if two pages do not point to each other the tags are ignored. And an x-default entry can serve visitors whose language is not on the list, for example from a language selector page.
The same page says something many owners do not expect. Google does not use hreflang or the HTML lang attribute to detect the language of a page, it works that out itself. And localized versions are only considered duplicates if the main content stays untranslated. So a properly translated page is not a duplicate of your original, and an untranslated page published under a new address is.
Is machine translation a risk for search?
It is a risk when it is done in bulk without care. Google’s spam policies describe scaled content abuse as generating many pages mainly to manipulate search rankings and not to help users, and they name using generative AI tools to generate many pages without adding value as one example. The section does not single out translation. We read it as a reminder rather than a ban: the policy is about volume without value.
For a small business this points to a sensible approach. Publish a limited number of language versions, translate the pages that help a reader decide, have a person check each one, and keep the original and the translation in step when you change a price. A site with fifteen reviewed pages in a new language is a different thing from a site with five hundred pages poured through a tool.
What does a worked word-count example look like?
Count words before you ask for a price, because the work scales with them. Here is an invented small site, to show the method and not a quote. It has a home page of 350 words, three service pages of 300 words each, a page about the team of 250 words, a contact page of 120 words and interface text for the menu and the form of 130 words. That is 350 + 900 + 250 + 120 + 130, which is 1,750 words.
Now sort it. The home page, the three service pages and the contact page (1,370 words) carry the offer and need a careful read. The team page and the interface text (380 words) are lower risk. If a person must read 1,370 words closely and skim 380, you know where the review time goes. The same count tells you what to leave out: an old news section of 40 pages is not worth translating unless it still brings visitors.
What should be set up technically?
Do the technical work once, properly, and the languages stay maintainable. The checklist is short:
- A separate address for each language, for example a folder such as
/de/or/fr/, as Google recommends separate URLs. - Hreflang tags on every page, each version listing itself and all the others, with an
x-defaultentry if you have a selector page. - A visible language switcher that leads to the equivalent page, not always to the home page.
- The menu, buttons, form labels and error messages translated, not only the body text.
- The form tested in the new language, with a message that arrives in a mailbox someone reads.
- Prices and currency formatted the way the local reader expects.
What does adding a language cost with us?
Our service for adding languages starts from 290 € per language. It covers one added language with an agreed page list and word limit and one revision round, with edited text, menus, agreed form messages, language addresses and the technical language setup. We check the result on mobile and desktop, check the links and approve terms and prices with you, and give you instructions for later updates.
Some things are outside it: specialist validation, certified translation, additional licences and later updates are separate, and we confirm platform limits before quoting. This is not a legal translation service. If a page is a contract, ask your adviser to approve the final text.
When is a new language not worth it yet?
When you cannot answer the enquiries that arrive. A German page that brings a German enquiry you cannot read, or a French page that promises a phone call in French you cannot take, is worse than no page. Add a language when someone on your side can reply in it, or when you are ready to say clearly which languages you can serve.
It is also not the first priority if the original site is weak. Fix the basics in what a website costs first, and think about reach and visibility with what SEO costs before multiplying pages. If you serve customers directly in several languages, an assistant that answers on your site can help, with the same review rules.
What should you check before the language goes live?
Run this list on every new language:
- Every price, unit and currency matches the source page.
- Delivery, cancellation and payment terms read the same in meaning as the original.
- The service names are consistent across the menu, titles and buttons.
- The form works and the message reaches you.
- Hreflang tags reference each other, and the language switcher points to the equivalent page.
- Someone reads the home page aloud and fixes anything that sounds odd.
- You know who updates the translation when the original changes.
How does Castel Studio handle translation?
We write the draft with a model, then edit it against the source, page by page, and we keep the same prices and terms in every language. We link the versions correctly, test the form and mobile layout and say plainly which pages we recommend leaving untranslated for now.
Tell us your site address, the language you want to add and which pages bring you customers. We reply in writing within 48 hours.
Questions
Can I translate my website with AI and publish it as it is?
Technically yes, but we do not recommend it. A machine translation can change a price, a condition or the name of a service without any visible error. A person who knows your business should read every page that carries an offer, a price or a legal term before it goes live.
Does Google penalise a machine-translated website?
Google's spam policies target pages generated in large numbers mainly to manipulate rankings and with little value for users, and they name generative AI tools as one example. A small number of carefully reviewed language versions written to help readers is a different situation, but the policy shows why unreviewed bulk output is a risk.
What is hreflang and do I need it?
Hreflang is a set of annotations that tells Google which page is the version of another page in a different language. Google says each language version must list itself and all the others, and that the links must be reciprocal, otherwise the tags are ignored.
How much does it cost to add a language to my website?
At Castel Studio one added language starts from 290 €, for an agreed page list and word limit, with one revision round. Certified translation, specialist validation and later updates are separate.