The short answer
For a correction to the same episode, use the host’s replacement workflow and preserve the original GUID. Before migration, compare old and new episode identifiers.
Know what you are preserving
Podigee describes a GUID as an episode identifier independent of title and date. It recommends keeping it when changing the same episode’s title, date or audio. A changed GUID can make an app display a new or duplicate entry.
Decide whether you are correcting an existing episode or intentionally publishing a different one before choosing a control that creates a new entry.
Make a comparison record
Write down title, public page, GUID and audio filename before using the documented replacement workflow. Compare the published entry afterward. A dashboard field named “ID” may not be the feed GUID.
Before GUID: sample-episode-017 After GUID: sample-episode-017 Audio: corrected export published through host
This is an illustrative record, not an identifier to copy into your feed.
Treat migration as its own check
Podigee recommends comparing GUIDs before redirecting feeds and asking support about discrepancies. Stable identity helps, but does not guarantee identical behavior across apps.
Keep the old export until verification. If duplicates appear, record both entries before further changes. Repeated deletion and recreation makes the history harder to understand. This guide does not replace your host’s migration and redirect instructions.
A checklist to take with you
Tick items as you go. Checks reset when you leave this page.
Sources & scope
These original sources support the factual guidance above. Examples, diagrams and observation worksheets were prepared for this guide; they are not reports of hands-on tests.
Source check: October 23, 2026. Platform behavior can change. Check the linked official documentation when a control or requirement differs.
Keep reading
A published episode is missing from Apple Podcasts: a checking order →Add chapter timestamps to an Apple Podcasts episode description →