How to Duplicate a Page in WordPress Without Breaking the Layout or SEO

Duplicating a WordPress page sounds like one of those jobs that should have a single button.

Sometimes it does. Sometimes it doesn’t.

The right method depends on what you actually want to copy.

If I only need the Gutenberg layout, copying the blocks may be enough. If I need the page content, featured image, template, custom fields and plugin settings, I would use a proper cloning tool instead.

And if I’m creating several pages that share the same structure, I may not duplicate a page at all. A WordPress pattern is often a cleaner solution.

So in this guide, I’ll show the practical ways to duplicate a page in WordPress, explain what each method actually copies, and cover the things I check before publishing the duplicated page.

First: What Do You Mean by “Duplicate a Page”?

This is the part that causes most confusion.

A WordPress page is more than the visible text and blocks.

Depending on the site, a page can also contain:

• title
• block content
• featured image
• excerpt
• parent page
• page template
• custom fields
• SEO metadata
• page-builder data
• plugin-specific settings

Copying the visible editor content and cloning the whole WordPress post object are therefore two different operations.

Copy blocks
    |
    +-- page content/layout


Clone page
    |
    +-- content
    +-- page properties
    +-- selected metadata
    +-- possibly plugin settings

I decide which one I need before choosing the method.

Quick Answer: Which Method Should You Use?

What you need	Method I would use
Copy only Gutenberg content	Copy all content
Copy a few blocks	Block copy or duplicate
Copy a complete page with settings	Duplicate-page plugin
Create many pages with the same layout	Unsynced pattern
Reuse identical content everywhere	Synced pattern
Make major changes to an existing published page	Revision/staging or rewrite workflow rather than a random duplicate

Method 1: Copy the Page Content with the Block Editor

If I’m using Gutenberg and only need the page’s blocks, this is usually the quickest option.

Open the existing page in the WordPress editor.

Then open the three-dot menu in the top-right corner.

Under the editor tools, choose:

Copy all content

Now create a new page and paste the content into the editor.

Pages
  ↓
Add New
  ↓
Paste
  ↓
Save Draft

This copies the Gutenberg block content, including the block structure and most block-level settings.

What it does not mean is that WordPress has cloned the entire page.

I still check things such as:

• featured image
• URL slug
• page parent
• template
• SEO title and description
• custom fields
• plugin-specific page settings

For a normal Gutenberg landing page, that may be perfectly fine.

For a complex page with a lot of metadata, I would use a real cloning method instead.

You Can Also Copy Only Part of a Page

Sometimes duplicating the entire page is unnecessary.

Maybe I only need a hero section, pricing section or call-to-action.

In the block editor, I can select a block or group of blocks and copy them to another page.

WordPress also provides a shortcut for duplicating selected blocks:

Windows:
Ctrl + Shift + D

Mac:
Command + Shift + D

The duplicated block appears directly below the original.

For more complicated layouts, I often use List View because nested Groups, Columns and Cover blocks are easier to select correctly there.

Method 2: Clone the Full Page with a Plugin

If I need a true page clone, using a mature plugin is normally easier than trying to rebuild WordPress’s post metadata manually.

One established option is Yoast Duplicate Post.

After installing and activating it, go to:

Pages
  ↓
All Pages

Hover over the page you want to duplicate.

Depending on the plugin configuration, you’ll see options such as:

• Clone
• New Draft
• Rewrite & Republish

Clone

This is useful when I simply want another copy created and don’t need to open it immediately.

New Draft

This is the option I often prefer when creating a new page based on an existing one.

It creates the copy and takes me directly into the new draft so I can immediately change the title, URL and content.

Rewrite & Republish

This solves a different problem.

If I need to make substantial changes to an existing published article or page without editing the public version immediately, a rewrite-and-republish workflow can be cleaner than creating a second permanent URL.

Check the Plugin Settings Before Cloning Important Pages

I don’t assume every field will be copied exactly the way I want.

Duplication plugins normally have settings controlling what should be copied.

Before using one on an important site, I check whether I need to duplicate:

• featured image
• excerpt
• page template
• custom fields
• taxonomies
• menu order
• plugin metadata

This becomes particularly important on sites using custom fields, WooCommerce extensions, page builders or SEO plugins.

I would test the duplication workflow on one draft before assuming it behaves correctly across the entire site.

Method 3: Use a Pattern Instead of Duplicating Pages

This is the method I think is overlooked most often.

If I’m repeatedly creating pages with the same design, I don’t necessarily want to clone an old page every time.

For example, suppose every service page needs this structure:

Hero
   ↓
Service introduction
   ↓
Three benefits
   ↓
Process
   ↓
Testimonials
   ↓
FAQ
   ↓
Call to action

Instead of duplicating the previous service page and then trying to remember which old content needs replacing, I can save that structure as a WordPress pattern.

Select the blocks that make up the layout, open the block options and choose:

Create pattern

Give it a useful name, for example:

Service Page Layout

Now it can be inserted into new pages without starting from the previous page’s content.

For repeated layouts, I often find that cleaner than cloning pages indefinitely.

Synced vs Unsynced Patterns: Don’t Mix These Up

This difference matters.

Unsynced Pattern

When you insert it, you get an independent copy of those blocks.

Pattern
   |
   +--- Page A → independent blocks
   |
   +--- Page B → independent blocks
   |
   +--- Page C → independent blocks

This is what I want for something like a service-page layout where every page starts with the same structure but gets different content.

Synced Pattern

A synced pattern is different.

Synced pattern
       |
       +---- Page A
       |
       +---- Page B
       |
       +---- Page C

Edit pattern once
       |
       v
All uses update

This is useful for content that should really stay identical everywhere, such as:

• contact information
• business hours
• a standard call-to-action
• legal or disclosure text
• repeated promotional content

I would not use a synced pattern as a page template if every page is supposed to contain different text.

Otherwise editing one page may unexpectedly update the same synced content somewhere else.

Method 4: Duplicate a Page Manually When You Don’t Want Another Plugin

If I only need to do this once, I wouldn’t necessarily install another plugin.

For a Gutenberg page, my manual workflow is:

1. Open the original page.
2. Use Copy all content.
3. Create a new page.
4. Paste the blocks.
5. Copy or recreate the featured image if required.
6. Select the correct template.
7. Set the correct parent page.
8. Configure the SEO metadata.
9. Check any custom fields.
10. Preview the page before publishing.

That is enough for many straightforward pages.

Where I stop doing this manually is when a page has a large amount of custom metadata. At that point a tested cloning workflow is less error-prone.

Duplicating a Page Is Not a Backup Strategy

The old version of this article described duplication as a safety net before changing an existing page.

I wouldn’t rely on it as my backup strategy.

WordPress already has a revision system for saved page and post changes.

If I edit a page and need to return to an earlier saved version, I can inspect its revisions and restore an earlier state.

Edit Page
   |
   v
Settings
   |
   v
Revisions
   |
   v
Choose previous version
   |
   v
Restore

For high-risk changes, I prefer proper site backups and a staging environment.

A duplicate draft may be useful during editing, but it is not a replacement for backing up the database and files before a major site change.

The SEO Problem with Duplicated Pages

Creating the draft isn’t the SEO problem.

Publishing two almost identical pages can be.

Suppose I clone this:

/web-development/

and publish the copy as:

/professional-web-development/

If I only change the heading while 95% of the page remains identical, I’ve probably created a page that adds very little value.

Before publishing a duplicated page, I make sure it has a genuine reason to exist.

That normally means reviewing:

• page purpose
• main heading
• body content
• URL slug
• SEO title
• meta description
• internal links
• images and alt text
• structured data where relevant

Duplicating the layout is fine.

Duplicating the value of the page is where I become much more careful.

Change the URL Before Publishing

This is one of the first things I check.

If the original page is:

/wordpress-development/

the duplicated page should not accidentally become something like:

/wordpress-development-2/

unless that URL genuinely makes sense.

I set the final page title and slug before publishing so the URL reflects the new page’s purpose.

Check the SEO Metadata Too

If the duplication method copies custom fields, it may also copy SEO-plugin metadata.

That can include things such as:

• SEO title
• meta description
• focus keyword
• social title
• social description
• schema settings
• canonical configuration

I never assume those values are correct simply because the visible page content has been changed.

Before publishing, I open the SEO settings and review them as if I were creating a new page.

Check Links That Point Back to the Original Page

This is an easy mistake to miss.

Imagine I duplicate a service page containing buttons such as:

Learn more

Book this service

View pricing

The layout may look perfect, but those links may still point to URLs related to the original service.

I check:

• buttons
• text links
• image links
• form redirects
• anchor links
• download links

Visual similarity makes these old references particularly easy to overlook.

Check Forms Carefully

Forms deserve their own check.

If a duplicated page contains a contact, booking or checkout form, I verify:

• which form is embedded
• notification recipients
• confirmation behaviour
• redirect URLs
• hidden fields
• tracking values

I don’t assume a cloned page needs a cloned form.

Sometimes both pages should submit to the same form. Sometimes they need separate tracking or entirely different workflows.

Don’t Forget Mobile Layouts

Duplicating a page can preserve layout, but replacing content can still break the design.

A heading that was two lines may become five.

A replacement image may have a different aspect ratio.

A button label may become much longer.

So I preview the new page on:

• desktop
• tablet
• mobile

A copied layout is a starting point, not proof that the new content still fits it.

What About Page Builders?

If a site uses a page builder, I become more cautious about the manual copy-and-paste method.

Page builders can store important configuration outside the normal post content.

For those sites, I first check whether the builder provides its own template or duplication workflow.

If I use a general duplication plugin, I test the cloned draft before publishing and make sure the builder data, responsive settings and custom fields came across correctly.

This is one situation where “the page looks copied in the WordPress editor” isn’t enough for me.

When I Would Use a Pattern Instead of a Plugin

For me, the decision is usually about whether I am copying content or copying a design system.

Situation	My choice
I need one exact copy of a complex page	Duplication plugin
I only need the Gutenberg blocks once	Copy all content
I repeatedly build the same type of page	Unsynced pattern
The content must stay identical everywhere	Synced pattern
I only need one section	Copy blocks or pattern

If I find myself cloning the same old page twenty times, that is usually a sign that I should create a reusable pattern instead.

My Checklist Before Publishing a Duplicated Page

I run through this list before pressing Publish:

• Change the page title.
• Set the correct URL slug.
• Replace old content rather than only changing a few words.
• Check the featured image.
• Check the page template.
• Check the parent page.
• Review SEO title and description.
• Check canonical and schema settings where relevant.
• Update internal links.
• Check buttons and calls to action.
• Check embedded forms.
• Check custom fields.
• Preview desktop and mobile layouts.
• Make sure the page adds genuinely different value before indexing it.

Common Mistakes I Avoid

Publishing Before Changing the Slug

I prefer setting the intended title and URL while the duplicate is still a draft.

Leaving the Old SEO Description

The visible content may be new while the metadata still describes the old page.

Assuming Everything Was Copied

Different cloning methods copy different data. I check instead of assuming.

Publishing Two Near-Identical Pages

A duplicated layout is useful. A duplicated page with almost no new value usually isn’t.

Using Synced Patterns When I Need Independent Content

If the inserted sections are meant to change independently, I use an unsynced pattern or detach the synced pattern first.

Treating a Duplicate as a Backup

For recovery, I rely on revisions, proper backups and staging—not an extra page draft sitting in WordPress.

Which Method Do I Usually Prefer?

For one simple Gutenberg page, I usually wouldn’t install a plugin. Copying the blocks is enough.

For a complicated page where I need the settings and metadata to come with it, I would use a tested duplication plugin.

And if I’m creating the same type of page repeatedly, I stop cloning old pages and build a pattern instead.

That last option tends to keep sites cleaner because every new page starts with the intended structure rather than carrying years of forgotten links, settings and old content forward.

Final Thoughts

WordPress makes it easy to reuse content, but there isn’t one duplication method that is correct for every situation.

If I only need the blocks, I copy the blocks.

If I need a full clone, I use a cloning tool.

If I need the same design repeatedly, I create a pattern.

More importantly, I treat the duplicated page as a starting point rather than a finished page.

I still review the URL, content, metadata, links, forms, images and mobile layout before publishing it.

Duplicating the layout should save time. It shouldn’t duplicate old mistakes along with it.