Add an audio version to your Weebly posts
Weebly is a closed builder, but audio adds without a developer: an Embed Code element for the player, the RSS feed to make the audio on its own, the API to keep control. The three routes, and which one to pick.
Weebly won over a lot of people who wanted a tidy site without writing code: drag a block, publish, done. That comfort comes with a catch anyone discovers the moment they want to go one step further. Weebly is a closed environment. You add features through the elements the editor provides, not by freely installing a server-side extension the way you would on WordPress. Turning your posts into audio looks, at first, like one of those things the platform simply won't let you do. It isn't. On Weebly, audio adds without a developer, as long as you use the right door. Here are the three routes, from fastest to most automated.
The player: an Embed Code element in your layout
Weebly offers an "Embed Code" element that you drag into the page like any other block, then paste HTML into. That's where the player lives. To make it appear on every post at once rather than page by page, drop the block into the repeating area of your post template, just under the title for instance.
The code is two lines:
``
<div data-wedispatch="wda-ARTICLE_ID"></div>
<script src="https://wedispatch.fr/player.js"
data-article="ARTICLE_ID" data-slot="wda-ARTICLE_ID" defer></script>
The first element reserves the exact spot where the player will render; the second fetches the matching audio. That precision isn't cosmetic: on a post built from several parts, each can carry its own player without them colliding, and the player stays put even if Weebly or a cache plugin moves the script to the footer. The player then takes the width of your column, with no setting to touch.
Matching the right audio to the right post
What's left is telling us which file goes with which post. Two ways, depending on how comfortable you are.
The most direct lets recognition happen on the page address: you send us the article URL, the text is pulled from the published page, and the audio is matched. Nothing to fill in. The sturdier way relies on a stable identifier you carry in the data-article attribute: the match holds even if the address changes one day, during a redesign or a title edit. A few more minutes at setup, no surprises later. That choice between address and identifier is the same whatever the player, in page or in an isolated frame, as the piece on the in-page player versus an iframe explains.
Three ways to make the audio
Showing the player isn't enough; the file has to exist. On Weebly, three routes.
The RSS feed is the simplest. The Weebly blog exposes a feed natively; you hand us its address, new posts are spotted as they publish, their text is extracted and the audio generated with no action from you. This is the route for a small team that wants to keep publishing as usual and find the player online on its own.
The sitemap works on the same principle if you'd rather point at your sitemap, handy when some of your pages don't go through the blog.
Finally, if you need control (triggering generation at a precise moment, choosing the voice, handling corrections), the API stays open. A Weebly site can call it at publication time through an external automation. More work up front, but you hold the whole chain.
Read-along and accessibility
Whichever route you take, you can turn on read-along: the text scrolls and highlights word by word in step with the voice. On a personal site as on a brand site, that detail matters to dyslexic and low-vision readers, and it puts your site on a path of real accessibility rather than a decorative one. None of it requires touching the Weebly theme: the player, the subtitles and read-along are all set from your dashboard, outside the editor.
When an article changes
Fixing then republishing a post is routine. If you go through the RSS feed, the update is spotted and the audio flagged "to regenerate": you relaunch once the text has settled, and successive corrections are never billed twice. If you go through the API, you send the same identifier with the corrected text. Either way, the already-published audio keeps playing until you relaunch, so no page falls silent while you adjust.
Where to start
For a Weebly site, the fastest route is the RSS feed paired with an Embed Code block in the post template: about fifteen minutes to set up, no line of code to write, and every new post ships with its audio version. Add the API only if you want stable identifiers or precise triggering. The logic is the same as on other closed builders, laid out for Wix: the editor locks the server down, but it always lets a block of code in and a feed out, and those two doors are enough. The most convincing thing is to hear the result on your own pages before you fit out 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