Podcast Schema

What this check is looking for

This flag fires when your podcast landing pages and episode pages ship without podcast structured data. Structured data is a block of machine readable markup, usually JSON-LD, that tells search engines exactly what a page is and how its parts relate. For a podcast, the relevant schema.org types are PodcastSeries for the show as a whole and PodcastEpisode for each individual episode, with an AudioObject describing the actual audio file.

Without it, a crawler lands on your episode page and sees paragraphs of text. It cannot reliably tell that this is episode 42 of a series, who hosts it, how long it runs, when it published, or where the audio lives. Add the markup and every one of those facts becomes explicit rather than guessed.

Why podcast schema matters for SEO

Three reasons, in order of how much they move the needle.

Eligibility for richer presentation. Structured data is how you become eligible for enhanced results. Google does not guarantee any rich treatment, but you cannot qualify for it without the markup. Clear PodcastSeries and PodcastEpisode data gives your pages the best shot at appearing as something more than a plain blue link.

Entity understanding. Schema connects your show to a named entity with a host, a publisher, a genre, and a run of episodes. That helps search engines build a confident picture of what your podcast is and which queries it should answer, which is exactly the understanding you want feeding rankings.

Voice and assistant surfaces. Assistants and podcast directories consume structured feeds. The cleaner and more explicit your data, the more places your show can be picked up correctly rather than mangled or skipped.

How to detect whether it is missing

1. Google Rich Results Test. Paste an episode URL and see what structured data Google can read. If it finds no podcast markup, you have your answer.
2. Schema.org validator (validator.schema.org). A stricter check of whether your JSON-LD is well formed and uses the right types and properties.
3. Screaming Frog or Sitebulb. Both extract and validate structured data across a whole site in one crawl, so you can confirm every episode page is covered rather than checking them one at a time.
4. Search Console Enhancements reports. Where Google surfaces structured data it has parsed plus any errors it hit, useful for spotting markup that exists but is broken.

How to add it, step by step

1. Mark up the show page as PodcastSeries. Include name, url, a square image, the author or host, and the webFeed pointing at your RSS feed. That feed link is important, because it ties your page to the canonical source directories already trust.
2. Mark up each episode page as PodcastEpisode. Set name, episodeNumber, datePublished, description, and partOfSeries pointing back at the show. Do not fake numbers or dates. Pull them from your real publishing data.
3. Describe the audio with AudioObject. Give contentUrl (the real audio file), duration in ISO 8601 like PT38M12S, and encodingFormat. This is the part that makes the audio itself machine readable.
4. Use JSON-LD in a script tag. Google recommends JSON-LD over inline microdata because it is easier to maintain and less likely to break when your template changes. Drop it in the head or body.
5. Keep the markup consistent with what users see. The schema must match the visible page. Marking up an episode that is not on the page, or a duration that is wrong, is a structured data violation and can get the markup ignored.
6. Validate, then request indexing. Run the Rich Results Test again, fix any errors, then submit key URLs in Search Console so Google re-fetches them.

Series versus episode markup at a glance

FAQ