One audio per section: several players in a single WordPress post
A daily chronicle, a list of dates, a press roundup: nobody listens to one forty-minute file to find item six. How the WordPress plugin splits a post into sections, places a player under each one, and what the split really costs.
Most articles are read from top to bottom, and their audio version follows the same path. Some are not. A "this day in history" column made of one entry per date, a morning roundup in eight items, a weekly events list, a collection of fact sheets: readers skim these. They stop at the entry that matters to them and skip the rest.
A single audio file for the whole post works against that habit. Forty minutes in one block is a file nobody browses: to reach the third entry, the listener has to guess where it starts. Chapters help if people know they exist. What a listener actually wants is a play button next to each entry, in the same place a heading sits above it.
That is what the "One audio per notice" option of our WordPress plugin does, since version 1.31. ("Notice" is the word the plugin uses for one self-contained entry in a list-shaped post.) It was requested by a publisher who was doing the job by hand every morning: pasting each entry as text into the client area, then pasting a separate embed code under each block. Here is how it works, what it decides for you, and where it stops.
A checkbox, per post
This is not a site-wide setting. It is ticked in the WeDispatch panel of the post editor, one post at a time, because most of your content is still ordinary articles that belong in a single audio. If you have not installed the plugin yet, the WordPress page lists what it adds to your site; the rest of this article assumes it is in place.
Once the box is ticked, two things change. The post's single player is no longer placed at the top. And every section becomes a separate audio for the service: it carries the section's title, gets its own player directly under that section, and shows up under that title in My audios.
How a section is detected
You do not have to add any markup. The plugin reads the structure the post already has, using two methods in order.
Grouping blocks. In the block editor, a chronicle is usually built from Group, Cover, Columns or Media & Text blocks, one per entry, often each with its own background colour. If there are at least two of them at the top level of the post, each one becomes a section. Its title is its first heading, or failing that its first line.
Headings. Otherwise the plugin looks for the first heading level (h2, then h3, then h4) that appears at least twice. Each section runs from one heading to the next heading of the same level. That is how the classic editor and most themes structure content.
Three safeguards come with the rule:
- a section under one hundred characters is not read, so a lone caption or an empty heading never becomes an audio;
- if fewer than two sections remain, nothing is split, and the editor tells you so ("No notices found"), suggesting you untick the option to read the post as one audio;
- the split stops at sixty sections, because a post that long is a table of contents, not a chronicle, and a hundred players on one page help no one.
One consequence is worth knowing before you tick the box: text outside the sections is not read. An introduction before the first entry, or a closing paragraph after the last one that sits outside any block, is in no audio at all. That is deliberate: each audio matches exactly what sits above its play button.
Under the block, not inside it
Each section's player is placed after the block, not inside it. That sounds cosmetic and is not. A player dropped inside a dark-background block inherits its text colour and padding, and depending on the theme it ends up unreadable or misshapen. Placed right after, it keeps its own styling and still reads visually as belonging to the entry above.
Every player is also exposed to screen readers as its own region, labelled with the section title ("Audio version: 14 November 1918", for instance). Someone navigating by keyboard or by voice hears ten named players, not ten identical "audio player" landmarks they have to tell apart by guesswork.
When the post changes
This is the part that needed the most care, because a chronicle is a living document: a date gets corrected, a new entry is added at the top the next morning.
A section is identified by its title, not its position. Adding an entry at the top does not make the plugin re-read every other one: they are recognised by title and keep their audio. Two sections with the same title are told apart by their rank. Renaming a section, on the other hand, makes it a new section: the old audio stays in your client area, it is simply no longer shown on the page.
An unchanged section costs nothing. The service recognises the text and returns the existing audio.
An edited section is not regenerated automatically. The editor shows how many sections changed, states that nothing is spent before you choose, and offers two prices for each: re-read only the changed passages, or regenerate the whole section. It is the same mechanism as for a regular post, explained in fixing one sentence without regenerating everything. Some sections can only be regenerated in full (when you switch voice, for example), and the screen counts those separately.
If a batch is cut short (credits exhausted, network failure), any section that could not be sent keeps its previous audio on the page, and the gap is reported as a failure rather than quietly ignored.
What splitting costs
Splitting does not make audio cheaper, and it is better to say so plainly: it is slightly the opposite. Each audio rounds up to the next whole credit. Ten sections mean ten roundings where a single post would have one. With sections of a few hundred words each, the difference is small. With a long list of very short entries, it becomes noticeable, which is one more reason sections under a hundred characters are skipped.
On the other side of the ledger, text outside the sections is not counted, since it is not read.
Outside WordPress
The option is specific to the plugin. On another platform you can get the same result by hand: create one audio per entry in the client area, then paste each one's "Embed" code under its entry. The copied code now carries its own placement, so the player appears where you paste it. Codes copied before that fix all landed at the top of the page; copy them again from My audios.
Who it is for
List-shaped formats, and only those: anniversaries and "on this day" columns, dated chronicles, press roundups, event listings, collections of fact sheets. An argued piece that is meant to be read start to finish is better served by one audio, possibly with chapters. The question to ask is not "does my post have headings?" but "do my readers go through it in order?". If they do not read it in order, they will not listen to it in order either.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo