Adding audio to a Ghost site, without breaking your theme
Ghost has become the go to platform for independent blogs and newsletters. Here are the three concrete ways to add an audio version of your articles, with their strengths and their limits.
Ghost has won over a lot of independent publishers, niche outlets and newsletter authors, because it does one thing very well: publishing clean, fast articles with a built in subscription model. If you are on Ghost and you want to offer an audio version of your articles, the good news is that there are several paths, from the simplest to the most integrated. The less good news is that none of them is a magic button in the admin: Ghost has no native "audio" field. So let us look at how to do it cleanly.
Understanding how Ghost builds a page
Before choosing a method, a useful reminder. A Ghost article is made of blocks (the content) and rendered by a theme (the template). You can inject content in three places: inside the article body through an HTML block, in the site header or footer through Code injection, or in the theme itself if you edit it. Each way of adding an audio player maps to one of these three entry points, with a different trade off between simplicity and automation.
Method 1: the HTML block, article by article
The most direct one. In the Ghost editor, you add an HTML block at the top of the article and paste in the player embed code. The audio appears exactly where you placed it. This is perfect for testing on a few articles, for a special feature, or if you publish rarely and want to keep control over each page.
The limit is obvious: it is manual. At a sustained publishing pace, pasting a block every time becomes a chore you end up forgetting. This method is ideal to start, not to last.
Method 2: Code injection, to automate display
Ghost lets you inject code into the header or footer of the whole site. You can use this to load a script that detects article pages and inserts the player in the right place automatically, without touching each post. You set it up once, and all your new articles get their audio version.
This is the right compromise for most Ghost sites: no theme changes, automatic display, and centralised control. You just need to make sure the script only runs on article pages and not on the home page or archives, a precaution we detail in our approach to static and generated sites, whose logic Ghost partly shares.
Method 3: go through the API and the feed, to drive everything
Ghost exposes a content API and a full RSS feed. This is the path for publishers who want to industrialise. Rather than injecting code on the display side, you let WeDispatch read your RSS feed: every newly published article is detected, its audio version is generated, and you get the result with no manual step. It is also the route to favour if you then want to expose your audio elsewhere, for example as a podcast.
For more advanced setups (triggering generation at the exact moment of deadline, handling several voices per section, feeding audio back into a homegrown app), the API and CMS integration give the fine control technical teams need. This method takes a bit of initial setup, but once in place it asks for nothing more.
Which method for which profile
If you publish a few articles a week and want to try safely, start with the HTML block on your best content. If you want it to run on its own without becoming a developer, Code injection is for you. If you manage real volume or a team, and you want to plug audio into a production pipeline, the API and RSS feed are the right level of commitment.
These three options are not mutually exclusive: many start with method 1 to convince themselves, then move to 2 or 3 once the habit is set.
The trap to avoid on Ghost
One point deserves your attention: Ghost themes and the "members" mode. If your articles are reserved for subscribers, make sure the player loads after the access check, so you do not expose the audio of paid content to a logged out visitor. Likewise, test the rendering on mobile, because Ghost themes are often very minimal and a badly placed player can break the layout. Nothing insurmountable, but two checks that avoid surprises.
Where to start
The most honest thing is to start small. Take your three most read articles, add an audio block by hand, and watch your listening stats over a week or two. If the signal is there, automate through Code injection or the feed. You will have validated real interest with your audience before investing a single minute in the technical integration.
Test audio on your Ghost site
The player turns on for free and works with all three methods above, with no theme change. Try it on your existing articles and see how your readers take it up.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo