One authoritative feed. Clear publishing ownership.

Separate the feed from the website

A readable episode page and an RSS item serve different readers. The page gives people context; the feed presents structured show and episode information. RSS 2.0 organizes content into a channel with items. Use that distinction to decide how a single approved record should populate both outputs without independent copies drifting apart.

Define a release boundary

Do not let a saved draft accidentally become a public feed entry. Name the owner of release approval and record the intended time zone. Inspect the generated item after publication, including identity and media references. Validation is one check; an outside retrieval test is another. Neither replaces listening to the approved audio.

Keep feed changes deliberate

A feed address change deserves a transition plan with the providers that control the old and new locations. Preserve a copy of the previous feed and a mapping of episode identities. Treat an address migration separately from a redesign, so a visual refresh does not unexpectedly become a catalog migration.