What Are Posts in a CMS and How Do They Differ From Pages?
In a CMS, Posts are dated content entries that flow in reverse-chronological order and are usually grouped by category or tag — blog articles, news items, product updates, and announcements. Pages are undated, hierarchical, evergreen content such as About, Services, or Contact. The practical test: if the item's value depends on when it was published and it belongs in a feed, it's a post; if it's a permanent destination reached through navigation, it's a page. Most CMS platforms support both, and choosing the wrong one for a given piece of content is one of the most common structural mistakes.
The core difference in one table
| Dimension | Posts | Pages |
|---|---|---|
| Ordering | Reverse chronological (newest first) | Hierarchical or menu-driven |
| Date dependency | Central — publish date is part of the content | Usually none |
| Grouping | Categories, tags, authors | Parent/child page tree |
| Typical examples | Blog articles, news, releases, updates | About, Services, Contact, Privacy Policy |
| URL behavior | Often dated or slug-only (/blog/my-post) |
Often nested (/services/consulting) |
| Lifecycle | Draft → scheduled → published → archived | Draft → published → occasionally revised |
| Volume | High, grows continuously | Low, relatively stable |
The distinction matters because it drives navigation, SEO structure, and how editors work day to day. A "Contact" entry published as a post will drift down a feed and become hard to find; a weekly news item built as a page will clutter your main menu.
What a post typically contains
In most CMS content models, a post is a content type with a defined set of fields. A common configuration includes:
- Title — the headline
- Body — rich text or a block-based editor
- Author — a reference to a user or author entry
- Publish date — used for ordering and display
- Categories / tags — taxonomy for grouping and filtering
- Excerpt or summary — used in listings and feeds
- Featured image — for cards and social sharing
- Status — draft, scheduled, published, archived
- Slug — the URL segment
Not every CMS uses the word "post." Some call them articles, entries, stories, or nodes. What defines the type is the behavior — dated, feed-oriented, taxonomy-driven — not the label.
How publishing states affect visibility
The status field is what separates a CMS from a static file. A typical flow:
- Draft — saved but not publicly reachable; safe for work in progress.
- Scheduled — has a future publish date; the CMS publishes it automatically at that time.
- Published — live at its URL and included in feeds and listings.
- Archived or unpublished — removed from feeds but often still reachable at its URL, depending on the platform.
The expected result of setting a future date is that the post stays invisible until that moment, then appears at the top of the feed. A common snag: some platforms require a scheduled task or cron job to trigger publication, so a post can sit unpublished past its date if that job isn't running.
Why the distinction matters when evaluating a CMS
When comparing platforms, check how each handles these four things:
- Content modeling — can you define custom post types with your own fields, or are you limited to a fixed "blog post"?
- Taxonomy — does it support multiple independent classification systems (categories and tags and authors), or just one?
- Workflow — are draft, review, scheduled, and archived states configurable, and can you restrict who can publish?
- URL and templating — can posts and pages use different templates and URL patterns, or does everything share one layout?
A CMS that treats posts and pages as the same underlying type with a flag will often fight you on navigation and feeds. One that separates them cleanly — as most modern headless and traditional systems do — gives editors a structure that matches how the content actually behaves.
For background on what a CMS does overall, see What Is a CMS and What Does It Actually Do?. For a broader look at the publication this guidance draws on, see What Is CMS Critic and What Can You Find on the Site?.