How to Duplicate a Page in WordPress in 2026: 3 Methods That Actually Work

To duplicate a page in WordPress, install Yoast Duplicate Post (the only major maintained plugin in 2026), hover over the page in Pages → All Pages, and click Clone or New Draft. According to WordPress.org plugin directory stats, Yoast Duplicate Post has over 5 million active installations, making it the de facto standard. The other […]

Tarun Sharma
Tarun Sharma Founder, Chetaru
|
Updated May 25, 2026
|
7 min read
Share

Need More Growth & Leads?

We are ready to work with your business and generate some real results…

Let's Talk

To duplicate a page in WordPress, install Yoast Duplicate Post (the only major maintained plugin in 2026), hover over the page in Pages → All Pages, and click Clone or New Draft. According to WordPress.org plugin directory stats, Yoast Duplicate Post has over 5 million active installations, making it the de facto standard. The other historical options have either been abandoned or merged into this one.

Key Takeaways: In 2026, use Yoast Duplicate Post (5M+ active installs) or duplicate natively via the block editor’s Copy and Paste Block workflow. The two-line WP-CLI command wp post create --post_type=page plus duplicating via SQL also work for automation and recovery cases. Avoid abandoned plugins like Duplicate Page and Post or WP Page Post Clone that have not been updated in 2+ years. Block themes (Twenty Twenty-Four onwards) also let you save a page as a Pattern and reuse it without traditional duplication.

Why duplicate a page in WordPress in the first place?

The honest reasons to duplicate a page are narrower than most marketing posts admit. Four legitimate cases:

  • Building a page template for repeated use. Service-page layouts, location pages, product variations. Duplicating a known-good page is faster than rebuilding the same blocks.
  • Creating a staging copy to edit before publishing. Useful when WordPress’s built-in revisions are too coarse and a parallel-page workflow is cleaner.
  • A/B testing two versions of a landing page. Duplicate the page, change one variable, route traffic with a plugin like Nelio AB Testing or Google Optimize successor tools.
  • Backing up a page before major surgery. A defensive copy in case a rebuild goes wrong. Less needed if the site already runs full database backups, but useful for single-page work.

The cases not to duplicate: publishing two nearly identical pages publicly (this creates duplicate content issues that hurt SEO), creating localised variants (multilingual plugins handle this properly), or copying content from another site (a copyright problem, not a WordPress problem).

How do you duplicate a page using Yoast Duplicate Post?

Yoast Duplicate Post is the only major plugin in this space still actively maintained in 2026. The original Duplicate Post plugin was acquired by Yoast in 2020 and continues to receive security and compatibility updates. Other historical options have been abandoned or are unmaintained.

The five-step install and use process:

  1. Go to Plugins → Add New in the WordPress dashboard.
  2. Search for “Yoast Duplicate Post”. Confirm the author is Yoast.
  3. Click Install Now, then Activate.
  4. Go to Pages → All Pages. Hover over the page you want to duplicate. Two new options appear: Clone (creates an immediate duplicate) and New Draft (creates a duplicate and opens the editor).
  5. Edit the duplicate as needed, then publish or save as draft.

Yoast Duplicate Post adds settings under Settings → Duplicate Post that control:

  • Which fields are copied (title, content, excerpt, featured image, categories, tags, custom fields).
  • The prefix and suffix added to the duplicate’s title (default: “(Copy)”).
  • Which user roles can duplicate pages (administrator only by default).
  • Whether the duplicate is created as draft, private, or pending review.

Two settings worth changing on most sites:

  • Prefix. Default is blank with a “(Copy)” suffix. Most teams find a “[Draft]” prefix more useful for filtering.
  • Replace at end of edit. Off by default. Enabling this turns “Rewrite & Republish” into a feature that publishes the duplicate over the original. Useful for major page rewrites; risky if accidentally enabled.

The plugin works with classic editor, block editor, and most page builders (Elementor, Beaver Builder, Divi). Compatibility issues are rare in 2026.

How do you duplicate a page natively in the block editor without a plugin?

The block editor’s Copy all blocks function plus Paste into a new page produces a clean duplicate without any plugin. The five-step manual route:

  1. Open the source page in the block editor (Pages → All Pages → click page).
  2. Click the options menu (three vertical dots at the top right) and choose Copy all blocks.
  3. Go to Pages → Add New to create a fresh page.
  4. Click into the content area and paste (Cmd/Ctrl + V). All blocks transfer with formatting.
  5. Set the title, permalink, featured image, and category as needed.

What this method copies and does not copy:

  • Copies: all blocks, including text, images, embeds, columns, custom blocks.
  • Does not copy: page settings (template, parent, order), SEO meta (title, description), Yoast/RankMath data, featured image, categories, custom fields.

For pages that depend on metadata, custom fields, or specific page settings, the plugin route is faster. For pages that are mostly block content, the native method is cleaner and avoids adding a plugin dependency.

How do you duplicate a page via WP-CLI for developers and automation?

WP-CLI supports duplicating pages with two commands that read the source and create a new post. Useful for deployment scripts, migration tooling, and recovery scenarios.

The minimal WP-CLI duplicate workflow:

SOURCE_ID=42
wp post get $SOURCE_ID --field=post_content > /tmp/page-content.txt
NEW_ID=$(wp post create --post_type=page --post_status=draft --post_title="Copy of Page" --porcelain < /tmp/page-content.txt)
echo "New page ID: $NEW_ID"

Replace 42 with the source page ID. The new page is created as a draft for review before publishing.

For more comprehensive duplication, WP-CLI’s wp post duplicate command (via the wp-cli-wp-cli/post-command package) copies post meta, taxonomies, and featured image in one step.

When WP-CLI duplication makes sense:

  • Bulk operations. Duplicating dozens of pages for a multi-location rollout.
  • Migration scripts. Cloning content during a site rebuild.
  • CI/CD pipelines. Building staging-to-production deployment scripts.

For a one-off duplication, WP-CLI is overkill. For automation, it is the right tool.

What about block themes and Patterns: do they change the duplication picture?

WordPress 6.4+ block themes introduced Patterns, which are reusable block layouts. Patterns reduce the need for traditional page duplication when the goal is reusing a layout, not the entire page.

The Patterns workflow that replaces some duplication use cases:

  1. Build a layout once (a hero section, a service-list, a comparison table).
  2. Select the blocks, click Create Pattern (Site Editor or Block Editor).
  3. Insert the Pattern on any page via the inserter.

When Patterns beat traditional duplication:

  • Multiple pages share a layout but not the content. Patterns produce one canonical layout that can be edited centrally.
  • Layouts evolve over time. Editing the Pattern updates everywhere it is used (with synced Patterns), which traditional duplication cannot do.
  • Building a design system. Patterns scale to teams; duplicated pages do not.

When traditional duplication still wins:

  • The whole page (content + layout) needs cloning. Patterns are layout-only.
  • A/B testing two whole pages. Patterns assume one canonical layout.
  • One-off staging copies. Setting up a Pattern is overkill for a single edit.

Patterns are the right tool for systematic reuse; duplication is the right tool for one-off copies. Most sites benefit from using both for different jobs.

How do you avoid the SEO problems duplicated pages create?

The SEO concern with duplication is publishing two indexable copies of the same content. Google’s duplicate content documentation explains that Google picks one canonical version and may ignore the other for ranking. Three practices that avoid the problem:

  • Keep duplicates as drafts or private until ready. Drafts and private pages are not indexed. Most legitimate duplication use cases (templates, A/B tests, edits) do not need both versions public.
  • Use a canonical tag if both versions must exist. Set the canonical URL of the duplicate to the original. Yoast SEO and Rank Math both expose canonical settings.
  • Noindex the duplicate if it is intentionally public but should not rank. A “thank you” page, a print version, or an A/B test variant that should not be indexed.

Avoid: publishing two near-identical pages with different URLs and no canonical signal. Google will pick one to rank and may rank neither for competitive queries.

What plugins should you not use in 2026?

Several historical “duplicate a page in WordPress” plugins have been abandoned or are functionally dead in 2026. Avoid these:

Plugin Status Why to avoid
Post Duplicator Updated rarely Lightweight alternative but Yoast Duplicate Post does the same job better
Duplicate Page and Post Abandoned Last updated more than 2 years ago; potential security and compatibility risk
WP Page Post Clone Abandoned Not maintained; broken on recent WordPress versions
Page and Post Clone Abandoned Same as above

The honest 2026 picture: the duplicate-a-page-in-WordPress plugin market consolidated when Yoast acquired the original Duplicate Post. The other plugins listed in older blog posts are mostly historical recommendations that have not been re-evaluated. Default to Yoast Duplicate Post unless there is a specific reason not to.

Frequently asked questions

Not directly. WordPress core does not include a “Duplicate” button in the page editor or list. The block editor’s Copy all blocks feature is the closest native equivalent. For full duplication including metadata, a plugin like Yoast Duplicate Post is still required.

What this means in practice

In 2026, duplicating a page in WordPress is solved by Yoast Duplicate Post for most users, by the block editor’s Copy all blocks function for plugin-free workflows, and by WP-CLI for developers and automation. Block-theme Patterns cover the related “reuse a layout” use case without traditional duplication. Avoid abandoned plugins from older recommendations. And keep duplicate pages non-public until they are ready, both for the cleaner workflow and to avoid the SEO problems indexed duplicates create.

For related reading, see our guides on how to set the homepage in WordPress, which SEO plugin is best for WordPress, and our custom WordPress design and development service.