news_podcast for TYPO3

news_podcast turns a news system into a podcast host

Anyone who maintains news articles in TYPO3 and at the same time produces a podcast faces a decision: either use an external podcast host (Podigee, Podcaster, Anchor) and link into the website, or deliver the podcast feed directly from TYPO3. news_podcast makes option two possible: the extension extends GeorgRinger/news with fields and Fluid templates for audio files and generates an iTunes-compatible RSS feed that Apple Podcasts, Spotify and Google Podcasts import without detours. For organisations that want to retain control over content and audio files, this is the relevant architectural option. It avoids platform dependency, keeps the usage statistics in-house and also serves the content in the same CMS context where the news articles and the magazine already live.

Typical use cases are corporate podcasts and educational formats

Corporate podcasts are the most common scenario. A mid-sized industrial company produces a new episode every two weeks with guests from the industry and wants to embed the episodes in the corporate blog, submit them to Apple Podcasts and at the same time publish SEO-effective news articles with transcript and show notes. news_podcast covers these three needs in a single record, without the editorial team having to maintain three separate systems. A curated podcast record automatically produces the news article, the RSS feed entry and the Schema.org/PodcastEpisode markup.

A second scenario are universities and education providers. Lectures are recorded as audio files and stored on the campus server. Through news_podcast they appear as episodes of a lecture series, with chapters, transcript and reading lists. The feed is submitted to Apple Podcasts and Spotify, and access runs directly through the TYPO3 website, without students having to use an additional portal. Especially in periods with a high share of e-learning, this is a noticeable advantage over third-party platforms that bring additional accounts and tracking with them.

A third scenario are associations and political organisations that offer weekly interviews or press conferences as a podcast. Here it is above all about sovereignty: all data stays on the organisation’s own infrastructure, and the audience statistics come from the organisation’s server logs, not from a third-party dashboard. For organisations with high sensitivity towards tracking services, this is often the decisive factor against external podcast hosts.

Technical architecture extends the news model with podcast attributes

news_podcast registers a new field set via a TCA override for tx_news_domain_model_news. Per article, additional fields become available: audio file (FAL reference), duration, episode, season, type (full, trailer, bonus), explicit flag and transcript. Through another override, the news category is extended with a podcast channel field, with iTunes category, cover art, author, owner email and language.

The RSS feed is delivered through a dedicated TYPO3 controller. The route is configurable and produces an RSS 2.0 with iTunes namespace extensions. Every episode contains the mandatory tags for enclosure, duration, episode, episodeType and explicit. Validation runs against the Apple Podcasts feed validator and castfeedvalidator.com. Without a valid validation, Apple Podcasts refuses to accept the feed, and Spotify does not show the channel in search results.

The frontend output uses Fluid partials that can be overridden via a package overlay. The standard output embeds an HTML5 audio player and renders the show notes into the running text of the news detail template. For transcript output, a separate partial area is used that is made accessible via a tab system or an accordion. Anyone who wants to keep transcripts visible in the DOM for SEO reasons can override the partial and render the full text inline.

Common problems involve feed validation, enclosures and streaming

The most common support topic is iTunes feed validation. Apple Podcasts rejects feeds when the cover art does not meet the requirements (minimum 1400x1400px, maximum 3000x3000px, JPEG or PNG, sRGB) or when the tag is missing a MIME type. In practice, the first submission often fails on the cover art ratio, not on the actual extension.

The second topic is file sizes and streaming. Audio files in podcast quality (128 kbit MP3) come in at 30 to 60 MB per episode. Anyone who delivers these files directly from TYPO3 storage transfers the entire load to the web server, which becomes a bottleneck with thousands of listeners per episode. We recommend offloading the audio files to a separate storage (S3-compatible, CDN) and connecting it through FAL remote storage. This keeps the TYPO3 server responsible for content delivery while the audio load lands on the cheaper storage tier.

Thirdly, Google Podcasts requires a speaking, permanent URL per episode. The extension generates that automatically from the news slug, but the routing has to be enabled for the podcast controller in the site config, otherwise TYPO3 produces typolink URLs with a query string that Google Podcasts does not accept.

Migration to TYPO3 v12 requires a synchronous news core upgrade

news_podcast is available for TYPO3 v11, v12 and v13 but requires a compatible GeorgRinger/news version. On the jump to TYPO3 v12, both extensions have to be updated in sync: news to the v12 series and news_podcast to the matching major version. The database structure stays stable, audio FAL references move along without any special handling.

Gosign typically migrates news_podcast as part of a content hub refactor. In the same step we check whether transcripts can be extended with structured data, whether the cover art complies with current Apple guidelines and whether the feed controller is protected with a rate limit. For larger podcasts we extend the extension with a dedicated hosts model, so that guests can be managed with profile page and backlink. In combination with md_news_author, podcasters and guests can then be maintained as author profiles in parallel, which significantly improves the Schema.org markup and internal linking.