AI translates the page. You decide the words.
Machine translation gives you a first version of every page. What to review first, what to leave untranslated, and how dashboard edits keep your words yours.
By FluentC2 min read
FluentC translates your pages with AI, so the first version of every page in every language comes from a machine. It's worth being plain about what that means: usually fine, sometimes not the word you'd have chosen, and once in a while wrong in a way that matters.
The point of FluentC isn't that the machine is always right. It's that the translation is yours: served from your address, the same for every visitor, and editable by you, line by line. A browser translation can't be reviewed by anyone at your organisation, because it's made fresh on each visitor's screen. Yours can.
What to read first
You won't read every page in every language, and you don't have to. Read these:
- Navigation and buttons. Menu items, "Add to cart", "Book now", "Contact us". Short, seen on every visit, and the easiest place for a machine to pick an odd word.
- Names. Your company, your products, your features. Decide which are translated and which stay as they are, then make it so.
- Lines with consequences. Prices and what they include, delivery terms, cancellation policies, anything with "must", "only" or "not" in it.
- The first screen of your most visited pages. Home, pricing, the top product or service page.
- Forms. Field labels, error messages, the confirmation. A form a visitor can't finish is a visitor you lose.
Everything else can wait until someone notices.
Fix it in the dashboard
Open the translation in the dashboard, find the line, change it. What you wrote is what's served from then on.
On WordPress, you edit from inside WordPress, and the plugin's glossary lets you fix a term once so it's used the same way across the site. See caching, translation memory and glossary in the plugin.
Leave some things alone
Some text must stay in its original language: contracts, notices that are valid in one jurisdiction, code samples, part numbers. Put the no-translate comment in front of it and FluentC leaves it as it is, while still translating the rest of the page and keeping the links in the right language.
<!-- no-translate-fluentc -->
The guide is skip translation for specific content.
If you're in a regulated field
Healthcare, legal, financial services, government: machine translation gives you a first version, and your own review stays in the process for anything a patient, a client, a customer or a resident will act on. Being able to see and edit every line is what makes that review possible. Reviewing it once, in the dashboard, is also what makes it stick: the next visitor gets the reviewed words, not a fresh machine translation.
Why not have a person translate everything?
You can, and for some pages you should. Have a translator read the pages that matter, in the dashboard, and fix them. The machine has already done the rest of the site, and the price doesn't change with how much you edit: it is flat per site, per language. See pricing.
Related: keeping translations current when your site changes every week.
