AIScan.site
Publishing & media

AI readiness for podcasts and video shows

Forty minutes of excellent audio, and nine words of text on the page.

E3C3E5D2C2

The moment

Lena, who produces an interview show about supply chains

A researcher asks an assistant which podcast episodes cover port automation and who was interviewed, and the show that has three such episodes is never mentioned.

What the agent needs: Which episode, which guest, and what was said.

What actually happens: Episode pages contain a player embed, a one-line description and nothing else. There is no transcript, no guest name in text, and no feed link on the site itself. Assistants have nothing to read.

Which dimensions decide it, and why

AIScan grades five dimensions. These are the ones that carry the outcome for this kind of business.

Content

Transcripts are the whole game. An episode without one is unsearchable and uncitable, and a transcript with speaker names and headings converts forty minutes of audio into the most quotable page on the site.

Discoverability

A feed is native to podcasting but often only lives with the host, never linked from the site. Publishing and linking it, plus a sitemap of episode pages, is how the show gets indexed as content rather than as a player.

Content

PodcastEpisode structured data with guest, duration and publication date is what lets an assistant answer 'which episode featured X' precisely instead of approximately.

The checks that matter here

Fix guides: /docs/checks/content · /docs/checks/discoverability · /guides

Most sites like this run on Astro — read the Astro playbook for where each fix lives.

Questions we get asked

Do transcripts actually change anything?
They are the difference between a page with no content and a page with several thousand words of it. In this category nothing else comes close.
Auto-generated transcripts — good enough?
Yes, with names and jargon corrected. Perfect prose is not the requirement; accurate, readable text is.
Should the transcript be on the episode page or a separate one?
On the episode page, in the HTML. Behind a 'show transcript' toggle is fine as long as the text ships and CSS does the hiding.
What structured data should episodes carry?
PodcastEpisode or VideoObject with name, datePublished, duration and the guest as a Person. That is what makes guest queries resolvable.
Our feed lives with the hosting platform. Is that a problem?
Link it from your own site and keep episode pages canonical on your domain, or the platform accrues everything you make.
How do we check an episode page?
Scan one episode URL. If E3 reports almost no server-rendered text, that is the transcript gap in one line.

Scan your site and see where you actually stand

Free, no account, about twenty seconds. The report names every failing check by ID, shows the evidence we found, and gives the fix for your platform — plus a hand-off prompt you can paste straight into Claude Code or Cursor.

Run a free scan npx aiscan-cli yoursite.com

Prefer to read first? Browse every check we run or the guide library.

Next in Publishing & mediaAI readiness for news sites and magazines

Also covers: podcast, audio show, interview show, video series, youtube channel, webinar series, conference talks, episode transcripts, show notes, audio drama, radio show, vodcast, creator site, media archive, guest interviews, captions and subtitles.