Podcast schema
Free Podcast schema generator
21 October 2026 · CiteScore Team · 8 min read
Free AI Answer Snapshot
When customers ask ChatGPT or Perplexity for your trade in your city, who do they name?
We email the Fix Pack within a few business days after payment, once we have the business name, city, service, and public site URL. The re-check in the pack is the same prompts, run again 14 days later. Full refund within 14 days of delivery if the Fix Pack is not useful. Refund policy.
Opens Payhip in a new tab. The shop name on that page is DeskOps Templates (opens in a new tab). Payhip lists a text file with the order. We email the Fix Pack. What happens after you buy.
The free AI Answer Snapshot asks logged-out ChatGPT and Perplexity and records the answer. The Fix Pack is $49. This generator copies facts the page already shows. It does not make an assistant name the business.
AI answers vary run to run. This is a snapshot, not a ranking, and not a promise that any assistant will name the business.
See an example snapshot · See what's in the Fix Pack. Example pages use illustrative numbers. Not a customer result.
Prepared by the CiteScore Team.
Request a free AI Answer Snapshot
Same request as the free snapshot page. AI answers vary run to run. This is a snapshot, not a ranking, and not a promise that any assistant will name the business.
Prepared by the CiteScore Team.
Free, no-signup PodcastSeries and PodcastEpisode JSON-LD generator. Add the show or episode name, the page URL, the RSS feed, and the audio file already on the page. Copy the script. Nothing is uploaded.
Why the show is labeled
A show page can put the title in the H1, a one-sentence description under it, an RSS link in the subscribe list, and a host credit in the footer. An episode page can add a date, a length, and a download. An answer engine that quotes the page still has to decide which string is the show, which URL is the feed, and which file is that episode. schema.org PodcastSeries and schema.org PodcastEpisode are that decision written down. A parser can read those labels without guessing which link was the RSS feed. The script does not create a citation, and it does not rank the page.
Google’s optimization guide, read on 21 October 2026, says structured data is not required for AI Overviews or AI Mode, and that there is no special schema.org type to add for those features. The useful part is the same as for any other labeled fact: the show name, the episode name, the date, and the feed URL are in the HTML, in words a person can read. The longer note on which facts to repeat is the schema guide.
Google’s structured data gallery, read on 21 October 2026, lists the rich results Google Search documents. Video and Article are on that list. PodcastSeries and PodcastEpisode are not. schema.org’s PodcastSeries page, read the same day, says the term is in the “new” area, where feedback from sites can improve the definition. A podcast app still subscribes to the RSS or Atom feed. webFeed points at that file. This script does not replace the feed, and it does not submit the show to a directory. A restaurant that also publishes a show is a different page, on AI search visibility for restaurants. The show still gets its own script.
What each field is
PodcastSeries is the show. The script needs the name a person can see. description is the sentence on that page. url is the show page. image is the cover file. webFeed is the feed URL, usually RSS or Atom. author is a Person or an Organization. schema.org’s own series example uses a person. This form writes the author only when you enter a name. A URL without a name is omitted, so the script does not invent a host. This page does not print a sample personal name. Type the name that is already on the show page, or use the studio when the credit is the studio. One author is one party. A second host has to be added by hand as an array, and only when the page names that second host.
PodcastEpisode is one episode. datePublished is YYYY-MM-DD, or a date and time. schema.org duration is the length in ISO 8601. Thirty-two minutes and fifteen seconds is PT32M15S. A zero length is left out. episodeNumber is an integer when you enter a whole number, and text when the page shows a label such as S2E4. schema.org associatedMedia is a media object that encodes the work. The JSON-LD example on the PodcastEpisode page uses a MediaObject and a contentUrl. This form writes an AudioObject, which is a MediaObject, because the field is the audio file. A video file does not belong there. A watch page uses the Video schema generator.
schema.org partOfSeries is the series this episode belongs to. This form writes a PodcastSeries with the show name, and the show URL and webFeed when those are valid. The feed stays on the series. It is not a property of the episode. A series URL without a show name is left out. schema.org timeRequired is the approximate time it takes to get through the work. The PodcastEpisode JSON-LD example uses it for the running time. This form writes duration instead, because that is the Episode property defined as the length of the item. Do not paste timeRequired next to it with a different length.
Google’s structured data policies, read on 21 October 2026, say not to mark up content that is not visible to readers of the page, and that the structured data must be a true representation of the page content. The copy block is one script tag. Paste it into the HTML the server sends. Answer engines often skip text that only appears after JavaScript runs. Show notes that are an article, with a headline and a byline, can also use the Article schema generator. Do not describe the same date in two scripts that disagree. The free check lists the JSON-LD @type values on the homepage. A show URL at another path is outside that fetch. Markup still has to match the copy a person can read.
How to install it
- Copy the script.
- Paste it into the HTML the server sends for that show page or that episode page, in the head or the body.
- Confirm the same name, description, page URL, image, feed, date, length, episode number, and audio file are visible on that page.
- Use PodcastSeries on the show. Use PodcastEpisode on each episode. Leave the series name blank only when the episode page does not name the show.
What to leave out
- A host, a date, a length, or an episode number the page does not show.
- An author URL without the name. Clear the URL or add the name.
- A series URL or an RSS URL on an episode when the series name is blank.
- A video file in the audio URL. A watch page uses VideoObject.
- timeRequired with a different length than duration.
- One series script that lists every episode. This form does not write that list.
- The same episode block on every URL of the site.
Questions about podcast schema
Does PodcastSeries or PodcastEpisode schema guarantee an AI citation or a Google rich result?
No. schema.org defines PodcastSeries as an episodic series of digital audio or video files a person can download, and PodcastEpisode as one episode of that series. Google’s structured data gallery, read on 21 October 2026, lists the rich results Google Search documents, including Video and Article. That list does not name PodcastSeries or PodcastEpisode. Google’s optimization guide, read the same day, says structured data is not required for AI Overviews or AI Mode, and that there is no special schema.org type to add for those features. The script does not make ChatGPT, Perplexity, Claude, Gemini, Copilot, Grok, Meta AI, DeepSeek, Mistral, Brave Search, You.com, DuckDuckGo, or Google AI Overviews cite the page.
Which fields does this form require?
schema.org does not list a required property for PodcastSeries or PodcastEpisode. This generator writes a script once the name is present and the type is one of those two. description, url, image, author, webFeed, datePublished, duration, episodeNumber, and the audio file are included only when they are valid. An author URL without a name is left out. On an episode, a series URL or an RSS URL without a series name is left out, so the script does not invent a show.
When should the page be PodcastSeries, and when PodcastEpisode?
Use PodcastSeries on the show page. webFeed is the RSS or Atom URL schema.org describes for that show. Use PodcastEpisode on the page for one episode. partOfSeries names the show. One episode is one script. A second episode is a second page. This form does not write a list of every episode inside the series script.
Where should the script go, and why does it write duration instead of timeRequired?
On the page for that show or that episode, in the HTML the server sends, where a person can already see the name and the other facts you mark up. Google’s structured data policies say not to mark up content that is not visible to readers of the page. The script is built in the browser. Nothing is sent to CiteScore. duration is the Episode property schema.org defines as the ISO 8601 length of the item. The JSON-LD example on schema.org’s PodcastEpisode page uses timeRequired for the same clock time. This form writes duration. Add timeRequired by hand only when you want that example’s property name, and do not write two different lengths. The example’s associatedMedia is a MediaObject. This form writes AudioObject, which is a MediaObject, because the field is the audio file. A watch page for a video episode uses VideoObject.
Get a free AI Answer Snapshot · Fix Pack, $49 · Run the free check
A separate GEO audit PDF covers one public URL.