How to Convert a WordPress Post to a Page (and Back) in 2026

There is no "convert to page" button in WordPress. People dig through the editor looking for one, and it is simply not there.

That is because a post and a page are two different content types under the hood.

But changing one into the other is a two-second job once you know the trick. I do it on client sites whenever a blog post grows into something that should really be a standalone page: an about, a service, a landing page.

Here are the three methods that work, from the one-click plugin most people want to the developer's one-liner. They all go both ways, so turning a page back into a post is the same job in reverse.

When should you convert a post to a page?

A post is dated, sits in your blog feed, and carries categories and tags. A page is timeless and standalone. So you convert when a piece stops being "news" and becomes a fixed part of the site.

Common cases I run into:

• A blog post that has turned into your real services or about content.
• A "resource" post you now want out of the blog feed and linked from the menu.
• The reverse: a page that should actually live in the blog and collect comments, so you turn it back into a post.

If the content needs a publish date and belongs in the feed, keep it a post. If it is evergreen and standalone, make it a page.

Method 1: the Post Type Switcher plugin (easiest)

This is the answer for almost everyone. Post Type Switcher by John James Jacoby is a free, lightweight plugin with over 200,000 active installs, made by a long-time WordPress core contributor. It adds the one control WordPress forgot.

Install it from Plugins → Add Plugin, search "Post Type Switcher", install and activate.

Once it is active, open the post you want to convert. In the editor's right sidebar, under the Post tab, you will see a new Post Type row at the bottom. Click it and pick Page.

Then click Save (or Update). The post is now a page, with the same content, featured image, custom fields and comments intact.

Only one thing changed in the database: the post_type value. Nothing else moves.

Converting several at once

If you have a batch to move, you do not open them one by one. On Posts → All Posts, the plugin adds a Post Type dropdown to Quick Edit, and to Bulk Edit when you select several posts at once.

Method 2: copy all blocks (no plugin)

If you cannot or will not install a plugin, you can move the content by hand. This is more work and it does not carry your metadata, but it needs nothing extra.

1. Open the post in the block editor.
2. Click the three-dot menu (top right) and choose Copy all blocks.
3. Create a new page (Pages → Add Page) and paste. Everything pastes in as proper blocks.
4. Set the featured image, and re-enter any SEO title and description, because those do not come across.
5. Delete or unpublish the old post, and add a 301 redirect from its URL to the new page.

The catch is real: this creates a brand-new page with a new ID, so the original post's comments, custom fields and SEO metadata stay behind.

Use it only when a plugin is genuinely off the table.

Method 3: WP-CLI (for developers)

If you have terminal access, this is the fastest method of all, and it keeps everything like the plugin does. WP-CLI changes the post type in place:

# convert a single post (ID 123) to a page
wp post update 123 --post_type=page

# convert every post to a page in one go
wp post list --post_type=post --format=ids | xargs wp post update --post_type=page

Swap page for post to go the other way. It is instant and touches only the post_type field, exactly what the plugin does, just without the UI.

One caution: the second command converts every post in one shot. Take a database backup before you run a bulk change, so a wrong flag is a restore, not a disaster.

Which method should you use?

For nine sites out of ten, the plugin is the right call. WP-CLI wins only if you are already in the terminal, and copy-blocks is the fallback when you are locked out of plugins.

What happens after you convert?

Most things carry over cleanly. One does not, and it is the one that matters for SEO.

That last row is the one people forget. When the post becomes a page, its URL changes, so the old address stops working. Set up a 301 redirect from the old post URL to the new page so visitors and search engines follow it across. Skip that and you 404 the old URL and throw away its ranking.

If you are curious why the conversion is so clean under the hood, it is because posts and pages live in the same database table and differ only by their post_type value. Changing that one field is all a conversion really is.

Final take

WordPress hides this behind its post-versus-page split, but the fix is simple. Install Post Type Switcher, open the post, switch the Post Type to Page, and update. It keeps your content and works in both directions.

Whichever method you pick, do not forget the 301 redirect afterwards. The conversion itself is a two-second job; protecting the URL it used to live at is the part that keeps your SEO intact.