Moving from Post 5 “What is a Podcast? No Really!” we now enter the realm of my specific forte – descriptive data or what is better known as metadata. So important is metadata to a podcast that it can literally make or break the relationship with would be subscribers by not convincing them of its value or effectively point a subscriber to content once the subscription is in place.
First, what is metadata?
[ metadata: Referred to as descriptive data, metadata is literally data about data. In the context of a podcast, where the data is an audio or video file, metadata typically describes the date the podcast episode was published and provides a description of the episode to better inform the listener of its contents. Metadata is critical in the development of a podcast and should be implemented with great care to ensure search functionality and proper visual identification. ]
With that under our belt, let’s get started with a quick review of the important aspects of properly developing <title> descriptive data for both <channel> and <item> XML feed tags. The following <title> development standards and support materials represent various extracts from my forthcoming Technical Manual on Descriptive Data for podcasting.
Podcast Title <title>
Task: Compose an appropriate show name to quickly attract attention and inform audience.
Standard: 60 character limitation and directly correlate with the podcast subtitle
Guideline: Create a title that is short, unique, easy to remember, and details the tone and focus of the podcast.
What’s in a name? Absolutely everything! It’s most likely the first thing that will bring attention to the podcast. This is true both before and after subscription. Additionally, the title will be visible in both the player organizational tree and on podcover artwork.
The <title> of a podcast show must attract the audience with a clear message and appeal for their consideration. Keep the name unique but don’t over-embellish: a poor title can potentially lose the listener and they may never subscribe. The title should be quick to remember, as short as possible, and detail the tone, emphasis, and focus of the podcast. Know the intended audience and work from there. So critical are the choice of words that they will be used as scan points after subscription as participants review their bins continuously in search of unique content. To maintain consistency in descriptive data, a “style guide” should be developed. A title should identify a podcast as clearly as a name identifies a person or a title identifies a book.
Episode Title <title>
Task: Compose an irresistible headline to quickly attract the attention of audience and promote topic.
Standard: 60 character limitation and directly correlate with the episode <description>.
Guideline: The episode title should be short, informative, and stimulate interest.
The episode <title> is essential to attract the attention of potential subscribers, but above all else, it is designed to stimulate interest among subscribers around individual episode content. The item <title> should be distinct from the <channel> specific <title> and relate directly to individual show topics.
An episode title acts much the same way as a Web headline does. It’s a clear call to action—it compels a participant to investigate! Regardless of the podcast aggregator or directory a subscriber uses, they will analyze the information in the episode <title> to determine the value of the content. The <title> must provide an incentive to invest time in show content. With many other podcast feeds in a bin, if a <title> doesn’t peak interest subscribers may move on to another show. It is recommended that a controlled vocabulary list be used to maintain consistency throughout the show series.
---
It is my hope that this simplified content will help both veteran and new podcasters better prepare <title> descriptive data for both <channel> and <item> tag data. Enjoy! For more information on descriptive data visit www.podcast-tuneup.com