Audio in WordPress without touching your theme: how the mechanism works
How the audio player inserts itself into your articles without changing a single line of your theme, and why that avoids the classic problem: a theme update that wipes out your tweak.
Anyone who has ever added something to a WordPress site knows the trap: you paste a snippet into a theme file, it works, then a theme update lands and wipes the tweak out. Article audio is not exempt from that fear. The good news is that the WeDispatch plugin inserts itself without ever modifying your theme, and the mechanism is simple enough to be checked. Here it is.
The player lands at display time, not in the file
The principle fits in one sentence: the plugin does not rewrite your theme files, it hooks into the extension points WordPress provides for exactly this. When you choose to have the player appear before or after the article, it hooks into the standard filter that lets any plugin add something around the content at display time. Your theme does not even know the player exists: it is WordPress that, as it renders the page, inserts the player's slot before or after the text, according to your setting. Nothing is written into the theme file, so nothing is erased when the theme updates.
That filter applies only where it should: on a single article page, in the main loop, for the content types you have ticked. On a homepage, an archive or a search result, the player does not invite itself. It is a point fix, not a carpet rolled out everywhere.
An empty slot, not a hand-rolled tag
Where the player lands, the plugin does not insert a hand-written <script> tag into your content. It places an empty slot and puts the player script into WordPress's official queue. The difference is not cosmetic. Writing a <script> straight into the content would work, but it would short-circuit everything that hooks onto that queue: deferral to the footer, caching plugins, your host's performance settings. By going through the queue, the player is treated as a well-behaved script, deferred and placed in the footer, exactly like the rest.
The slot itself is a landmark announced to assistive tools: it carries a role and a label that make it a region screen readers flag and can jump straight to, instead of a silent block stuck at the top of the article. That is what lets us honestly claim an accessibility gain, a subject we cover more broadly in audio versus a screen reader.
Three ways to place it, none touches the theme
The before-or-after setting covers most cases. When you want the player somewhere else, at a precise point in a long article for instance, you have three doors, and none goes through a theme file.
The editor block: in the block editor you open the inserter, type "audio" and drop the player where you want it. Importantly, the block records nothing in the content: it places a marker, and the audio identifier is looked up at display, never frozen at save. A regenerated article gets a new identifier, and a block that had memorised the old one would point at audio that no longer exists. The [wedispatch] shortcode: it works in the classic editor, in a theme template or in a page builder, for those who prefer that route. The sidebar widget: for classic themes, still the majority for many publishers, which have neither a block nor a free slot inside the article, the widget gives the player where the theme knows how to place it, and it disappears entirely on a page that has no audio.
Why this detail decides your long-term peace of mind
A plugin that modifies the theme is a debt that comes back to you at every update. A plugin that hooks into WordPress's extension points survives updates, theme changes and the move to full-site editing without breaking anything, because it never depended on a particular file. That is exactly what you want from an addition you mean to forget once it is in place. For the full list of what the plugin writes (and does not write) into your install, see our dedicated piece: what the plugin installs and what it leaves alone. And to set it all up, the WordPress page brings together the paths and the plugin itself, downloadable without creating an account.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo