Podcast Schema Markup: What to Add and Why

QuickReel Team avatar
QuickReel Team22nd November, 2026
Podcast Schema Markup: What to Add and Why

Add PodcastSeries JSON-LD to your show page and PodcastEpisode JSON-LD to every episode page, with the episode linking back to the series. This won't trigger a special podcast box in Google, that result doesn't exist anymore, but it makes your pages legible to crawlers and AI answer engines, which is the real payoff. The copy-paste code is below.

The honest framing first, because it saves you hours. There is no "podcast rich result" in Google's structured data gallery. Adding PodcastEpisode markup will not put a play button or an episode carousel in search. What schema does is cheaper and more durable than a rich result: it removes ambiguity. It tells a machine exactly what your page is, a podcast episode, its title, its host, its audio file, the show it belongs to, so that web search, AI Overviews, and other answer engines can use the page with confidence. That clarity is worth doing well, and it takes about ten minutes per template.

Does podcast schema markup get you a rich result in Google?

No. Google's structured data search gallery, the official list of every search feature markup can trigger, does not include a podcast or PodcastEpisode entry. There has never been a dedicated PodcastEpisode rich result, and the old playable podcast features Google did have were retired in 2023–2024. So no schema field will produce a podcast-specific SERP element.

That matters because most "podcast schema" advice still promises a play button or an episode list in search. It is selling something Google doesn't ship. What you can actually earn from search features sits in two other schema types, covered further down: VideoObject (for video episodes) and Article (for the episode's written page). The Podcast* types are still worth adding, they are how you describe the entity cleanly, but go in with the right expectation.

How PodcastSeries and PodcastEpisode connect The show page carries PodcastSeries markup; each episode page carries PodcastEpisode markup that links back to the series with partOfSeries. One series, many episodes, linked both ways Show page PodcastSeries name · url · image · webFeed Episode page #1 PodcastEpisode Episode page #2 PodcastEpisode Episode page #3 PodcastEpisode each episode uses partOfSeries to point back Structure based on Schema.org PodcastSeries / PodcastEpisode. Source: schema.org.
The show page carries the series markup; each episode links back with partOfSeries. Source: schema.org/PodcastEpisode.
Illustration depicting Podcast Schema Markup: What to Add and Why

Why bother adding schema if there's no rich result?

Because search results are not the only machine reading your page anymore. Structured data is how a crawler resolves what your page is without guessing from the HTML, and that resolution feeds web indexing, knowledge-graph entity matching, and the AI answer layer. Clean markup is a small, durable investment in being understood.

The discovery shift makes this concrete. Social video clips now drive podcast discovery more than friends and family do, InsideRadio reported that social media passed personal recommendation as the top way listeners find new shows (InsideRadio, 2025). As discovery fragments across feeds and AI summaries, the pages a machine can parse cleanly are the ones that get cited and surfaced. Schema is the cheapest way to be one of them. Pair it with show notes that rank on Google and episode titles built for discovery, and the page works for both humans and crawlers.

The copy-paste PodcastSeries JSON-LD

Put this once on your show's home page. Fill the values, drop it inside a ````

The load-bearing fields are name, url, image, and webFeed (your RSS feed URL), they pin the show's identity. The sameAs array is the underrated one: it links your site's version of the show to its Apple, Spotify, and YouTube profiles, which helps an engine merge them into one entity instead of three lookalikes. If you only edit one thing, fill sameAs honestly with your real platform URLs.

Illustration for 'The copy-paste PodcastEpisode JSON-LD'

The copy-paste PodcastEpisode JSON-LD

Put this on each episode's dedicated page, and link it back to the series with partOfSeries. PodcastEpisode defines no unique properties of its own, it inherits everything from Episode and CreativeWork, so the field list below is what those parents give you, per Schema.org PodcastEpisode.

``html ``

Three fields trip people up. duration must be ISO 8601, PT48M30S means 48 minutes 30 seconds, not 48:30. associatedMedia is the actual audio file; give it both contentUrl (the direct MP3 link) and encodingFormat (audio/mpeg). And partOfSeries must point at the exact name and url you used in the series markup, mismatched values fragment your catalog instead of connecting it.

What you actually optimize for a search feature: video and article schema

Since there's no podcast rich result, the schema that can earn a SERP feature for your episode is VideoObject (if you publish a video episode) and Article (for the written episode page). This is where effort converts to visibility.

For a video episode, Google's video structured data docs require three fields on VideoObject: name, thumbnailUrl, and uploadDate. Add contentUrl and description and you've covered the essentials. The feature worth chasing here is key moments, the clickable chapter segments under a video result. You enable them with Clip markup (you label each segment with a name, a startOffset in seconds, and a url) or SeekToAction (you tell Google your timestamp URL format and let it auto-detect). Both need the video to run at least 30 seconds. For a conversational podcast, key moments are the closest thing to that old episode-list result you wanted.

For the written page, Article (or BlogPosting) markup is standard and well supported. If your episode page is a real article, transcript, summary, links, mark it up as one. That, plus a clean PodcastEpisode block, is the realistic ceiling for what schema gets a podcast page in Google today.

What schema still earns a search feature for podcasts Video key moments and Article are still supported; a dedicated podcast rich result never existed; FAQ rich results were deprecated in August 2023 and HowTo was deprecated the same year. Worth the effort vs. effort wasted Still earns a feature Won't earn a feature VideoObject + key moments (Clip) Article / BlogPosting on the page PodcastSeries / PodcastEpisode (clarity for crawlers + AI, not a SERP box) Dedicated "podcast" rich result (never existed in Google's gallery) FAQ rich results (ended August 2023) HowTo rich results (deprecated 2023) Sources: Google structured data gallery & video docs; Search Engine Land; Search Engine Journal.
Spend schema effort on the left column. Sources: Google search gallery; Search Engine Land.
Illustration for 'Common mistakes that quietly waste the effort'

Common mistakes that quietly waste the effort

Chasing FAQ and HowTo schema for SERP features. Both are dead weight now. Google deprecated FAQ rich results in August 2023 (Search Engine Land; Search Engine Journal), and HowTo rich results were deprecated the same year. The markup is still valid Schema.org and harmless to keep, but do not add it expecting a search feature, that ship sailed.

Marking up audio you don't host. If your episode lives only on Spotify or Apple and your contentUrl points at a player you don't control, the markup describes a page Google can't fully verify. Schema works best on a page you own where the audio (or video) is actually present.

Letting series and episode values drift. The show's name and url in PodcastSeries must match the partOfSeries block in every episode, character for character. A typo or a trailing slash splits one show into two entities in a machine's eyes.

Markup that contradicts the visible page. Structured data must describe what a user actually sees. If your JSON-LD says the episode published June 20 but the page says June 22, you've planted a mismatch that erodes trust signals. Generate the schema from the same data that renders the page.

Skipping validation. Paste the episode URL into Google's Rich Results Test or the Schema Markup Validator before you call it done. Two minutes catches the ISO-8601 duration error, the broken contentUrl, and the missing required field that would otherwise sit there doing nothing.

Tools for generating and checking schema

You can hand-write the JSON-LD above, it's short, or generate it. Most podcast hosts and CMS plugins output PodcastEpisode and Article schema automatically; check what yours emits before adding your own, because two conflicting blocks confuse crawlers. Free schema generators exist for both types if you want a form instead of a code editor.

For validation, use Google's Rich Results Test and the Schema Markup Validator, both are free and authoritative. If you publish video episodes, also watch Search Console's Video pages report to confirm key moments are firing; it can take days or weeks to appear, so don't panic on day one.

Where QuickReel fits: schema makes your page legible, but the thing that brings new listeners to that page is the clip they saw in a feed. If you want the clips that point people back to your episode pages, paste your episode's YouTube link into QuickReel and get a handful of captioned clips back free, the markup gets you found, the clips get you watched.

FAQ

Do I need both PodcastSeries and PodcastEpisode schema? Use both. PodcastSeries goes once on your show page to establish the show as an entity; PodcastEpisode goes on each episode page and links back with partOfSeries. Together they form a connected catalog a crawler can navigate. Either one alone leaves the relationship implicit and weaker.

Will adding PodcastEpisode schema improve my Google ranking? Not directly. Structured data is not a ranking factor on its own, it's a clarity signal that helps Google understand the page and qualify it for any features it's eligible for. Rankings still come from content quality, links, and relevance. Schema helps you get understood, not promoted.

What's the right format for episode duration? ISO 8601. Write 48 minutes 30 seconds as PT48M30S, not 48:30 or 48 min. A one-hour-five-minute episode is PT1H5M. The P and T are required literals. Validators flag a non-ISO duration as a warning, and a malformed one is simply ignored.

Is FAQ schema worth adding to my episode page? Not for search features, Google deprecated FAQ rich results in August 2023 (Search Engine Land). A visible FAQ section is still useful for readers and AI answer engines, and the markup is harmless to keep. Just don't add it expecting a SERP box.

Where should the JSON-LD go on the page? Inside a