A feed needs a dependable way to identify an episode even when its visible details change. In podcast RSS, the GUID serves that role. Apple Podcasts requires each episode to have a globally unique identifier that does not change.
Keep identity separate from presentation
A title, summary or audio file name may need correction. Do not use those changing values as your only idea of episode identity. Before editing a published item, record its existing GUID and confirm that the hosting workflow preserves it.
For example, correcting a guest's name in the title should normally remain an update to the same episode. Creating a second item with a new identifier can lead to duplicate-looking entries or a different treatment by listening apps.
A file move and an editorial replacement are also different from publishing a new episode. Decide which action you intend before changing feed fields.
Inspect the generated feed
After saving an update, compare the episode's identifier with the previous version. Check the item in the feed, not only the title shown in the dashboard. Also confirm that the audio enclosure still points to the intended file.
If a migration tool proposes rewriting identifiers, stop and read its current migration guidance before applying the change to the whole catalog. Keep a feed snapshot for comparison, with private information handled appropriately.
Ask the hosting provider when an identity change is unavoidable or unclear. Do not test an uncertain migration on the only live feed. Stable identifiers are a small technical detail with a large practical purpose: they help services recognize the same episode as it moves through corrections, imports and routine metadata updates.