Podcast update frequency tag: declaring a schedule
Open a source-aware analysis with this article as the primary source.
Add us to your Preferred Sources.

The podcast update frequency tag is channel-level RSS metadata for stating a show's intended release schedule in readable text and structured data. Written as <podcast:updateFrequency>, it can describe a simple weekly cadence, a schedule on selected days, a limited run, a future return from hiatus, or a show that has finished publishing.
How the podcast update frequency tag works
The official Podcast Namespace update frequency specification allows one <podcast:updateFrequency> element under <channel>. Its node value is a free-form schedule that an app may display with other show information. The specification asks publishers to keep that text within 128 characters because aggregators may truncate longer values.
<podcast:updateFrequency rrule="FREQ=WEEKLY;BYDAY=MO,WE">
Every Monday and Wednesday
</podcast:updateFrequency>The readable text tells a listener what to expect. The rrule attribute gives software a recurrence rule defined by iCalendar RFC 5545. The attribute is recommended, but it is not required. Common rule parts in the specification's examples include FREQ for the basic unit, INTERVAL for spacing, and BYDAY for named weekdays.
Keep those two representations aligned. Every Monday and Wednesday pairs with FREQ=WEEKLY;BYDAY=MO,WE, while Every weekday can use FREQ=DAILY;INTERVAL=1;BYDAY=MO,TU,WE,TH,FR. The specification also provides monthly, yearly, and date-specific examples. Choose the rule that describes the schedule. Do not copy a familiar example unchanged without checking that its timing matches your publishing plan.
This is Podcast Namespace metadata, so the feed must declare the namespace before using the element. The RSS namespace explainer covers how extension elements coexist with the core RSS fields in a feed.
Attributes for recurrence, start, and completion
The element has three optional attributes:
| Attribute | What it expresses |
|---|---|
| `rrule` | A recommended iCalendar recurrence rule |
| `dtstart` | The ISO 8601 date or datetime at which the rule begins |
| `complete` | Whether the publisher has no intention to release more episodes |
dtstart becomes required when rrule contains COUNT. A count limits the recurrence to a set number of occurrences, so the rule needs a starting point. If the rule uses UNTIL, the specification says dtstart must use the same date or datetime standard as that UNTIL value.
<podcast:updateFrequency
rrule="FREQ=WEEKLY;INTERVAL=2;BYDAY=MO;COUNT=10"
dtstart="2023-08-28T00:00:00.000Z">
Every other Monday for 10 episodes starting August 28, 2023
</podcast:updateFrequency>A future dtstart can communicate an intended return from hiatus. For a finished show, complete="true" states that the podcast has no intention to release further episodes. If complete is omitted, software should assume false.
<podcast:updateFrequency complete="true">
This series is complete
</podcast:updateFrequency>Do not use complete="true" for a seasonal pause if you plan to return. A future start date and an appropriate recurrence rule convey that plan without declaring the show finished.
What the schedule does and does not say
The tag records publisher intent. It does not publish an episode, schedule a media file, or prove that a release happened on time. Feed readers may display the text, interpret the recurrence rule, ignore the element, or support only part of it. Keep the public wording accurate even if an app does not read the structured rule.
The schedule applies to the channel, not to an individual episode. Episode metadata belongs under <item>. The podcast episode tag guide explains a separate field for episode numbering, while the RSS feed glossary explains the channel and item structure around both fields.
Avoid encoding an aspirational cadence that your production plan no longer supports. If a weekly show moves to every other week, update the node value and rrule together. If only one changes, listeners and software receive different versions of the schedule.
How to verify podcast:updateFrequency
After publishing, open the raw RSS feed. Do not rely only on a hosting dashboard preview. Find the channel-level element and check five details:
- The feed declares the
podcastnamespace. - Only one update-frequency element appears under
<channel>. - The node text is accurate and no longer than 128 characters.
- The recurrence rule matches the readable wording.
- Any
COUNT,UNTIL, or future start configuration follows thedtstartrequirements.
Run the feed through your usual validator, then inspect a fresh fetch to make sure the host did not remove or rewrite the extension. The podcast feed cleanup workflow provides a broader check for feed structure and post-publish playback. Valid XML confirms what the feed contains, but app display still depends on each app's implementation.
When you want delivery data alongside an accurate publishing schedule, start with Podder Analytics.
FAQ
What is the podcast update frequency tag?
The podcast:updateFrequency tag is channel-level Podcast Namespace metadata for expressing a show's intended release schedule as readable text and structured data.
Is the rrule attribute required?
The specification recommends rrule but does not require it. The node value can still provide a readable schedule, though software has less structure to interpret.
What does complete="true" mean?
It means the podcast has no intention to release further episodes. When complete is absent, software should assume false.
See who's actually listening.
Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.
Start free