Frequently asked questions
Everything they usually ask us before buying
Grouped by topics. If your question isn't here, write to us: we answer truthfully, and by email.
Before buying
No. You install the plugin, choose the languages, and translate by clicking on your own website. There are no .po/.mo files or technical configuration.
No. It's a one-time payment: the license does not expire and updates are included for life. The only limitation is how many sites you activate it on.
You have a 14-day money-back guarantee, no questions asked. Write to us from the contact page and we will refund the full amount.
Yes. The free version translates into one language with the basic engine, enough to see how the visual editor works on your own website. Activating the license unlocks the rest of the languages and engines, without losing any of the translated content.
Depends on the plan: 1, 5, or 20 sites. Local, testing, and staging environments do not consume activation, so you can work calmly before publishing.
Translation and languages
No, and it's deliberate: you use your own Gemini, DeepL, Google Translate, or Yandex keys. This way, the translation cost is direct with the provider, without intermediaries or margins on our part. Gemini and DeepL have generous free tiers.
As many as you want in the paid plans. Each language adds its URL prefix and sitemap.
Current engines provide a publishable result for most commercial texts. Even so, each AI-translated string is marked as pending review so you can check important things: headlines, prices, legal texts.
Yes, with the glossary: brand names, product names, or technical terms you add there always remain the same.
The string is marked as pending again and you can retranslate it from the panel or from the page itself.
SEO and performance
Yes. Each language is published on its own URL with a prefix (/en/, /fr/), with reciprocal hreflang tags, correct canonical, and a sitemap per language ready for Search Console.
Translations are saved in your database and served as normal HTML. There are no calls to any API when someone visits the page, nor JavaScript added for being in another language.
Yes, with the usual ones. Each language is cached by its URL, which is how these plugins expect to work.
Yes, SEO metadata enters the same flow as the rest of the strings.
Compatibility
Yes. String detection works on the page output, so it doesn't depend on the theme being ready for translation.
It has specific support: we read the internal JSON of each design to not miss any string, including those from Elementor Pro widgets.
Yes: product pages, categories, attributes, cart and checkout texts, and order emails.
Yes. Each site in the network consumes one activation of your license.
License and support
Upon purchase, you receive a key by email. You paste it into Settings → WP-Translate → License and the plugin is activated on that site.
Yes. You deactivate the license on the old site from the panel itself and activate it on the new one. The activation becomes free instantly.
Email support for plugin operation, engine configuration, and any failures. Plans with more sites have priority in the queue.
The translations are yours: you can export them before uninstalling. Upon uninstalling, the plugin cleans its own tables without leaving a trace.
Still have doubts?
Tell us your case and we'll frankly tell you if WP-Translate fits you or not.