Why your site still needs translating in the age of AI
Browsers and assistants translate anything a visitor asks. That helps the reader. It does nothing for you: not found, not chosen, not in control of the words.
By FluentC3 min read
Every browser has a translate button now. Every AI assistant answers in whatever language it's asked in. So the question comes up, from clients and from owners who'd rather not pay for one more subscription: if a visitor can translate my site in one click, why would I translate it myself?
It's a fair question. The short answer is that those two things happen on opposite sides of the web. Translation on the reader's side helps the reader who is already on your page. Translation on your side is what gets them there.
What a translate button does
When a visitor clicks translate, their browser takes the page it already has, sends the text off, and swaps the words on their screen. Nothing of it is published. The address in the bar is still yours, in your language. The page a search engine fetched is still in your language. Nobody at your company has seen the words that visitor read.
The same is true when someone pastes your page into an assistant, or asks it to summarise your pricing in Portuguese. The assistant does it for that one person, once.
That's useful. It is also private to that one visitor, which is exactly the problem.
Three things only a published translation gives you
An address
A translated page that lives at es.yoursite.com/precios/ is a thing in the world. It can be linked, shared, bookmarked, put in an ad, printed on a box and cited by an assistant. A browser translation has no address. It stops existing when the tab closes.
A place in the results
Search engines index what they fetch. If they fetch English, they index English, and a search typed in Spanish is matched, as a rule, against pages in Spanish. An assistant that looks things up on the web before answering finds pages the same way. Your English page can be read by either of them. It isn't what turns up for someone who never typed a word of English.
The words
A browser translates your product names, your terms and your buy button on the fly, differently for each visitor, and you never see the result. When the translation is yours, it's the same for everyone, you can read it, and you can change the one line that matters.
What AI changed, and what it didn't
AI changed the translation itself. Machine translation got good enough to start from, which is why FluentC uses it: translate the whole site, then fix the lines that matter, instead of starting every language from a blank page.
It didn't change where a page has to exist to be found. It didn't change that a search in one language is answered with pages in that language. And it didn't put anyone at your company in front of the words your visitors read.
FluentC sits on the publishing side of that line. It translates your pages with AI, then does the part a translate button can't: it serves each language from its own address, with hreflang set so search engines know which page is which, saves each translation so the next visit is fast, and lets you edit any line in the dashboard.
Where the translate button still wins
If a visitor from a language you don't serve lands on your site, the browser's translate button is exactly what they need. Don't fight it. Those are the languages where you don't expect to be found, only read.
For the languages where you want to be found, chosen and understood on your own terms, you need pages in those languages. Pick them, and publish them.
Next
- Can ChatGPT translate my website? covers what a chatbot does and what's left over.
- Browser translation vs a translated site lays the two out side by side.
- How AI assistants find your site in other languages is the search side.
- How Domains works is the setup: three steps in the dashboard, no plugin.
