← Blog · 22 November 2026 · Lire en français

“Listen next”: offering a second article to your listeners without tracking them

The end of an audio article is when your most attentive visitor of the day leaves. How WeDispatch picks what to suggest next (same section first, then the most recent), where the list appears in WordPress or through the API, and what it deliberately does not do.

Most sites put real effort into the bottom of an article: related links, “you might also like”, recommendation widgets. All of it is designed for someone who has been reading. Very little is designed for someone who has been listening, and that person reaches the end in a different state. They have just given you five, eight, twelve minutes of attention. They may not be looking at the screen at all. When the audio stops, the player resets to its play button, and unless something useful is sitting right under the article, the next move is closing the tab.

A “Listen next” list is a small answer to that moment: a short set of links placed directly under the article, ready for when the listener picks their phone back up. Here is exactly how ours works, read from the code rather than from a brochure.

How the list is chosen

The rule has two steps, and it is meant to be predictable:

1. Articles from the same section first, newest to oldest.
2. If that is not enough, the most recent articles on the site, whatever their section.

Three filters apply before anything is listed. The article being read is never suggested. Only articles whose audio is ready can appear. And a private document listened to in WeDispatch Radio is never recommended to anyone.

That is the whole algorithm. No text analysis, no “people who listened to this also listened to”, no popularity ranking. The practical consequence is worth spelling out: the quality of the list depends on your sections. A site where everything is filed under “Uncategorized” will simply get its latest audio articles. A site with a clean structure gets suggestions that make sense. Our page on sections covers what else a section controls, from voice choice to listening statistics.

Why we chose not to follow the listener

A behavioural recommender would produce sharper lists. It would also need an identifier for each listener, a memory of what they played, and therefore prior consent, another paragraph in your privacy policy and another banner on your page. Our player sets no tracker and profiles no one; we go through the details in audio player, cookies and GDPR consent. A recommendation feature that broke that promise to win a few extra plays would have been a bad trade for the publishers who rely on it.

So the list depends on the article on screen, never on the person looking at it. Two visitors on the same page see the same suggestions.

On WordPress: one checkbox, off by default

If your site runs on WordPress, the block lives in the WeDispatch plugin settings, labelled “Show ‘Listen next’ under the article”. It is unchecked on install. Adding content under someone's articles without being asked is not an improvement, it is a surprise.

Once enabled, this is what the plugin does:

  • It shows at most four articles, linked to your own permalinks, never to a player hosted somewhere else.
  • It only lists content published on that site. A draft, a trashed post, or a post from another site sharing the same API key is never offered.
  • The section sent for each post is its first category, skipping the default one, because “Uncategorized” is the absence of a section, not a section.
  • The block sits after the content, and after the transcript if you enabled that too, wherever the player itself is placed.
  • It is marked up as a navigation landmark with a “Listen next” heading and a label for screen readers, and it brings no colours or fonts of its own: your theme styles it.

One detail matters for page speed: the plugin never calls our service while a page is being rendered. Each list is cached for six hours (five minutes if the service did not answer) and refilled by a background task. The visible side effect is minor but real: right after you tick the box, an article may appear without the block until its cache has been filled. That is not a fault. It is the cost of never making a reader wait for a suggestion.

Without WordPress: one API call

On a custom CMS or a static site, the same list comes from a single request, described in our documentation:

GET /api/v1/recommendations?article_id=…&limit=5

For each suggested article, the response gives its id, title, section, creation date and a ready-made player URL. The limit can go from one to twenty, with five by default. Our advice is to render the list with your own article URLs, looked up from the id, rather than the bare player URL. The listener stays on your site, and the next page comes with its text, images and links.

What it does not do

  • It does not autoplay the next article. When an article ends, the player stops. Starting another audio on someone who may have put their phone down is not a decision we take on your behalf. If you want continuous listening, there is a format built for it, which the listener starts knowingly: the daily playlist on your homepage.
  • It does not rank by audience. Your most played articles do not jump the queue.
  • It costs nothing in synthesis. Only audio that already exists can be suggested.

The question every team asks next is whether it helps. The honest way to find out is in your listening statistics: compare a few weeks before and after you enable the block, on the articles it suggests. Our piece on what to actually measure explains which numbers tell you something and which only flatter.

Give your articles a voice with WeDispatch

This blog is itself voiced by WeDispatch. Curious how it sounds on your content?

Book a demo

Read next