Pages vs Posts: What’s the Difference?

Pages vs Posts

WordPress has two main content types out of the box – Pages and Posts – and it’s easy to use the wrong one. Here’s how to tell them apart.

Pages

Pages are for static, standalone content that doesn’t really change based on date – things like “About Us”, “Contact”, “Safeguarding”, or a specific policy. Pages can also be nested (a page can have “child” pages underneath it) and are usually what your main menu links to.

Posts

Posts are for timely content, added to over time – news items, updates, blog-style entries. Posts belong to Categories and can have Tags, and they usually appear in a reverse-chronological list somewhere on the site (like a News page).

Custom Post Types

Beyond the standard Pages and Posts, our sites also use Custom Post Types for specific kinds of content – for example, property listings or other structured entries managed through our custom plugins. These behave similarly to Posts in the editor, but usually have their own dedicated section in the left-hand admin menu (rather than living under “Posts”), and often have their own fields tailored to that content type. If you’re looking for somewhere to add something and it doesn’t feel like a normal Page or Post, check the admin menu for a dedicated section first before creating a new Page.

Categories vs Tags

Both help organise Posts, but they work differently:

• Categories are broad, structural groupings – think of them like chapters or sections (e.g. “Parish News”, “Events”, “Safeguarding Updates”). Every post should usually sit in at least one category, and categories can be nested (parent/child) similar to pages.
• Tags are more like keywords – specific, granular, and not hierarchical (e.g. “fundraising”, “youth group”, “Peterborough”). A post can have several tags, and tags are optional.

A simple way to think about it: if you’d expect it in a site’s main navigation or a filter dropdown, it’s probably a Category. If it’s more of a descriptive label for search and related-content purposes, it’s a Tag.

Page hierarchy in practice

Nesting pages (making one a “child” of another) doesn’t just affect the main menu – it usually affects the page’s URL too. A child page under “Safeguarding” might get a URL like /safeguarding/policy-updates/ rather than /policy-updates/, reflecting its place in the structure. Many themes also generate breadcrumbs automatically from this hierarchy (e.g. Home > Safeguarding > Policy Updates), so getting the parent/child structure right helps both navigation and how visitors understand where they are on the site.

Featured images

Both Posts and (depending on the theme) Pages can have a Featured Image set – found in the block settings sidebar under “Featured image”. This is the image used on listing pages, social media previews, and search engine results, separate from any images placed within the content itself. It’s easy to forget to set one, which often results in a blank or default placeholder thumbnail showing up on a News listing or when the link is shared elsewhere – worth checking before publishing.

A simple rule of thumb

1. Is this a permanent part of the site’s structure? → Page.
2. Is this a dated update, story, or announcement that will eventually be old news? → Post.
3. Is it a specific, structured content type with its own admin section (e.g. property listings)? → Custom Post Type.

Tip: If you’re not sure which to use for something, it’s worth asking – moving content from a Post to a Page later isn’t always straightforward.