Adding an audio version to your Wix articles
Wix has no server-side plugin directory like WordPress, yet audio can still be added without a developer: an embed in your blog, an RSS feed, or the API, all three methods explained.
Wix built its name on a simple promise: put together a clean website without touching code, by dragging blocks around a visual editor. That ease has a well-known flip side for anyone who wants to go one step further. Wix stays a closed environment, where you add functions through approved apps or embed blocks, but not by freely installing a server-side plugin the way you would on WordPress. Adding an audio version of your articles looks, at first glance, like one of those blocked requests. The good news: on Wix, audio can be added without a developer, as long as you pick the right entry point. Here are the three methods, from the quickest to the most automated.
The player: an HTML block in your post or template
Wix Blog renders every post from a shared layout. That is where you act so the player shows up everywhere at once. The editor offers an Embed element (sometimes labelled "Embed a widget" or HTML iframe) that you place wherever you want it, just under the title for example.
The block holds a single line:
``
<script src="https://wedispatch.fr/player.js"
data-article="ARTICLE_ID" defer></script>
The player draws itself where the block sits and takes on the width of your column. Because Wix applies the same post structure to all your publications, you paste this code only once: every future article inherits the player with no extra step.
Linking the right audio to the right post
You still need to say which file matches which post. Two approaches, depending on how comfortable you are with the editor.
The first lets detection work from the page address. You give us the article URL, the text is pulled from the published page, the audio is matched. No field to create, no data to enter: it is the most direct option for a small team.
The second, more robust, relies on a stable identifier. You fill in the data-article attribute value for each post, which protects the pairing even if the URL changes during a future redesign. It takes a few more minutes, but it avoids surprises on a site meant to evolve.
Three ways to generate the audio
Showing the player is not enough: you have to produce the file. On Wix, three routes exist.
The RSS feed is the simplest. Wix Blog natively exposes a feed (its address usually ends in /blog-feed.xml). You send us that URL, new posts are spotted as they publish, the text is extracted and the audio generated with nothing for you to do. It is ideal for a team that wants to keep publishing as usual and find the player online automatically.
The sitemap approach works on the same principle if you would rather point to your site map than to the blog feed. Useful when some of your pages do not go through Wix Blog.
Finally, if you need control (trigger generation at a precise moment, choose the voice, handle corrections), the API stays open. A Wix site can call that API through an external automation tool (Make or Zapier, for instance) at publish time. It is more work up front, but it hands you the whole chain.
Read-along and accessibility
Whatever mode you pick, you can turn on read-along: the text scrolls and highlights word by word in time with the voice. On a personal blog as much as on a brand site, that detail matters for dyslexic or visually impaired readers, and it places your site within a real accessibility effort rather than a decorative one. The synced subtitles are set from your dashboard, without touching the Wix editor.
When an article changes
Editing then republishing a post is common on Wix. If you use the RSS feed, detection notices the update and flags the audio as "to regenerate": you relaunch generation once the text is settled, and successive corrections are never re-billed. If you use the API, you simply resend the same external identifier with the corrected text. In both cases the already published audio keeps being served until you relaunch, so no page is ever left without a player while you adjust.
Where to start
For a Wix site, the fastest route stays the RSS feed combined with the Embed block in your blog layout: about fifteen minutes to set up, no line of code to write, and every new article ships with its audio version. If you care about stable identifiers or precise timing, add the API. The details are in the documentation, and the plans by article volume on the pricing page. The most convincing test is to see the player run on your own pages: try it on one article and listen to the result before equipping the whole site.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo