> 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/create-and-publish/publishing-and-distribution/moderate-comments.md).

# Moderate comments

Review listener comments on your podcast website, publish or reject them, and control visibility.

Use this task to review the comments that listeners leave on the episode pages of your podcast website. New comments are not visible until you publish them.

## Before you start

* You need the owner role, a collaborator role, or an organization role with permission to manage comments.
* Comments must be enabled for the podcast website. Open the podcast, select the **Blog** tab, and check **Show comments on blog**. The setting is on by default.
* The website theme must contain the comments section. The setting notes **Following code must be present in the blog templates (eg show\.html).**

![Blog tab of a podcast in the classic view with the Comments section expanded and the checkbox Show comments on blog enabled](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-12530a03061370f669a3dd0ac03effb73ee49088%2Fdoc-distribution-013-classic-show-comments-setting.png?alt=media)

The Show comments on blog checkbox sits in the Comments section under Advanced settings of the Blog tab.

{% tabs %}
{% tab title="Classic view" %}

### Review new comments

1. Open the comments page of your account. The lists are **pending**, **published**, and **rejected**.
2. Open the pending list. Each new comment starts as pending.
3. For each comment, publish it or reject it.

![Comments page in the classic view with the Pending list, the search field, and Publish and Reject buttons for each comment](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d702416b5d99be254fbc3777a7344a07a9eccecb%2Fdoc-distribution-013-classic-pending-list.png?alt=media)

The Pending list shows each new comment with its Publish and Reject buttons.

The lists show 25 comments per page. You can sort by date, state, and nickname, and search by nickname, content, episode title, or podcast title.

### Expected result

A published comment appears on the episode page. A rejected comment stays in the rejected list, and visitors do not see it.

### What listeners can do

* A comment needs at least 10 characters and a nickname.
* The form refuses a submission that arrives too fast with **Sorry, that was too quick! Please resubmit your comment.** This blocks automated spam.
* Listeners cannot answer other comments from the website. Podigee has no reply feature.

### Notification

The podcast owner receives the email **A new comment on your episode '\[episode title]' (\[podcast title])** with the button **Publish, reject or answer to comment here** for each new comment.

### If you cannot complete the task

* The comments page is empty although a listener commented: check that the comment is in the pending list of the correct podcast. Check that your role includes comment management.
* Comments are not shown on the website: check **Show comments on blog** and confirm that the theme contains the comments section.
  {% endtab %}

{% tab title="Podigee workspace" %}

1. Open the podcast and select **Comments** in the sidebar. The sidebar shows the number of pending comments.
2. Under **Audience comments**, keep the status filter on **Pending**. To see the other comments, select **Published**, **Rejected**, or **All comments**.
3. To find one comment, enter a name, a word, or an episode title in the search box.
4. For each comment, select **Publish** or **Reject**.

![Comments page in the Podigee workspace with the Pending filter, the search box, and Publish and Reject buttons on each comment.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-bb016a08024143ffe274303c442720632c9b2a11%2Fdoc-distribution-013-pending-comments.png?alt=media)

Each pending comment has a Publish button and a Reject button.

What is different:

* You moderate the comments of one podcast, not one list for the whole account.
* The page explains **Publishing makes the comment public. Rejecting hides it from listeners. You can publish a rejected comment later.**
* You can sort by **From**, **Episode**, **Received**, and **Status**, and show 5, 10, 25, or 50 comments per page.
* The **Show comments on blog** setting has no page in the workspace. Set it in the classic view.
  {% endtab %}
  {% endtabs %}

## Next step

[Set up the podcast website](/documentation/create-and-publish/hosting-and-management/set-up-the-podcast-website.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/create-and-publish/publishing-and-distribution/moderate-comments.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.
