WeDispatch 1.6.0: one language, and a plugin that meets the bar
The site and your account now share a single language, the player speaks the language of the article, and the WordPress plugin reaches the level the official directory requires.
This version gathers several weeks of work along one thread: making language a decision you take once, and making the WordPress plugin publishable where publishers actually go looking for it.
One language, from the site to your account
Until now the public site and your account each remembered your language separately. Two memories is an opportunity to disagree: you could read the site in English and find French waiting for you once signed in.
They are now the same. The language of the page you are reading aligns your account, the sign-in screen opens in the right language, and links back to the site point to its localised version. The choice is made once and it holds, in both directions, and across every supported language, not just the English–French pair.
One engineering detail that matters for page speed: the preference is only rewritten when it genuinely changes, so pages are not pulled out of the delivery cache on every visit.
The player speaks the language of the article
The embedded player showed its controls (play, summary, accessibility) in the language of the site. That is sensible for a single-language site, less so for a newsroom publishing in several: an English article came wrapped in French controls.
The controls now follow the language of the text being read. Articles already narrated are relabelled on the next pass: it is a field update, no synthesis is re-run and no cost is incurred.
The WordPress plugin reaches directory level
The plugin moves up two versions at once, and the second has a precise target: passing the official WordPress directory review.
1.8.0 answers what multilingual newsrooms, and newsrooms that work ahead, actually asked for. The reading language is derived from the article itself (Polylang, WPML, or the site locale as a fallback) and the voice list puts the voices that can read that language first. A scheduled post is prepared when it is scheduled rather than when it goes live, so the audio is ready the moment the article appears. A fingerprint of the submitted text guarantees the same content is never sent twice. And automatic retry after a failure is available, off by default, with its cost written on screen, we would rather a spend be chosen than discovered.
1.9.0 is the compliance work. Plugin Check, the tool directory reviewers run, comes back with zero errors, verified on a real WordPress installation. The player uses the official script queue, which finally makes it legible to caching plugins, a point that matters on a high-traffic site. Every setting is filtered before it is stored, the per-author and per-category voice forms carry their security token, and the documentation is in English, as the directory has required since July 2025.
The download archive is now built by walking the plugin folder rather than listing filenames. A file added to the plugin ships in the archive without anyone having to remember, and an automated check verifies it on every change.
The MCP server keeps pace
The MCP server moves to 1.1.0 and catches up with the features added over recent weeks: translated editions, batch narration, subscription profile, and a voice catalogue that now declares which languages each voice can read, precisely what an agent needs in order to choose without guessing. An automated check locks that catalogue to the service's own.
What you do not see
Two pieces of infrastructure ship alongside this version.
Every change now passes a series of automated checks before it can reach production: the test suite, the WordPress plugin verification, and a full build. Those checks are deliberately offline, they call no external service and consume no quota. A check that depends on a third party eventually fails for reasons unrelated to the change under review, and at that point people stop reading it. A second check, this one daily, queries the live production site to confirm it answers correctly.
We have also put technical supervision in place, with its data ingested in Germany. Incidents are tagged by environment and by deployment version, faced with an anomaly, the first useful question is always "since which release?". Consistent with the rest of our commitments: no personal data is sent to it, and no session replay is recorded.
What it changes for you
If you use the WordPress plugin, update it: preparing scheduled posts ahead of time and choosing voices by language are immediately useful. If you browse in more than one language, you should no longer have to pick yours twice. And if you work through the MCP server, the voice catalogue will now answer you on languages.
Nothing else is required: your settings, your voices and your integrations are unchanged.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo