Your articles in audio, with no key to copy and no developer.
Install the plugin, click Connect, authorise it on our site. That is all. No API key to paste, no password handed to WordPress, no technical work.
After that, in automatic mode, your journalists publish as usual and the player appears at the top of the article. This is the path most of our customers take: they will never touch a line of API.
Free download, no account · WordPress 6.3 and above · PHP 7.4 and above · Gutenberg and classic editor
Three steps, about six minutes
Exactly what happens at each step, including what can go wrong.
01Install
2 minNothing unusual here: the plugin installs and activates like the others, and it adds a single menu entry.
- 01Plugins, then Add New, then search for WeDispatch. Install, Activate.
- 02A WeDispatch menu appears in the admin sidebar.
- 03No table is created in your database, and no file is written outside the plugin folder.
- 04No request leaves for us before you have connected an account.
If it does not workOn an older installation, check for PHP 7.4 as a minimum. If your host blocks outbound connections, the plugin detects it and shows the address to allow, rather than failing in silence.
02Connect
1 minThis is the step where you are usually sent off to fetch an API key. Not here.
- 01Click Connect. WordPress opens our site in a new tab.
- 02Create the free account, or sign in if you already have one. No card is asked for.
- 03You see your site's name and what the plugin will be allowed to do. You authorise it.
- 04Back in WordPress: the connection is established and the account name is shown. The key was exchanged server to server, and you never saw it.
What this avoidsA copied key always ends up lying around somewhere: an email, a chat thread, a notebook. Here there is nothing to mislay, and the key belongs to this site alone. You can revoke it from the dashboard without touching your other sites.
03Publish
3 minThe first audio is made from the overview, in one click. Then switch to automatic mode if you want every publication read aloud without you.
- 01Choose which content types are covered: posts, pages, products or custom types.
- 02Automatic mode: every publication triggers generation. Manual mode: one button per article, to keep control. A new site starts in manual mode.
- 03The first audio leaves the moment you click. It is ready in seconds for a news brief, in under a minute for a long read.
- 04The player appears at the top of the article, or wherever you placed the Gutenberg block.
The classic trapIf your theme displays content without going through WordPress, the player may not insert itself. The Gutenberg block or the shortcode then give you control over the exact position, and "Check the display" tells you what it found on the public page, page cache included.
Why you will never paste an API key
The usual method asks you to generate a key on one site, copy it, and paste it into WordPress. That key crosses a clipboard, sometimes an email, often an internal chat thread. It ends up living in clear text in a database several people administer.
We do it differently. WordPress opens our site, you authorise the connection with the account you have just created, and the plugin exchanges a single-use code for its own key, server to server. You never see the key, nobody copies it, and it belongs to this site alone.
One practical consequence matters more than it sounds: your site does not need to be reachable from outside. A staging site, an intranet or a password-protected site connects just as well as a public one.
What travels, and what does not
- NeverYour WordPress password. We do not see it and the plugin transmits it nowhere.
- NeverAn API key displayed, copied or pasted by a human being.
- NeverAn inbound connection to your site. Everything leaves from your end, so a staging site or an intranet works just as well.
- OnceA single-use code, valid for a few minutes, exchanged server to server for the site's key.
- ThenThe text of your articles, so it can be voiced, and nothing else. It trains no model.
You can revoke a site's connection from the dashboard at any time. The other sites are unaffected: each one has its own key.
Everything is configured inside WordPress, without changing tab
The plugin is not a thin bridge that sends you back to our site at the first setting. What the newsroom uses every day lives in the newsroom's own tool.
Overview
The state of the site seen from WordPress: connection, this month's usage, and what is left to set up. During the trial it offers to read one of your posts straight away, the one that fits what is left.
- Connection and this month's usage
- The first audio in one click during the trial
- Published items without audio, voiced in one click
My content & audio
Every item with the state of its audio, the voice that will read it, and its listens. An item that was refused says why on its line: no credits left, text too short, voice refused.
- Filters by content type and by audio state
- Bulk actions: generate the audio, remove the player
- "Check the display" looks at the public page
Voices
Which voice for which section, and which voice for which writer. A column read by a recognisable voice and a news brief by a neutral one, without touching anything article by article.
- One voice for the site, per section and per writer
- Pronunciations: a name corrected once, for every audio that follows
- Every voice can be heard before it is picked
Player
What the player looks like and what it offers, set from WordPress rather than from the dashboard.
- Layout, font and reading speed
- Highlighting, summary, download and sharing
- An option outside your plan is shown and explained, never offered and then refused
Statistics
Listens over thirty days against the thirty before, by byline, and your most listened items, named the way you name them.
- Trend over thirty days
- Listens by byline, unsigned items included
- The most listened items, with a link to edit each one
Settings
Connect or disconnect the site, choose between automatic and manual, which content types are read aloud, and where the player goes.
- Posts, pages, products or custom types
- Player at the top, at the bottom, or placed by hand
- Transcript and "Listen next" under the article, off by default
My subscription
The volume you subscribed to, how much of it is used, the longest item accepted, and where to change the volume. Subscribing and billing stay on wedispatch.fr.
- This month's volume and usage
- Longest item accepted
- A direct link to change the volume
Help & checks
The screen you open when something is wrong. It checks the key and subscriber-only listening from your server, without spending anything, and prepares a diagnostic to paste into a support request.
- Test of the key and of subscriber-only listening
- The cache plugins it knows, emptied after each audio
- A diagnostic ready to copy: versions, settings, scheduled task
What changes for the newsroom: nothing
It is the only goal worth having. Journalists write and publish in WordPress exactly as before. The plugin works behind them.
They publish as usual
In automatic mode, no new button to click, no box to tick. The audio version is made on publication, the way image thumbnails are.
They see the state of every audio
The My content & audio screen says where each item stands: audio up to date, text changed since, no audio, or refused with its reason. One glance is enough.
They fix a pronunciation
A name said wrong is corrected once, on the Voices screen, by writing how it is pronounced. Every audio that follows takes it into account.
They keep control when it matters
Manual mode, for the whole site or article by article from the editor panel, exists for sensitive subjects, obituaries and embargoed content.
They do not face failures alone
An item that was refused (text too short, no credits left) shows its cause in plain words on its line, inside WordPress, instead of a silent "no audio".
They do not wait for the audio
A scheduled article is voiced as soon as it is scheduled: it goes out at the planned time with its player, with no delay the listener can see.
Two other paths, exactly the same result
The choice depends on your setup, not on your budget: everything is included in the same subscription.
API
Plus an MCP server that exposes the main path to an assistant: produce, track, regenerate, measure. In synchronous mode the audio comes back in the response and the article publishes already voiced.
API documentationRSS feed
Give us the address of your feed or your sitemap. We discover new publications and generate the audio. Nothing to install, no access to your server. This is the path for proprietary CMSs and for sites nobody wants to touch.
Integration modesQuestions from WordPress administrators
Is the plugin free?
Yes, and there is nothing to pay to install it or to try it. It connects to a WeDispatch account, whose free trial includes 5 credits, one credit being 1,000 characters. Beyond that the service is paid for; the plugin never is.
Do I need an account to download it?
No. The file downloads freely from this page. An account is only needed when you connect the site, that is, when you want to produce your first audio.
Is this the latest version?
Always. The archive is rebuilt from the plugin's source code on every download: this page cannot distribute a stale version, because it stores no file.
Does the plugin slow my site down?
Generation happens on our side, not on your server. For the visitor, the player is a one-line asynchronous script that blocks neither the page nor its first render.
What happens if I deactivate the plugin?
Your audio stays online and keeps being served, because it is not hosted inside WordPress. Only the automatic insertion of the player stops. Reactivate and everything comes back.
Does it work on WordPress multisite?
Yes. Each site on the network connects separately and receives its own key, while sharing the volume and the billing at account level.
What about a staging site or an intranet?
It works, because the connection leaves from your site towards us and never the other way. We do not need to reach your server, nor even to know its public address.
Can I choose where the player appears?
Three ways: automatic insertion at the top or bottom of the article, a Gutenberg block placed wherever you like, or a shortcode for the classic editor and theme templates.
Is my content used to train a model?
No. The text serves only to produce the audio. Charter mode even lets you guarantee that no language model touched your text, only its voicing.
Does it work with my theme and my page builder?
Yes. The player is placed by a block, a shortcode, or automatically at the top of the article, and it picks up your page's colours. It imposes neither a font nor a layout.
Six minutes to hear your first article.
Create the free account, install the plugin, connect. You will have given no card details and you will already know whether the reading suits you.