Podcast Series Schema Generator: Describe Your Show
Create PodcastSeries JSON-LD for the main show page with its name, description, URL, artwork, language, and publisher.
Try the Podcast Series GeneratorWhy podcast show pages can be difficult to interpret
- The show and its individual episodes are marked up as if they were the same entity.
- The canonical show URL, artwork, or publisher is missing from the structured data.
- Names and descriptions differ between the visible page and the JSON-LD.
- Episode pages are not visibly linked from the main show page.
How SwiftSchema helps
The Podcast Series schema generator creates JSON-LD for the show itself: its name, description, canonical URL, artwork, language, and publisher.
Keep PodcastSeries on the main show page. Use PodcastEpisode on each episode page so search engines can distinguish the series from its episodes.
How it works
- 01
Enter the podcast name, description, canonical show URL, artwork URL, and language.
- 02
Choose whether the publisher is an Organization or Person, then add the publisher name and URL.
- 03
Copy the generated JSON-LD or script tag and add it to the canonical show page.
- 04
Validate the markup with Schema.org Validator and confirm every value matches the visible page.
Ready to build the markup?
Add the visible show facts, copy the markup, and validate it.
What is PodcastSeries structured data?
PodcastSeries describes a podcast as a complete show. Podcast structured data for a series can identify the show name, summary, language, canonical page, cover artwork, and publisher. Add it to the main page that represents the show.
Individual episode pages should use PodcastEpisode instead. This separation helps crawlers understand which page represents the full series and which pages represent individual recordings.
Does PodcastSeries create a rich result?
PodcastSeries does not currently have a dedicated Google rich result. Adding it does not guarantee a ranking improvement or special search display.
The markup is still useful when it accurately describes the visible show page. It gives search engines and other systems a machine-readable record of the series and its publisher without replacing the page content listeners rely on.
Essential properties to include
name: The public podcast title shown on the page.description: A concise summary of the show and its format.url: The canonical URL of the main show page.image: A publicly accessible URL for the show artwork displayed on the page.inLanguage: The primary language, such asen-US.publisher: The Person or Organization responsible for the show. Include the visible publisher name and its public URL when available.mainEntityOfPage: The canonical show URL. SwiftSchema uses the Series URL for this value.
Prepare the show page first
- Confirm the canonical show URL: Use the main page for the complete podcast, not an episode URL or private feed URL.
- Use the public show name: Match the spelling and capitalization visitors see on the page and listening platforms.
- Write a visible description: Summarize the topic, format, and intended audience without adding claims that appear only in the JSON-LD.
- Choose stable artwork: Use an image URL that crawlers can access without authentication or expiring parameters.
- Confirm the publisher: Decide whether the show is published by a person or organization and use the same identity shown on the page.
- Link the episodes: Give listeners visible links to episode pages. Add
PodcastEpisodemarkup to those pages separately.
How to use the Podcast Series schema generator
- Enter the podcast title and visible show description.
- Add the canonical Series URL and public Image URL.
- Enter the primary language code.
- Choose Person or Organization for the publisher, then add its name and URL.
- Copy the JSON-LD or script output and add it to the canonical show page.
- Validate the finished markup and compare every value against the rendered page.
Common errors and fixes
- Using PodcastSeries on episode pages: Keep series markup on the main show page. Use
PodcastEpisodeon each episode page. - Marking up a feed URL as the show page: Use the canonical web page in
url. Link the RSS feed visibly when it helps listeners. - Mismatched artwork: Use the same show artwork in the page and JSON-LD, and make sure the image URL is crawlable.
- Missing publisher identity: Add the Person or Organization that is visibly credited for the show.
- Hidden or outdated descriptions: Keep the schema description aligned with the summary visitors currently see.
- Orphaned episodes: Link episode pages from the show page and use
partOfSeriesin episode markup when appropriate.
Maintenance checklist
Revisit the markup when the show name, artwork, publisher, canonical URL, language, or description changes. If the page moves, update both url and mainEntityOfPage.
Check the visible episode links after publishing or removing episodes. The structured data should describe the current show page rather than an older feed or platform listing.
Podcast Series schema checklist
- Use
PodcastSerieson the canonical show page. - Include a visible name and description.
- Add the canonical URL, public artwork URL, and language.
- Identify the visible Person or Organization that publishes the show.
- Link episode pages from the show page and use
PodcastEpisodeon those pages. - Keep every JSON-LD value consistent with the rendered page.
Validation workflow
- Generate the PodcastSeries JSON-LD with SwiftSchema.
- Check the JSON-LD in the JSON-LD Formatter + Validator Lite.
- Validate the structure with Schema.org Validator.
- Inspect the live page source and rendered DOM to confirm the markup is present.
- Recheck the markup after major show, publisher, URL, or artwork changes.
Required properties
namedescription
Recommended properties
urlimageinLanguagepublisher.namepublisher.urlmainEntityOfPage
{
"@context": "https://schema.org",
"@type": "PodcastSeries",
"name": "The SwiftSchema Show",
"description": "Conversations about structured data and practical SEO.",
"url": "https://your-site.invalid/shows/structured-data-weekly",
"image": "https://media.invalid/shows/structured-data-weekly/cover.jpg",
"inLanguage": "en-US",
"publisher": {
"@type": "Organization",
"name": "SwiftSchema",
"url": "https://your-site.invalid"
},
"mainEntityOfPage": "https://your-site.invalid/shows/structured-data-weekly"
}FAQs
What does PodcastSeries schema describe?ShowHide
It describes the overall podcast show, including its name, description, language, artwork, canonical URL, and publisher.
How should I connect podcast episodes?ShowHide
Link each episode from the visible show page and add PodcastEpisode JSON-LD to each episode page. Episode markup can use partOfSeries to reference the show.
Where should I place PodcastSeries markup?ShowHide
Add it to the canonical page for the podcast show, not every episode page. Keep the JSON-LD aligned with the show information visitors can see.
Should I add the podcast RSS feed to PodcastSeries?ShowHide
Schema.org does not require a dedicated feed property for PodcastSeries. Link the public feed in the visible page content when it is useful to listeners.
Does PodcastSeries create a Google rich result?ShowHide
PodcastSeries does not currently have a dedicated Google rich result. Use it to describe the show accurately, then validate the structure with Schema.org Validator.