Duplicate Posts and Pages in WordPress (Page Builders Too)

Clone a WordPress post or page with custom fields, taxonomies and builder layout intact—one click or in bulk, saved as a draft so nothing goes live.

The first time I needed ten near-identical landing pages, I did it the manual way: build one, then copy the Elementor layout into the next, and the next. Two pages in, a meta field didn’t carry across and the third opened as a blank white canvas in the builder. Duplicating content in WordPress looks trivial and absolutely isn’t—because a post is far more than the text you see. Here’s how to clone anything, layout and all, in one click.

The essentials

  • Core WordPress has no built-in duplicate button—you need a tool for it.
  • The Content Duplicator clones content, custom fields, taxonomies, template, menu order and hierarchy in one click.
  • Elementor and Beaver Builder layouts survive because it copies the post-meta rows directly at the database level, exactly as stored; Divi’s layout lives in the content and is copied with it.
  • Copies are made as a draft by default, so nothing goes live by accident.
  • Duplicate from the posts list or in bulk, and even duplicate taxonomy terms (categories, tags, custom)—the copy is an empty term with the same description and parent.

Why is duplicating WordPress content harder than it looks?

Because a WordPress post is far more than its title and body: it carries custom fields (post meta), categories and tags, a parent, a menu order and a template, and page builders such as Elementor store the whole layout in those custom fields. Copy the text alone and the builder opens an empty page.

Underneath, a post carries:

  • Custom fields (post meta) — often dozens of them, especially with a page builder or ACF.
  • Taxonomies — categories, tags and any custom taxonomies.
  • A parent-child hierarchy and menu order — particularly for pages.
  • A page template assignment.
  • Optionally comments and other attached data.

Page builders like Elementor and Beaver Builder store their entire layout inside post meta; Divi stores its layout as shortcodes in the post content itself. If those meta rows aren’t copied exactly as stored—Elementor’s layout is a long JSON string full of backslashes—the “copy” opens as an empty page in the builder. That single detail is why a naive copy-paste, or a duplicator that writes the meta through functions that strip those backslashes, fails.

How do you duplicate a post or page in WordPress?

Core WordPress has no duplicate button, so you add one: activate the Content Duplicator module in Blaminhor Essentials and a one-click Duplicate action appears in your posts and pages lists, in the bulk-actions menu and in taxonomy lists. It clones the whole post—content, custom fields, taxonomies, template and page-builder layout—straight to a draft. That action shows up everywhere you actually work:

  • In the posts and pages list, next to Edit, Trash and View.
  • In the bulk-actions menu, to clone several items at once.
  • In the taxonomy list, to duplicate a category, tag or custom term.

Click it, and the module builds a complete clone.

Illustration: a 3D WordPress page being duplicated, the copy carrying the same layout and fields as the original. Pick what’s duplicable and how copies are labelled once—then it’s a single click from every list afterward.

What exactly gets copied?

With the default settings, the copy carries the content and excerpt, every custom field except a handful (edit locks, the WooCommerce SKU, the canonical URL and builder-generated CSS), all categories, tags and custom taxonomies, the template, menu order and parent—and, for a WooCommerce product, its variations. Child posts and comments are optional and off by default.

In detail:

  • All content and the excerpt.
  • Every custom field except internal locks, the SKU, the canonical URL and builder-generated CSS (which is regenerated), read straight from wp_postmeta and re-inserted at the database level so the encoding is preserved exactly—this is what keeps page-builder layouts working.
  • All taxonomies — categories, tags and custom taxonomies.
  • Template, menu order and hierarchy.
  • Page-builder data — Elementor, Beaver Builder, Brizy and anything else that lives in post meta, because the meta is copied wholesale; Divi’s shortcode layout travels with the content.
  • Not the media files themselves — images and attachments are not cloned; the copy points to the same files as the original, so deleting a copy never removes an image the original still uses.

Two things are optional and off by default, because they’re not always what you want: copying the post’s child posts (for hierarchical content) and copying its comments. Turn either on in the settings when you need it.

At a glance, here’s what a clone carries over:

ElementCopied when you duplicate?
Content and excerptYes, always
Custom fields (post meta)Yes, by default—copied at database level, encoding intact (internal locks, SKU and builder CSS excepted)
Taxonomies (categories, tags, custom)Yes, by default
Template, menu order, hierarchyYes, by default
Page-builder layout (Elementor, Beaver Builder, Divi)Yes—meta copied wholesale; Divi’s layout comes with the content
WooCommerce product variationsYes, always, for products
Attached media filesNot duplicated—the copy references the same files
Child posts (hierarchical content)Optional—off by default
CommentsOptional—off by default

Can you make the duplicate behave the way you want?

Yes. The Content Duplicator settings let you choose the default status of a copy (draft out of the box), a title prefix or suffix (” - copy” by default), whether the copy keeps the original’s date and author, which post types and taxonomies can be duplicated, and whether child posts and comments come along. In detail:

  • Default status of new copies — draft out of the box, so nothing publishes by accident. Change it to published or private if that fits your flow.
  • Title suffix / prefix — copies get ” - copy” appended by default, so you never confuse a clone with the original in a list.
  • Date and author — by default a copy takes the current date (not the original’s) and keeps the author; both are configurable.
  • Eligible post types and taxonomies — decide exactly what can be duplicated, custom post types included.

What does the copy look like?

A genuine second post, ready to edit, with its layout, fields and taxonomies intact—no blank builder page, no missing meta. Two deliberate differences: a WooCommerce SKU is left empty (it must stay unique) and a canonical URL is not copied (it would send search engines back to the original). Media files aren’t cloned either; the copy uses the same images. What was an afternoon of rebuilding becomes a click.

If you’re duplicating pages to organise a lot of content, you’ll probably want to arrange it afterward too—reordering posts and pages by drag-and-drop pairs naturally with this.

Content Duplicator is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.

Download Blaminhor Essentials

– blaminhor

FAQ

Will duplicating a page keep my Elementor or Divi layout?

Yes. Elementor and Beaver Builder store their layout in post meta, and the Content Duplicator copies those meta rows directly at the database level, exactly as stored—only a few internal keys, the WooCommerce SKU, the canonical URL and the builder's generated CSS are left out, and that CSS is rebuilt for the copy. Divi keeps its layout as shortcodes in the content itself, which is copied too. The copy opens in the builder as the original did, not as a blank canvas.

How do I duplicate a WordPress page without a plugin?

You copy it by hand: open the original, switch to the code view, paste the content into a fresh page, then manually reassign the template, parent, menu order and custom fields. It's slow and page-builder layouts rarely survive the trip, which is exactly why a one-click duplicator earns its place.

Can I duplicate several posts at once in WordPress?

Yes. The Content Duplicator adds a Duplicate option to the bulk-actions menu in any enabled post type, so you select multiple posts, choose Duplicate and clone them all in one operation. It can also duplicate a taxonomy term—category, tag or custom term—from its own list: the copy gets the same description, parent and term meta, but no posts are assigned to it.

Is a duplicated post published immediately?

No, and that's deliberate. By default the copy is created as a draft with the current date, so nothing goes live by accident and you won't publish a half-edited clone. You can change the default status, title suffix and date behaviour in the module's settings if you prefer.

Does duplicating a page cause duplicate-content SEO problems?

Not by itself. Copies are created as drafts, so search engines never see them and there's nothing to penalise. The risk only appears if you publish two near-identical pages live—so edit and differentiate the clone, or set a canonical URL, before you hit publish on the copy.

Can I duplicate a WooCommerce product?

Yes. A WooCommerce product is a custom post type, and products are enabled by default in the Content Duplicator's post-type list, so the Duplicate action clones it like any post—price, attributes, gallery, variations and custom fields included (the SKU is left empty, since it must stay unique)—as a safe draft you can rename and adjust before putting it on sale.

blaminhor Building what's missing.

Comments