You made a page. You hit Publish. And now your carefully written “About” text is sitting in the blog feed between two dated articles, looking like it was posted on a Tuesday. That is the moment most people go looking for how to create a page in WordPress, so let’s fix the confusion first and the clicks second.

What is a page in WordPress?

A page in WordPress is for content that isn’t tied to a date. About, Contact, Services, a privacy policy, a landing page for an ad campaign. Pages and posts are the two standard built-in post types WordPress ships with, and they share the same editor, the same title field, the same content block. That similarity is exactly why people mix them up.

How do you create a page in WordPress?

If you’ve already written a post, you already know how to do this. Creating a page is practically the same job. The difference shows up on the right side of the editor: posts offer you categories and tags, pages offer you hierarchies, custom templates, and menu ordering instead.

To add and publish a new page:

  • In the dashboard, click Pages then Add New (or hit the + New button at the top bar and pick Page);
  • Type your title and content, and set a featured image if your theme supports one;
  • Check the Page Attributes box on the right if you want a parent page or a custom template;
  • Click Publish. WordPress confirms with “Page published” and gives you a View Page link.

And that’s how you create a page in WordPress. Easy, right? If the dashboard itself still feels like a foreign country, our walkthrough of what the WordPress admin dashboard actually is covers where everything lives.

Here’s the part nobody warns you about: if you write your About text in Posts instead of Pages, it will appear in your blog feed, in your RSS feed, in your archive pages, and possibly in your “recent posts” widget. That’s not a bug. That’s the post type doing what it was built to do. Delete it and start again under Pages.

How many pages can you have on a WordPress site?

I once got into a conversation about WordPress where somebody asked exactly this, and I found it more interesting than it sounds.

The answer: as many as you want. WordPress itself puts no cap on pages or posts. The real limit is your server. Every page adds rows to your database and, depending on the content, files to your disk. A few hundred pages is nothing. Tens of thousands of thin, image-heavy pages will slow your database queries and your load time, and that’s the point where you start looking at caching or a bigger host.

Practically, the constraint isn’t “how many pages can WordPress hold” but “how many pages can a visitor navigate”. A site with 40 well-organized pages beats a site with 400 that nobody can find their way around.

What is the difference between a post and a page in WordPress?

Pages and posts share titles, content, and the theme’s template files, so they look identical on the front end when a theme wants them to. The differences are structural, and they matter once your site grows past five items.

FeaturePostPage
PurposeTimely, part of a seriesStatic, one-off document
Date in URLOften yes (/2026/11/slug)No
Categories & tagsYesNo
Hierarchy (parent/child)NoYes
Custom page templatesNo (by default)Yes
Appears in RSS feedYesNo
Appears in blog feed & archivesYesNo

A few of those deserve a sentence each:

  • Timeliness. Posts belong to a reverse-chronological stream. Pages sit outside it. Your “About” page doesn’t get old. Your tutorial from 2019 arguably does.
  • Hierarchy. A page can have a parent, so “Our team” can live under “About us” and get a URL like /about/our-team/. Posts cannot be nested. This is the single most useful reason to pick Page over Post for site structure.
  • Categories and tags. Posts get them. Pages don’t. If you want to group content, that’s a taxonomies job, and posts are where taxonomies live.
  • Custom templates. Pages can use a page template your theme ships, such as a full-width or landing-page layout. Posts can’t, by default.
  • Feeds. Posts go into RSS. Pages are excluded. Nobody wants your privacy policy in their reader.

One rule of thumb I use: if you’d be embarrassed to see the item dated, it’s a page. If you’d be embarrassed to see it undated, it’s a post.

Where does the page go after you publish it?

This is the follow-up question that actually matters, because a published page is invisible until you link it somewhere. Two places to look:

Appearance > Menus adds the page to your navigation. Tick the page in the Pages panel, click Add to Menu, drag it where you want it, save. If your theme supports it, the same screen is where you set a static homepage under Settings > Reading.

And if you’re deciding whether a piece of content should be a page or a post, it helps to know the post side of the equation too. Our guide to writing a blog post that’s actually worth reading covers the post format in detail.

Final thoughts

Create the page, publish it, then go add it to a menu. That’s the whole job, and it takes less time than reading this article did. If your page still isn’t showing up where you expect, tell me which menu you added it to and what theme you’re on, and I’ll take a look.

Arrivederci, for now 🙂