Translate Toolset with Transxlate
Views, forms and custom types. Here is exactly how it goes multilingual with Transxlate.
How does Transxlate translate Toolset?
Transxlate works on the rendered page rather than the database structures Toolset uses internally. When a visitor opens a language URL, every sentence Toolset outputs is looked up in your local translation table and — if new — translated once via your own Google or DeepL key. No field mapping, no compatibility add-ons.
What gets translated in Toolset
- Views output
- Archive templates
- Form labels
Setup with Toolset — 4 steps
- 1
Install Transxlate
Download the plugin from your transxlate.com account (free plan available) and activate it — the setup wizard opens automatically.
- 2
Add your target languages as a target language
Pick your default language and select your target languages in the wizard. The language URL is created instantly.
- 3
Connect your API key
Paste a Google Cloud Translation or DeepL key and switch on automatic translation. You pay the provider directly at wholesale rates.
- 4
Refine visually
Open any translated page with ?trx-edit=1 and click any sentence to perfect it. Human edits permanently override the machine.
Is Toolset content SEO-ready in other languages?
Yes: translated Toolset output is served as real HTML on real URLs (/fr/, /de/ …), indexable by search engines. With the Pro SEO pack, hreflang alternates link every language version so each one ranks for its own audience.
Frequently asked questions
Does Transxlate work with Toolset?
Yes. Transxlate translates the rendered front-end output, so everything Toolset prints to the page — views output, archive templates, form labels — is translated automatically, without per-plugin configuration.
Do I need a special add-on to translate Toolset?
No add-ons and no compatibility glue: because translation happens at the rendered-HTML level, any plugin or theme that outputs content is covered by the same engine.
Can I fine-tune how Toolset content reads in another language?
Yes — open any page with ?trx-edit=1 and click any Toolset string to override the machine translation permanently. Human edits always win over automatic output.
Will translating Toolset content slow my site down?
No. Each string is translated once, stored in your database, and served from cache afterwards. Language pages are fully compatible with page caching (WP Rocket, LiteSpeed, etc.).
Keep exploring
Make Toolset multilingual today
Works out of the box — no add-ons, no word quotas, your own API key.