3 BBC Sounds metadata rules for UK podcast SEO

What to take away

Why BBC Sounds metadata matters for public-service podcast SEO

BBC Sounds is the main listening home for UK public-service audio. Its catalog runs from Radio 4's File on 4 and In Our Time to 5 Live's daily news output and BBC Introducing music sessions. Each show competes for discovery with commercial networks such as Global and Bauer.

Metadata is how a public-service show competes. Title, synopsis, series name and availability travel from BBC production systems into BBC Sounds, then out to third-party apps through the RSS feed. Thin fields leave a show invisible in search and in app directories.

UK listeners search in their own words. They type "NHS waiting lists explained" or "Scottish football weekend review", not the working title used in a commissioning meeting. Metadata that ignores this loses the click before the audio plays.

Ofcom sets content standards for UK broadcasters under the BBC's operating license, and the BBC's public purposes require its online audio to be findable and accessible. Metadata supports those obligations. It is not a marketing extra.

Start with the podcast SEO foundations explained before touching individual episodes. Crawlable pages, clean titles and durable URLs apply to public-service audio just as they do to independent shows.

Radiocentre and AudioUK track how UK audio is discovered, and weak metadata skews that picture. When a BBC show cannot be found, the public-service category looks smaller than it is.

Rule one: brand and episode titles written for UK search

BBC Sounds names content in two layers: the brand, which is the series, and the episode. Both feed search, and both come from the same records that generate the RSS feed.

A title such as "Episode 14: The Inquiry continues" tells a listener nothing and gives a search engine nothing to rank. "NHS waiting lists in England: what the latest figures show" carries the topic, the nation and a reason to click.

Descriptions should front-load the key phrase. Put the subject in the first sentence, because apps truncate descriptions in list views and phone snippets cut around 120 characters. Google's desktop snippet runs nearer 155.

Series names need the same treatment. "The BBC Sounds Documentary" is a brand, not a search term. "The Documentary: Inside UK Food Banks" gives a World Service strand a subject anchor that carries across every episode page.

Use the spellings and terms UK listeners type. "Organise", "programme" and "council" match British search habits. Mixing in US spellings splits the search footprint across two vocabularies and weakens both.

Apple's Podcast RSS feed requirements explain which title and description fields apps read. Episode title, description, series name and artwork all come from the feed, so anything missing there is missing from Apple Podcasts, Spotify and Pocket Casts too.

Google's crawlers read the page text around the BBC Sounds player. The Google crawler overview sets out how they fetch and render episode pages. A title stuffed with comma-separated tags looks poor in the snippet that follows.

A worked example: coastal erosion on Radio 4

Suppose a Radio 4 strand commissions an episode about coastal erosion in Norfolk. A weak title reads "Coast, episode 7". A strong title reads "Coastal erosion in Norfolk: how fast is the sea advancing?".

The strong synopsis opens: "Norfolk councils are spending millions on sea defenses. This episode looks at erosion rates and what residents face." It names the place, the topic and the question, matching searches for "Norfolk coastal erosion" and "sea level rise Norfolk".

The same title gives the brand page a clear internal link anchor when other episodes cover the same coastline.

Steps for writing searchable episode metadata

Rule two: brand pages, play pages and a feed that agree

BBC Sounds builds two page types from one record set: a brand page at bbc.co.uk/sounds/brand for the series, and a play page at bbc.co.uk/sounds/play for each episode. Each carries a BBC programme identifier (PID) that stays fixed for the life of the content.

The podcast feed for a series typically sits at podcasts.files.bbci.co.uk/.rss, named after that same identifier. Search engines index pages, not audio files, so the page around the player does the ranking work.

Brand pages act as hubs. A brand page that lists every episode, with links to each one, gives crawlers a clear path through the archive. Episodes reachable only from a search box are indexed slowly or not at all.

RSS metadata must match the on-site page. If the feed says 45 minutes and the page says 30, apps and search engines disagree. Keep duration, release date, series name and episode number identical in both places.

Apple's guidance on managing your podcast covers how to update metadata after publication. Corrections are normal, but each change should be made in the source feed so every destination updates together.

Use robots.txt deliberately. BBC audio archives often sit behind rules that block crawling by accident. The robots.txt specification explains how Google reads allow and disallow lines, which matters when a rights window closes and you want a page deindexed.

Structured data helps. PodcastSeries and PodcastEpisode markup tells search engines what the page contains. It does not replace good titles, but it can earn richer results for a query about a specific guest or subject.

Accessibility is part of structure. The W3C media accessibility requirements set out how captions, transcripts and audio description should be exposed. A transcript adds indexable text and serves deaf and hard-of-hearing listeners.

Checklist for crawlable BBC Sounds episode pages

Align this work with your wider podcast SEO channel strategy. Search, apps and BBC Sounds each send listeners, and the metadata has to serve all three.

Rule three: rights and availability windows that shape indexing

A drama with a five-year music license cannot sit on a permanent page unless the rights are cleared again. Rights decide what can stay online, and that decides what can stay indexed. Record the window in the metadata from the start.

BBC Sounds shows that window on the page. Most radio episodes carry a 30-day catch-up period after broadcast. Podcasts cleared for longer display "available for over a year". A music documentary or a live sports commentary can be shorter than either.

The availability field in the feed is the technical expression of the window, telling apps when an episode expires. If the page stays live after expiry with no audio, the listing becomes a dead end and search engines may keep ranking it.

Plan for two states: available and archived. An archived page can keep a transcript, a summary and a clear note that the audio is gone. That preserves search value and avoids a broken player.

Rights also affect geography. Some BBC audio is UK-only, including sports commentary and licensed music, and the page should say so. Blocking or allowing crawlers by region is a technical decision, and robots.txt is one lever.

Music rights for UK audio run through PRS for Music and PPL, which license the composition and the recording. The Intellectual Property Office publishes the copyright framework behind both.

Record rights holders, license terms and expiry dates alongside the episode metadata. When a rights query arrives, the answer should be one field lookup away.

Availability changes should be scheduled, not reactive. A monthly audit of upcoming expiries lets you update pages, refresh transcripts and decide whether to seek renewal. Sudden removals create broken links and lost rankings.

Worked example: a BBC Introducing music documentary

A BBC Introducing documentary uses commercial tracks licensed for two years. The metadata records the expiry date, the territories and the rights holder. At month 22, the team reviews the page.

If the license is renewed, nothing changes. If not, the audio comes down, the page keeps the transcript and a note, and the sitemap is updated. Search engines see a consistent page, and listeners see an honest one.

Applying the three rules to BBC Sounds podcast SEO workflows

Write metadata at commissioning, not at publication, so titles and descriptions have time to be tested against real search terms.

Build a metadata template for every commission. It should include the search phrase, brand name, episode number, rights window and transcript owner. One page per episode keeps the handover clean.

Use a pre-publication check. The podcast SEO quality checklist approach of dated evidence works here: record who checked the title, the description, the structured data and the rights field, and when.

Measure what the metadata achieves. Track impressions and clicks from search, plus plays on BBC Sounds and third-party apps. The podcast SEO measurement guide sets out how to plan that before you report another download figure.

Feed the results back into titles. If a subject performs well, reuse the phrasing pattern in later episodes. If a title underperforms, rewrite it and note the change in the episode log.

Tooling can carry part of the load. The podcast SEO tool implementation plan covers how to connect feeds, page templates and reporting without duplicating work across teams.

Steps to embed the rules in a production workflow

What the three rules mean for commercial UK shows

A BBC show can rely on the Sounds app for a baseline audience. A commercial show depends on search and app discovery from day one, with less margin for error.

Title and description discipline transfers directly. Networks such as Global and Bauer run large archives, and consistent series structure keeps those archives crawlable. Rights windows matter more when music and talent contracts are shorter.

The regulatory layer differs. The ASA and CMA police advertising claims, and the ICO governs listener data. Metadata that promises something the audio does not deliver can attract attention from more than search engines.

The British Podcast Awards and the Radio Academy's ARIAS awards show how visible metadata has become. Judges and listeners both find shows through search, so a weak title is a competitive disadvantage.

Public-service metadata rules are not a BBC-only concern. They are a working standard for any UK show that wants to be found, played and measured.

Common questions