Multilingual platform

The price isn't published yet, and that's on purpose: it depends on how much content you have and how many languages you want, and publishing an average figure would set the wrong expectations in both directions. It comes in writing in the proposal, after we look at the size of your platform. What we won't do is make up a number here just to look complete.

No. It's a standalone add-on, independent of your plan — a client on the entry-level plan can have a bilingual platform. Going multilingual is a business need, not a sign of company size, and it wouldn't make sense to tie it to a contract tier.

Both, in that order. The AI handles the volume and flags everything as a suggestion; a person reviews and approves. That's the setup that makes translating an entire platform feasible — and it's also why nothing goes live with the suggestion badge still showing on the main copy.

No. Batch filling only touches empty fields — text that someone has written or reviewed is preserved in every situation. That's a system rule, not a usage recommendation.

Technically, as many as you want. In practice, each additional language multiplies the review work for every piece of new content — and experience shows that two well-maintained languages are worth more than four half-maintained ones. The conversation here is usually about cutting back, not adding more.

It starts out untranslated and shows up in the hub as pending. This is the part that takes discipline: without ongoing review, the platform is bilingual at launch and slides back to monolingual within a few months, which makes a worse impression than never having translated at all.

No. The translated content stays stored; the platform simply goes back to showing only the source language, exactly as it did before. Turn the add-on back on and everything reappears, with no rework.