Short answer: posts are time-stamped blog entries that flow in reverse-chronological order and can be organised with categories and tags; pages are static, standalone content like your About or Contact page that sits outside that stream and has no categories or tags. Use a post for anything dated – news, articles, updates. Use a page for evergreen content that does not belong on a feed. Both are edited in the same WordPress editor and both can be public or private; the difference is how WordPress organises, displays, and lets visitors find them.
Posts and pages are the two content types every WordPress install ships with. They look almost identical in the editor, which is exactly why so many people mix them up. The distinction only becomes obvious once you understand what WordPress does with each one behind the scenes.
Posts vs pages at a glance#
| Posts | Pages | |
|---|---|---|
| Purpose | Dated, time-sensitive content (blog articles, news) | Evergreen, standalone content (About, Contact, Privacy) |
| Order | Reverse-chronological, newest first | No inherent order |
| Categories and tags | Yes | No |
| Hierarchy | Flat – no parent or child | Hierarchical – can have parent pages |
| Appear in RSS feed | Yes | No |
| Author byline and date | Shown by default | Usually hidden |
| Comments | On by default | Off by default (varies by theme) |
| Templates | One post template (mostly) | Can use custom page templates |
| Typical URL |
/2026/06/my-article/
or
/blog/my-article/
|
/about/
|
That table covers ninety percent of what most people need. The rest of this article explains the reasoning behind each row, and the one place the line genuinely blurs.
What posts are for#
A post is a blog entry. It is meant to be read once, around the time it is published, and then it slides down the stream as newer posts appear above it. The blog index, the RSS feed, the category archive, the author archive – all of these are lists of posts in reverse-chronological order.
The defining feature of a post is that it carries metadata WordPress uses to organise it:
- A publish date. Posts are time-stamped, and that timestamp is what orders them. Change a post’s date and it moves up or down the feed.
- Categories. Every post belongs to at least one category – a broad bucket like “Tutorials” or “Company news.” Categories are hierarchical: you can nest a child category under a parent.
- Tags. Tags are free-form, non-hierarchical labels for the specifics of a post – “wordpress,” “caching,” “checkout.” Categories and tags are both taxonomies, WordPress’s system for grouping content, and they are the main reason you reach for a post over a page.
If the content you are writing is dated, belongs in a feed, or you want visitors to browse it by topic, it is a post. News, articles, tutorials, case studies, release notes – all posts. If you are starting a blog on an existing site, adding a blog is really just deciding where that stream of posts will live.
What pages are for#
A page is a standalone document. It is not dated in any meaningful way, it does not appear in a feed, and visitors usually reach it through the navigation menu rather than by browsing a list. Your About page, Contact page, Privacy Policy, Terms of Service, a landing page, the homepage itself – these are all pages.
Two things set pages apart from posts:
- No categories or tags. A page is not part of any taxonomy. There is no “Pages by category” archive because the concept does not exist. Pages are meant to be reached directly, by name, not browsed by topic.
- Hierarchy. Pages can have parent and child relationships. A “Services” page can have “Web design,” “Hosting,” and “Support” as child pages, and WordPress reflects that nesting in the URL:
/services/hosting/. Posts cannot do this – they are always flat.
Because pages are evergreen, themes usually hide the author byline, the publish date, and comments on them. Nobody needs to know when you last touched your Contact page. You can still drop structured content, embeds, or raw HTML into a page exactly as you would in a post – the editor is identical.
How to tell which one you are looking at#
Inside the WordPress admin, posts and pages live under two separate menu items: Posts and Pages. When you create new content, you pick which one from the start, and the choice determines which controls appear in the editor sidebar.
- Open a post and you will see Categories, Tags, an Author dropdown, and a publish date that affects ordering.
- Open a page and those taxonomy boxes are gone, replaced by a Page Attributes panel where you set a parent page and, on some themes, a custom template.
The front end gives it away too. If the content shows a date and a “filed under” category link, it is a post. If it sits in your top navigation and reads like a fixed part of the site, it is a page.
When the line blurs: custom post types#
Here is the nuance the simple “dated vs static” split misses. Under the hood, WordPress does not treat “post” and “page” as two special things – they are both just post types.
post
and
page
are the two that ship by default, but a theme or plugin can register as many more as it wants. These are custom post types, and they are everywhere once you start looking.
WooCommerce products are a custom post type. Portfolio items, testimonials, events, real-estate listings, knowledge-base entries – all custom post types registered by plugins or themes. Each one can behave like a post (with its own custom taxonomies for browsing) or like a page (standalone, hierarchical), or some mix of both, depending on how the developer set it up.
So the real picture is not “posts vs pages.” It is “WordPress has a flexible content-type system, and posts and pages are the two starter types it gives everyone.” Most sites never need more than those two. The moment you do – a structured catalogue of anything that is not a blog article and not a one-off page – a custom post type is the right tool, not a pile of pages or a misused category.
Which one should you use?#
A quick decision list:
- Is it dated, or part of an ongoing series? Post. Blog articles, news, updates, anything you want in the RSS feed.
- Do you want visitors to browse it by topic? Post. Categories and tags only exist for posts.
- Is it a fixed, evergreen part of the site reached from the menu? Page. About, Contact, Pricing, legal pages.
- Does it need a parent or child relationship? Page. Only pages nest.
- Is it a repeating, structured kind of content that is neither a blog article nor a one-off? Custom post type. Products, events, listings, team members.
When in doubt, ask whether the content belongs in a feed. If yes, it is a post. If it would look strange showing up in your blog’s chronological list, it is a page.
Can you convert a post to a page (or the other way)?#
Not with a built-in button, because the two types store their data differently – a post has categories and tags that a page has no slot for, and a page can have a parent that a post cannot. WordPress core does not offer a one-click convert.
You have two options:
- Recreate it. For a single piece of content, the fastest path is to copy the body, create the new type, paste it in, set the relevant attributes, and delete the original. Redirect the old URL to the new one so you do not break inbound links – the URL slug and permalink articles cover how WordPress builds those addresses and how to redirect cleanly.
- Use a plugin. Tools like Post Type Switcher add a dropdown to the editor that flips the type in place, carrying the content over and dropping the attributes that do not apply. Handy when you have dozens to convert.
Either way, watch the URL. Posts and pages often use different permalink structures, so converting one changes its address, and a changed address without a redirect is a broken link and lost SEO.
How Hostney handles posts and pages#
There is nothing host-specific about posts versus pages – the distinction is part of WordPress core, so it works the same on any host. Where hosting matters is everything around the content: how fast those pages load, whether the site stays online when a post goes viral, and how quickly you can recover if an edit goes wrong.
On Hostney, every WordPress install runs in its own isolated container with per-site PHP version control and automatic SSL, and the built-in cache plugin purges automatically when you publish or update a post or page, so visitors always see the current version without you clearing anything by hand. Snapshot backups mean that if a bulk edit or a botched conversion mangles a batch of content, you roll back to a known-good state in a couple of clicks. The content model is WordPress’s; keeping it fast and recoverable is the part a host is actually responsible for.
If you are still deciding whether WordPress is the right platform at all, what WordPress is and whether it counts as a CMS covers the bigger picture – posts and pages are just the two front doors into that content system.
Summary#
Posts are dated, feed-based, browsable by category and tag – use them for blog content. Pages are static, standalone, hierarchical, and taxonomy-free – use them for the fixed parts of your site. Both are edited identically; the difference is purely in how WordPress organises and displays them. And underneath both sits a flexible post-type system, so when you outgrow the two defaults, a custom post type – not a misused page or category – is the next step.