WordPress pages vs posts: which to use and when
Table of Contents
WordPress pages vs posts comes down to how long the content stays relevant. Pages hold content that stays put and forms your site structure, like your service and contact pages. Posts hold dated content, like guides and news articles, that appears in your blog. ProfileTree plans every WordPress site around this split.
Picking the wrong one rarely breaks a site on the day it goes live. The damage builds slowly: a service page published as a post carries a date that makes it look out of date within a year, and a guide published as a page never reaches the category archives that help visitors find related articles. If you are planning a new site with WordPress web design, the decision is best made at the sitemap stage, before any content is written.
The difference between WordPress pages and posts
Pages and posts look almost identical in the editor, but WordPress treats them as two separate content types with different jobs. Both are stored in the same database table and edited with the same block editor (the default WordPress editor, which builds content from separate blocks for headings, paragraphs, images and tables). The differences lie in how each one is dated and grouped, which in turn decides where visitors come across it.
| Feature | WordPress pages | WordPress posts |
|---|---|---|
| Publication date | Not usually shown | Shown, and used to order the blog feed |
| Organisation | Parent and child pages | Categories and tags |
| RSS feed (the automatic update feed readers subscribe to) | Not included | Included automatically |
| Author display | Usually hidden | Usually shown |
| Where visitors find it | Menus and direct links | Blog page, category archives and related links |
| Typical business use | Services, locations, pricing, legal pages | Guides, news, case studies, company updates |
Neither format ranks better by default. Google ranks the content on the page, so a well-written post can outrank a thin page, and the reverse is also true. What changes is the signal each format sends to visitors: a date tells a reader the content belongs to a moment in time, and a place in the main menu tells them the content describes the business itself.
Which business content belongs on a page
A piece of content should be a page when it describes what your business is and does, and when you would expect to update it in place rather than replace it with something new. A simple check works for most decisions. Ask whether it should sit in your navigation or footer, and whether it would still be accurate in two years with routine edits. If both answers are yes, it is a page.
That covers your homepage, service pages, location pages, pricing, team and about pages, contact details, and legal content such as the privacy policy and terms of business. Campaign landing pages also belong here, because they serve one purpose and are reached from adverts, emails or social posts and not from the blog feed.
Pages can be grouped under a parent page, which keeps related content together in the dashboard and in the address bar. An SEO service can be nested beneath a services page, giving a URL such as /services/seo/, which tells visitors and search engines where the page fits. ProfileTree is a Belfast web design and digital marketing agency, founded in 2011 and based at the McSweeney Centre, and our own service and location pages follow this pattern, from UK-wide services to website redesign for Belfast businesses. For a wider view of how hierarchy affects the whole site, the guide to planning a clear website structure covers menu depth and internal linking in more detail.
Keep the hierarchy shallow. Two levels suit most small business sites, and three is the practical limit before URLs grow long and menus become hard to use on a phone.
Which content belongs in a post
Content should be a post when its value is tied to a date or when it answers one question in depth. Guides, how-to articles, industry news, event write-ups, case studies and company announcements all fit, because readers expect to see when they were written and because they gain from appearing in the feed and in category archives.
Posts are organised with two tools. Categories group posts by broad topic and should map to the services you sell, so a business offering web design and SEO might run categories for each of those and one for company news. Tags describe a post in more detail, and they are optional. Most business blogs work well with five to eight categories and very few tags, because every category and tag creates an archive page that search engines can find, and dozens of near-empty archives add nothing for visitors.
The main job of a business post is to answer a question your customers ask and then point them to the page that sells the answer. A guide on choosing a website platform should point readers to your web design service, and a case study belongs alongside a link to the service it describes. That link pattern is how posts pass visitors, and some ranking value, through to the pages that bring in enquiries. For the publishing steps themselves, our separate guide on how to create and schedule a post in WordPress walks through the editor, categories, featured images and scheduling.
How the posts page setting works
The posts page setting decides where your blog feed appears once your homepage is a normal page. A fresh WordPress install shows your latest posts on the homepage, which suits a personal blog but not a business site. The fix is in Settings, then Reading, under the option labelled “Your homepage displays”, where you choose “A static page” and then pick one page as the homepage and another as the posts page.
Behind the scenes, WordPress records the ID of your chosen blog page in a setting named page_for_posts, and the homepage choice in its partner, page_on_front. Themes and plugins read these settings to decide which template to load, which is why the page you pick behaves differently from every other page on the site.
The most common mistake is writing content on the page chosen as the posts page. The WordPress.org documentation on creating a static front page is clear that anything on that page apart from its title will not be shown, because WordPress replaces the content with your latest articles. If you want an introduction above the feed, add it through the theme. On a block theme (a theme edited through the Site Editor), you do this by editing the blog home template, and on an older theme it is usually a theme option or a widget area.
Name the posts page plainly, using “Blog”, “News” or “Guides”, because its slug becomes the address of your blog archive. Check this setting after any theme change or migration, since a site that suddenly shows a list of posts on its homepage has usually lost its Reading settings.
Creating a page in the block editor
Creating a page takes a few minutes, and the two choices that matter most after the title are where the page sits and what its address is. The steps below apply to the block editor, which has been the default since WordPress 5.0.
- In the dashboard, open Pages and select Add New Page to open a blank editor.
- Write a title that names the service or topic plainly, because most themes use it as the H1 (the main heading search engines read first).
- Build the content with blocks, opening with a short answer to the question the page exists for and following it with supporting detail and a clear next step.
- Open the page settings panel on the right, set the parent page if the page belongs in a section, and edit the slug.
- Preview the page on a desktop and a phone, then publish it and add it to the right menu.
Setting the parent page and slug
Choose the parent before you publish, because a child page takes its parent’s slug as part of its address. Moving a page under a new parent later changes its URL, which breaks existing links unless a redirect is set up.
Edit the slug every time. WordPress builds it from the title, so a page titled “Our web design services for small businesses in Northern Ireland” gets a long slug that should be cut down to something like /web-design/ beneath /services/. Use lowercase letters and hyphens between words, and leave out dates so the page never looks out of date.
Structuring pages and posts for search
Search engines read the structure of a site as well as its words, so the format you choose and the address you give it both matter. Google’s guidance on URL structure recommends a simple URL structure built from descriptive words, with hyphens to separate them, which is what a short, keyword-led slug delivers.
Each page and post also needs its own title tag (the headline shown in search results) and meta description (the summary shown beneath it). WordPress does not provide fields for these by default, so most business sites add an SEO plugin. Our guide to setting up Rank Math in WordPress covers the settings we check first on client sites.
Pages and posts reach visitors through different routes, and both routes need planning. Pages are found through the main menu, the footer and links from other pages, so every important page needs a menu link; our guide to building WordPress navigation menus explains how to set them up. Posts are found through the blog page, category archives and related articles, so each new post should point to at least one older article and to the service it supports.
“A website is a business tool before it is anything else, and deciding what a page is and what is a post is one of the first places that shows. At ProfileTree we build on WordPress because a Belfast business has to be able to run its own site once we hand it over, and that includes knowing where each new piece of content belongs. The sites that keep earning are the ones where the owner still publishes in the right place every week,” says Ciaran Connolly, founder of ProfileTree.
Fixing content published in the wrong format
Content in the wrong format can be moved, but the move needs care if the content already ranks or has links pointing to it. The usual signs are services carrying a publication date and an author byline, or long guides sitting in the menu with no place in the feed.
Start with the content that brings in enquiries. A service published in the blog is worth moving first, because the date and blog layout undersell it and it cannot be nested beneath your services section. WordPress has no built-in switch between the two formats, so most sites either recreate the content in the right format or use a plugin built for the job, such as Post Type Switcher.
Check the URL before and after the move. Where your permalink settings give posts and pages the same address pattern, the content can often keep its original address. Where the address changes, set up a 301 redirect (a permanent redirect that sends visitors and search engines from the old address to the new one) on the day of the move, then update the internal links across the site so they point straight to the new address. Leave content in place where it already ranks well, and the format is only a minor mismatch, because a working page is worth more than a tidy dashboard.
What to have ready before a WordPress site review
A review of your page and post structure moves faster, and costs less, when the reviewer has the right access and context from the first day. Most of what is needed already exists in your business, and gathering it usually takes less than an hour.
- Administrator access to the WordPress dashboard, or a named person who can create a login for the reviewer.
- Access to Google Search Console for the site, so the reviewer can see which pages and posts already earn impressions and should be left where they are.
- A list of the services you sell and the towns or regions you serve, which decides what each service page covers and where it sits on the site.
- A note of any pages whose address has changed in the past year, because old URLs left without redirects often explain lost rankings.
- The names of the people who publish content, so any training can be planned around how they work now.
None of this needs to be tidy before you share it, and gaps in the list are useful information in their own right. A site with no Search Console access, for example, tells the reviewer that nobody has been watching how the pages perform. With these details in hand, the review can show which content should move first and what the work will cost, so you can choose the route that suits the business.
Getting help with your WordPress site
Most of the problems in this guide come from decisions made early in a build, or from content added later by people who were never shown how the site is meant to work. Both have practical fixes.
If your site needs rebuilding with a clear page and post structure from the start, a new WordPress website from ProfileTree starts at £4,000 plus VAT, and a review of a neglected site is quoted on request. If your team publishes its own content, our digital training for business teams starts at £350 plus VAT and is built around your own website, so people leave knowing which format to use and where each piece belongs. ProfileTree has more than 500 Google reviews with a 5.0 rating, and the team in Belfast can tell you which of those routes suits your site.
FAQs
What is the difference between a page and a post in WordPress?
A page holds content that stays in place, like a service or contact page, while a post holds dated content, like a guide or news item, that appears in your blog feed. Pages are organised into parent and child pages and usually reached from the menu. Posts are organised with categories and tags, carry a date and author, and are included in the site’s RSS feed.
Should a service page be a page or a post?
Service content should always be a page. It describes something your business does on an ongoing basis, it belongs in your navigation, and it should sit within your services section so its address shows where it fits. Publishing it in the blog adds a date that makes the service look dated within months and files it alongside news and articles, which weakens it as the page you want enquiries to come from.
What is the posts page in WordPress?
The posts page is the page WordPress uses to show your list of blog posts once your homepage is set to a normal page. You choose it in Settings, then Reading, by selecting “A static page” and picking a page for the posts. The choice is saved as page_for_posts. Anything you write on that page will not appear, because WordPress swaps it for the feed, so leave it blank apart from the title.
Can I change a WordPress post into a page?
Yes, you can change a post into a page, either by recreating the content as a new page or with a plugin such as Post Type Switcher. Check whether the address changes as a result. If it does, set up a 301 redirect from the old address on the same day and update your internal links, so you keep the visitors and rankings the post had already earned.