Audio Metadata
Make podcasts and recordings understandable with audio elements, AudioObject markup, episode notes, feeds, and transcripts.
Audio needs a visible landing page, episode title, summary, and accessible text alternative. An audio URL by itself provides very little context for search or generative discovery.
| Field or attribute | Purpose | Best practice |
|---|---|---|
| <audio controls> | Exposes a native audio player. | Keep native controls or provide accessible equivalents and a direct media fallback link. |
| preload | Hints how much audio to fetch initially. | Use metadata or none to avoid unnecessary downloads. |
| name | Names the recording or episode. | Use a specific episode title rather than the series name alone. |
| description | Summarizes the episode or recording. | Include the topic, important guest or organization names, and a concise answer to what the listener will learn. |
| contentUrl | Points to the actual audio bytes. | Use a stable MP3, AAC, WAV, or other supported URL appropriate to the audience, not the episode page. |
| encodingFormat | Declares the media MIME type. | Use the correct value, such as audio/mpeg or audio/mp4. |
| duration | Declares recording duration. | Use ISO 8601 syntax, such as PT24M18S. |
| uploadDate | Declares publication time. | Use an accurate ISO 8601 date and keep it consistent with episode notes and feeds. |
| transcript | Provides the spoken content as text. | Prefer a complete visible transcript with speaker labels and timestamps. Link to it or include it in AudioObject when practical. |
| associatedArticle | Connects the media to its written context. | Use episode notes or a related article that genuinely expands the audio content. |
| RSS enclosure | Delivers podcast episodes to podcast clients. | Provide the episode file URL, correct MIME type, and byte length; keep episode notes and artwork descriptive. |
AudioObject clarifies the media entity, but there is no universal audio rich-result equivalent to every video feature. The visible episode page and transcript remain essential.
<audio controls preload="metadata">
<source
src="https://cdn.example.com/podcasts/media-workflows-12.mp3"
type="audio/mpeg"
/>
<a href="https://cdn.example.com/podcasts/media-workflows-12.mp3"
>Download the episode</a
>
</audio>{
"@context": "https://schema.org",
"@type": "AudioObject",
"name": "Media Workflows, Episode 12: From Recording to Discovery",
"description": "A conversation about reusable video production, transcripts, and media discovery.",
"contentUrl": "https://cdn.example.com/podcasts/media-workflows-12.mp3",
"encodingFormat": "audio/mpeg",
"duration": "PT24M18S",
"uploadDate": "2026-10-21T09:00:00-05:00",
"transcript": "In this episode, we explain how a reusable media workflow starts with a clean recording..."
}For long episodes, render the full transcript in the page rather than placing an enormous JSON string in every response. Add speaker names, chapter links, and corrections for names, products, and technical terminology.
Why transcripts matter
“A transcript gives listeners another way to consume the episode and gives machines a precise text representation of the spoken content.”
transcriptaccessibilitydiscovery