> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/portal-overview/create-blog-post.md).

# How to Create a Blog Post

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Categories** (optional): If you want to organize blog posts by topic, create categories assigned to **Content** first. See: [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md).

### Instructions

1. Navigate to [**ENGAGE > Manage Blog Posts**](https://control.peoplevine.com/blog).

> **Note (Pro Dash):** Navigate to **ENGAGE > Blog > Manage Blog Posts**.

2. Click **Create a Blog Post**.
3. Complete **The Basics**:
   * **Page Name** — Internal name (not visible to members).
   * **Page Title** — Headline displayed on the blog listing and in search results.
   * **Blog Preview** — The short preview shown for the post on the blog listing.
   * **Content** — Add the body of the blog post directly on the page. There is no separate page builder — the content is entered here.
4. Complete **Settings**:
   * **Set Posting Date** — Date and time the post should appear.
   * **Page Status** — Controls visibility (see statuses below).
   * **Assign to a Category** — Select one or more category checkboxes to organize the post.
5. Complete **SEO & Options**:
   * **Meta Keywords** — Up to 10 search terms for SEO.
   * **Brief Description** — Summary text (300 characters max).
6. Set **Visibility** under Permissions & Owner:
   * **Anyone (Public)** — visible to everyone.
   * **Active Members Only** — visible only to members in the membership group(s) you select. For staff-only content, select a dedicated staff membership group.
7. Use the **Blog Preview** and **Content** sections to review the post before publishing.
8. Click **CREATE NOW**.

> **Tip**: Set media files to **Public** visibility in [**ENGAGE > Manage Files**](https://control.peoplevine.com/admin_media.aspx) before using them in blog posts. Files uploaded as "Members Only" will not display inline.

### Best Practice

To preview a blog post before publishing it to members, set **Visibility** to **Active Members Only** and select the staff membership program. This lets staff preview the post in the portal without publishing it to members. The QA portal is for design and layout testing only — content changes made there are not isolated from production.

### What Happens Next

* **On the member side**: The post appears on the blog listing page, sorted newest first. Members can filter by category.
* **Next step**: Add content pages to complement your blog. See: [How to Manage Content Pages](/products/portal-overview/manage-pages.md).

*Last updated: 2026-06-11*


---

# 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://help.peoplevine.com/products/portal-overview/create-blog-post.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.