Blogging & content · Guide
How to Change a WordPress Page to a Post (Step by Step)

Short answer
WordPress has no built-in button for this, so install the free Post Type Switcher plugin, open the page, set the post type to Post and save. You can also copy the content into a new post or run a WP-CLI command. Afterwards add a category and redirect the old URL.
Key takeaways
- Pages and posts differ only by the post_type field, so conversion is a small change.
- The Post Type Switcher plugin is the easiest method and keeps the ID, comments and date.
- WP-CLI can convert many pages at once with wp post update.
- The URL usually changes, so add a 301 redirect from the old address.
- Assign categories, check menus and clear caches after switching.
Can you change a WordPress page into a post?
Yes, you can change a page into a post, but WordPress has no built-in button for it, so you use a plugin, copy the content, or run a WP-CLI command.
Pages and posts are both stored in the same database table. The only thing that separates them is a field called post_type, which holds either page or post.
That means a conversion is mostly a matter of flipping one value. The page keeps its ID, content, author, featured image and publish date.
What changes is how WordPress treats it afterwards. Posts get categories, tags, an archive date and a place in your blog feed. Pages get parent pages and page templates instead.
If you are unsure which type a piece of content should be, our guide to posts vs pages in WordPress explains the difference in plain terms.
Why would you convert a page to a post?
You usually convert a page to a post when content that was published as a standalone page really belongs in your blog, with dates, categories and RSS.
Common reasons include:
- A news update was published as a page by mistake. It should appear in the blog list and the feed.
- You want the article to show up in category archives. Pages cannot be assigned to categories by default.
- You are restructuring a site. Old landing pages are being turned into regular articles.
- You need comments and related posts. Many themes only show these features on posts.
The reverse case also exists. Sometimes a post should be a page because it is evergreen, like an About or Contact screen. The same methods below work in both directions.
What should you check before converting?
Before converting, make a backup, note the current URL, and check whether the page uses a custom template, has child pages, or sits in a menu.
A few minutes of checking saves a lot of cleanup later. Run through this list first:
- Back up the site. A full backup or at least a database export lets you undo the change if something goes wrong.
- Copy the current URL. You will need it to set up a redirect if the address changes.
- Look for child pages. Posts cannot have parents or children, so any child pages lose that relationship.
- Check the page template. If the page uses a template such as Full Width or a landing template, that setting will not carry over the same way.
- Check menus. Menu items that point to the page may stop working or disappear.
- Check page builder data. Content built with a page builder is usually stored in post meta and moves with the item, but test it.
If you work on a busy site, try the change on a staging site first. That way visitors never see a half-converted page.
How do you change a page to a post with a plugin?
The simplest way is the free Post Type Switcher plugin, which adds a post type option to the editor so you can switch a page to a post and save.
Post Type Switcher on WordPress.org is a small, long-standing plugin that does one job. Here is the usual process:
- Go to Plugins > Add New Plugin and search for Post Type Switcher.
- Install and activate it.
- Open the page you want to convert in the editor.
- In the settings sidebar, find the Post Type option that the plugin adds.
- Choose Post from the dropdown.
- Click Update or Save. WordPress reloads the item as a post.
You can also change several items at once. On the Pages list screen, tick the pages you want, choose Edit from Bulk actions, and look for the post type field in the bulk edit panel.
After the switch, the item appears under Posts instead of Pages. Its ID stays the same, so comments, custom fields and the featured image remain attached.
You can deactivate the plugin once you are done. The conversion is stored in the database, so removing the plugin does not undo it.
How do you convert a page to a post without a plugin?
Without a plugin, create a new post and copy the page content into it through the Code editor, then redirect the old page and delete or unpublish it.
This method gives you a fresh post with a new ID. It is a good choice when you only have one or two pages to move.
- Open the page in the block editor.
- Click the three-dot menu at the top right and choose Code editor.
- Select all the content and copy it. This includes the block markup, so layout is preserved.
- Go to Posts > Add New Post.
- Switch this new post to the Code editor and paste the content.
- Switch back to the Visual editor, then add the title, featured image, categories and tags.
- Set the slug and publish.
The WordPress block editor documentation covers the Code editor and other editor views if you have not used them before.
Keep in mind what does not carry over. Comments, revisions, the original publish date and any custom fields stay with the old page. If those matter, use the plugin or WP-CLI method instead.
Once the new post is live, set the old page to draft or private. Our guide on how to unpublish a page in WordPress walks through those options.
How do you switch the post type with WP-CLI?
With WP-CLI, run wp post update with the page ID and the post_type field set to post, which changes the type in one command.
If you have SSH access, this is the fastest way to convert one page or many. First find the page ID by hovering over the page in the admin list, or run:
wp post list --post_type=page --fields=ID,post_title
Then update the type:
wp post update 123 --post_type=post
Replace 123 with the real ID. You can pass several IDs to the same command to convert a batch. The official wp post update reference lists the other fields you can set at the same time.
Avoid editing the database by hand in phpMyAdmin unless you know exactly what you are changing. A typo in a raw SQL query can affect every row in the table.
If WP-CLI is not installed on your server yet, the official WP-CLI website has install steps. Many managed hosts include it by default.
What happens to the URL after you convert a page?
The URL usually changes, because pages use their slug at the site root while posts follow the permalink structure you set under Settings > Permalinks.
For example, a page at example.com/summer-sale/ might become example.com/2026/11/summer-sale/ or example.com/blog/summer-sale/, depending on your structure. If your structure is plain Post name, the address may stay the same.
WordPress often redirects old slugs automatically, but you should not rely on that for pages that become posts. Set up a proper 301 redirect from the old address to the new one.
Our guide to setting up 301 redirects in WordPress covers plugin and server methods. Redirects keep search rankings and stop visitors from hitting a 404 page.
Google explains in its guide to redirects and Search that permanent server-side redirects are the clearest signal that a page has moved.
If you changed the permalink structure recently or links still break, re-save permalinks. Our guide on how to flush permalinks shows the one-click fix.
What do you need to fix after converting?
After converting, add categories and tags, check the layout, update menus and internal links, and confirm the post appears where you expect.
Work through these items once the switch is done:
- Assign a category. A new post without one lands in Uncategorized. See how to add categories if you need to create new ones.
- Check the template. Your theme uses its single post template now, so sidebars, author boxes and dates may appear.
- Review the publish date. The post keeps the page's original date, which can place it far down your blog list. Change it if it should look recent.
- Fix menus. Replace any menu items that pointed to the old page.
- Update internal links. Search your content for the old URL and update it.
- Clear caches. Purge your caching plugin and CDN so visitors see the new version.
- Resubmit the sitemap. Your SEO plugin will move the item from the page sitemap to the post sitemap automatically.
Which conversion method should you choose?
Choose the plugin for a quick, safe switch from the dashboard, WP-CLI for bulk jobs over SSH, and copy and paste for a clean new post.
| Method | Keeps ID, comments and date | Best for | Skill needed |
|---|---|---|---|
| Post Type Switcher plugin | Yes | One or many pages from the dashboard | Low |
| Copy via Code editor | No | One page where a fresh post is fine | Low |
| WP-CLI wp post update | Yes | Bulk changes on sites with SSH | Medium |
| Direct database edit | Yes | Last resort only | High |
For most site owners, the plugin is the right choice. It keeps everything attached to the original item and needs no technical knowledge.
Can you change a post back into a page?
Yes, the same plugin and WP-CLI command work in reverse, so you can switch a post back to a page by choosing Page or setting post_type to page.
When you go from post to page, categories and tags are no longer shown, though the term links may remain in the database. You can then set a parent page and pick a page template.
The URL will change again, so add a redirect from the post address to the new page address. Do this every time you switch types on a live page.
What problems can come up when converting?
The most common problems are broken links, lost page templates, child pages that lose their parent, and custom post meta that a theme or plugin only reads on pages.
If something looks wrong after the change, try these fixes:
- 404 error on the new URL. Re-save permalinks and clear the cache.
- Layout looks broken. The theme is using the post template. Adjust the post layout settings or use a block that matches the old design.
- Page builder content missing. Some builders only enable themselves for certain post types. Check the builder's settings and allow posts.
- Item does not appear in the blog. Check the status is Published, the date is not in the future, and the category is not excluded from the blog page.
For more detail on how WordPress stores these items, the developer documentation on post types explains the system behind posts, pages and custom types.
Frequently asked questions
Does converting a page to a post hurt SEO?
It does not have to. The content stays the same, so rankings usually hold if you add a 301 redirect from the old URL to the new one, update internal links and let your SEO plugin refresh the sitemap. Problems come from broken URLs, not from the change in post type.
Will I lose comments when I change a page to a post?
Not if you use a plugin or WP-CLI, because the item keeps its ID and comments are linked to that ID. If you copy the content into a new post, comments stay with the old page and do not move across.
Is there a built-in WordPress option to change a page to a post?
No. WordPress core does not include a post type switch in the editor. You need a plugin such as Post Type Switcher, a WP-CLI command, or a manual copy of the content into a new post.
Can I convert many pages to posts at once?
Yes. Post Type Switcher adds the option to the bulk edit panel on the Pages screen, and WP-CLI lets you pass several IDs to one update command. Back up the database first, because bulk changes are harder to undo by hand.
Why does my converted post show an old date?
The item keeps the original publish date from when it was a page. Open the post, change the publish date in the settings sidebar and update it if you want the post to appear near the top of your blog list.
Sources
- Post Type Switcher WordPress.org
- wp post update WordPress Developer Resources
- Post Types WordPress Developer Resources
- WordPress Block Editor WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


