Multilingual sites
WPML & multilingual
WordPress, set up right.
Independent help with WPML, Polylang, TranslatePress and AI translation SaaS tools: audits, one-symptom fixes, performance, setup, AI translation and development. I spent 7.5 years on WPML at OnTheGoSystems, the company behind the plugin, over three of them leading one of its technical support teams. Today I am independent and not affiliated with OnTheGoSystems.
Products
Fixed prices. No assessment call first.
Many multilingual problems start in configuration, compatibility or content settings rather than in the plugin itself. Getting the settings right once saves the bugfix later.
WPML Site Audit
EUR 299
Fixed price. Existing site, checked and not changed.
I check the multilingual configuration, performance and database footprint, and known issues for your exact plugin, builder, WooCommerce and theme versions. I also flag outdated or unsupported PHP and plugin versions. Elementor sites get a dedicated pass.
Written report in three business days, sorted by risk, with a fixed quote for the fixes or for a migration. Credited against Setup, fixes or a migration booked within 30 days.
Best before the sale season, before adding a language, before a big update, or before moving between translation plugins.
Bugfix
EUR 490
Fixed price, no timesheet. One concrete symptom.
Translated pages 404, strings missing, wrong currency, empty fields in the second language, broken after an update.
I reproduce it on a staging copy, find the cause, fix it or name what is outside the plugin and quote that. Up to four hours, short write-up. Start within two business days.
Same-day start on business days if the site is down: +EUR 200.
Outcome: the symptom gone, and the reason it appeared.
Multilingual performance
EUR 890
Fixed price. An existing multilingual site that has become slow.
Slow saves in the editor, slow front end in one or more languages, sitemap or taxonomy pages timing out, String Translation tables grown to gigabytes, slow queries from language filtering. Large WooCommerce catalogues with many variations and several active languages are the usual case.
Measured before and after: admin save time, front-end response per language, sitemap fetch, the size of the WPML tables, and the slow queries behind them. I work at the WordPress and WPML layer, advise on host, PHP and cache configuration, and do not administer your server.
Outcome: numbers you can compare, and the reason it was slow.
Multilingual Setup
EUR 390
Fixed price. New or unconfigured site, with WPML, Polylang, TranslatePress or an AI translation SaaS.
Languages and URL format, translation mode per post type, taxonomy and custom field, string translation, sitemap, hreflang, switcher, editor and workflow. Builder compatibility tested (Elementor, Divi, blocks). A one-page settings document so the next person knows why each option is set.
WooCommerce: +EUR 200. Two sessions within five business days.
Outcome: a site that translates the way you expect, documented.
AI translation
From EUR 250
Add-on to a Setup, or EUR 390 on its own.
Engine chosen for your content and budget: WPML Advanced Translation Editor, Polylang add-ons, TranslatePress, an AI translation SaaS or a DeepL integration. Which strings are excluded, a glossary, the review workflow and a cost estimate per language before anything runs.
Outcome: machine translation that a human reviews in one place, at a cost you can predict.
Multilingual development
From EUR 250
EUR 250, one task. For example twenty strings made translatable, one snippet written and tested, one filter made language-aware, one ACF field group set up to translate correctly.
EUR 475, five hours used within 60 days. For code that has to know which language it is in: your own theme or plugin, ACF and SCF fields used as a page builder, a custom switcher, a third-party plugin never built for WPML.
Written notes on what changed and why, so your developer can maintain it without me.
Larger work is quoted after a free 30-minute call: a full theme, migrations between multilingual plugins such as Polylang to WPML, site key and translation memory recovery after a staging to production move, multi-domain setups and complete multilingual builds.
Outcome: code that handles the site’s active languages correctly.
Which plugin?
Choosing the multilingual approach.
If you have not chosen yet, a 60-minute consulting call can compare the options before you commit to one. If you have, I work with what you have.
WPML
The most complete and the most complex. Right for shops, custom fields and sites with many content types. Needs configuring properly, which is what the Setup is for.
Polylang
Lean and close to WordPress core. Right for content sites with a small team and no WooCommerce complexity. The Pro version and its add-ons close most gaps.
TranslatePress
Translate from the front end, page by page. Right for small sites and page-builder sites where editors are not technical.
AI translation SaaS
Hosted services that translate the site through a script or proxy. Fastest to start, paid per word and per month. Right when speed matters more than control, and when the site rarely changes.
Problems I can help with
Problems I regularly investigate.
An update appearing to trigger a problem does not mean the update is the cause. Existing compatibility problems, custom code, outdated components or changes elsewhere are just as likely. I investigate what changed, isolate the problem and find the safest way forward.
- Problems after WPML or plugin updates
- Broken or missing translations
- Translation workflow problems
- WooCommerce and multilingual issues
- Plugin and theme compatibility problems
- Language switcher and URL problems
- Performance problems on multilingual sites
- String Translation table too large
- Custom fields not translating, including ACF and SCF flexible content used as a page builder
- Difficult issues that have already gone through standard troubleshooting
Experience
More than 17,000 hours of hands-on experience.
Before becoming an independent consultant I spent 7.5 years on WPML at OnTheGoSystems, the company behind the plugin, including over three years leading one of its technical support teams. My work involved investigating complex customer problems and working across first, second and third tier support. When a case was stuck I stepped in to move it forward and made the call on what happened next. I also helped build that team: technical interviews, onboarding, training and mentoring new support engineers and developers.
Today I provide independent consulting and am not affiliated with or employed by WPML or OnTheGoSystems.
Start with the problem
You do not need to diagnose it first. Tell me what is broken, when it started, what changed beforehand and what you have already tried.
All prices net, excluding VAT. WPML, Polylang and TranslatePress are trademarks of their owners; this is an independent service.