> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/distribute-a-podcast/check-show-distribution-status.md).

# Check show distribution status

Review normalized show status, listing URLs, RSS feed, and next action by platform.

Use the podcast ID to see which destinations are live, pending, rejected, or not submitted.

## Before you start

* Find and inspect the podcast.
* Keep its numeric ID.

## Check distribution

1. Ask your agent to get distribution status for the podcast ID.
2. Confirm the RSS feed URL.
3. Review the summary groups for `live`, `in_review`, `submitted`, `rejected`, and `not_submitted`.
4. Review each connection's stable `platform_key` and normalized `status`.
5. Use `external_url` as the public listing signal when it is present.
6. Check `manual_submission_required` before choosing a next action.
7. Use status and guidance together for the platform you need to resolve.

Podigee creates connection rows for supported platforms when a podcast is created. A default `not_submitted` row is not a fault by itself. The `active` field is a web player or posting toggle, not a directory submission signal.

## Expected result

You can state where the show is live and which platforms need direct submission, a one-time human handoff, review, or investigation.

## If a platform is missing

Do not invent a status. Use the current catalog and handoff guidance. The platform can be outside Podigee's tracked connection set.

## Next step

* [Submit a podcast to a supported platform](/documentation/start-here/ai-agents/distribute-a-podcast/submit-a-podcast-to-a-supported-platform.md)
* [Complete a one-time directory handoff](/documentation/start-here/ai-agents/distribute-a-podcast/complete-a-one-time-directory-handoff.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/distribute-a-podcast/check-show-distribution-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.