Spreaker prefix not working? Check these causes

If your Spreaker prefix is not working, confirm that RSS Settings are enabled for the correct podcast and inspect the Tracking URL prefix field. Spreaker officially documents third-party prefixes there. For Podder, paste the unique URL with the required trailing slash, save it, then verify the public enclosure and episode playback before checking fresh analytics.

Do not keep changing the field while diagnosing it. One controlled test makes the failure easier to locate.

Spreaker prefix not working: check these causes

Record the podcast, public feed, exact prefix, save time, test episode, and player. Then work through these causes in order.

1. RSS Settings are off, or the prefix went in the wrong field

Spreaker's official third-party prefix guide starts in the CMS. Open the podcast you want to track, go to RSS Settings, and set them to Enabled.

Its broader RSS settings guide also lists Tracking URL prefix among the fields available on that page. If RSS Settings are disabled, editing another part of Podcast Settings will not install the prefix.

Spreaker's field is called Tracking URL prefix. Podder's Spreaker prefix installation guide calls it the Tracking URL field and places it at the bottom of RSS Settings. Both sources tell you to save the change.

Fix: select the intended podcast, enable RSS Settings, and paste the URL into Tracking URL prefix rather than hand-editing individual enclosure URLs. Select Save, then reopen the page to confirm that the value remains.

2. The Podder URL is incomplete or lacks its trailing slash

Podder's Spreaker guide specifically instructs you to add the unique Podder prefix with / at the end. A missing character, extra space, copied example, or identifier from another show can prevent the intended route from working.

Fix: copy the complete prefix again from the correct Podder show. Confirm the protocol, domain, show-specific identifier, and final slash. Do not type it from memory. What is a podcast prefix? explains why the exact address matters to delivery.

3. The test episode is not public and downloadable

Spreaker says the prefix is automatically added to public, downloadable episodes included in the RSS feed. A private, limited, unpublished, or otherwise unavailable episode is not a reliable test of the public feed path.

Fix: choose one published episode that appears in the public RSS feed. Inspect that episode's enclosure URL rather than testing a draft or private link.

4. The feed has not updated, or playback fails

The field itself is not final proof. Open the public RSS feed and inspect a published episode's enclosure. The route should include the expected prefix and continue to the Spreaker-hosted media.

Podder says the update can take up to 24 hours. If the expected route remains absent after that window, preserve the feed URL, enclosure URL, screenshot, prefix value, and save time. Send that evidence to Spreaker or Podder support. Changing a podcast directory listing will not repair the enclosure distributed by the feed.

Spreaker warns that an incorrectly set prefix can break the RSS feed. It also notes that the podcast becomes dependent on the outside tracking service: if that service is unavailable, episode downloads can become unavailable too.

Fix: stop making further edits and retain the exact failing media URL. Test the same public episode once through a normal player. If it fails, ask Spreaker and the prefix provider to identify where the request stops. Restore the last known working configuration with their guidance if audience playback is affected.

The general Podder prefix guide gives the request-path explanation and a basic verification sequence.

5. Playback works, but the numbers look wrong

A prefix starts observing qualifying requests after it enters the delivery path. It does not import earlier Spreaker downloads.

Spreaker and Podder can also collect at different points and apply different filtering, time zones, date cutoffs, and processing schedules. A numerical difference alone does not prove the prefix failed. Spreaker's statistics processing guide says current-day listening stats update hourly, then undergo recalculation the following morning and for two more days. Avoid reconciling a provisional Spreaker number against a settled report.

Fix: mark the installation time and use one fresh public playback test. Check the intended Podder show after normal processing, comparing the same episode, post-installation dates, and time zone. Keep Spreaker as the source for the host's earlier history and do not compare a new Podder series with the show's lifetime total. Use how to measure podcast downloads to keep each provider's definition beside its total.

How to verify the Spreaker prefix fix

1. Confirm the correct podcast and public RSS feed.
2. Enable RSS Settings.
3. Confirm the exact Podder URL and trailing slash in Tracking URL prefix.
4. Save, reopen the settings page, and verify the value remains.
5. Inspect a public, downloadable episode's enclosure in the feed.
6. Play that episode once through a normal public player.
7. Record the test time and check for fresh activity after installation.
8. Allow up to 24 hours for the feed update before escalating an absent enclosure.

If playback works but fresh activity remains absent, send support the podcast title, feed URL, episode, full enclosure URL, prefix, screenshot, installation time, and test time.

Prevent the next Spreaker prefix problem

• Save the prefix beside the podcast title and feed URL.
• Record who made the change and when.
• Keep one working enclosure URL as a baseline.
• Test playback after any prefix, RSS, or hosting edit.
• Review outside prefix service status before changing a live route.
• Keep Spreaker history and post-installation Podder results separate.

FAQ

Where do I add a prefix in Spreaker? Open the podcast in the CMS, enable RSS Settings, enter the value in Tracking URL prefix, and save. Use Podder's Spreaker guide for its trailing-slash requirement.

Why does the prefix appear but an episode does not play? A malformed prefix or unavailable tracking service can interrupt the media request. Preserve the failing URL and ask Spreaker or the provider to review it.

Will a Spreaker prefix report earlier downloads? No. It begins a new measurement series after installation. Keep Spreaker as the source for earlier periods.

Once the feed path, playback, and fresh activity are verified, start with Podder Analytics.