Duplicate Page plugin review and common issues

The Duplicate This link appears in the post row actions (revealed on hover). If missing: (1) verify Duplicate Page is active in WordPress → Plugins; (2) check Settings → Duplicate Page to verify the plugin settings are saved; (3) try a different browser or clear browser cache; (4) a custom admin screen may suppress the standard WordPress post row actions — test with a default theme/no page builder active; (5) verify the current user has the edit permissions for the post type — users without edit permissions do not see the Duplicate This link.

Duplicate Page copies standard post meta fields but WooCommerce product gallery images use a specific meta key (_product_image_gallery) that stores attachment IDs. Check: (1) in the duplicate product, go to Product Data → Product Gallery and verify if the IDs are present (they should be copied); (2) if gallery is empty, WooCommerce’s product gallery may use a meta key not captured by basic post meta copying; (3) for more complete WooCommerce product duplication, use the WooCommerce built-in “Duplicate” product feature (available in WooCommerce product list natively) or a WooCommerce-specific duplicate plugin.

Duplicates are saved as drafts by default. In the Pages list, drafts may not appear if the list is filtered to show only Published pages. Check: (1) in Pages list, look for a draft status filter at the top and select “Drafts”; (2) or change the filter to “All” to see all post statuses; (3) in Settings → Duplicate Page, you can change the default duplicate status — if set to “Publish,” the duplicate appears in the main list immediately; (4) if the duplicate is not in any status, check if a redirect plugin or caching issue is preventing the save action from completing.

Go to Settings → Duplicate Page in the WordPress admin. Find the “Post Status” setting and change from “Draft” to “Pending.” Save. All future duplicates will be created with Pending status, appearing in the Pending queue for editorial review before publication. This is useful for editorial workflows where duplicated content must be reviewed and edited before going live, and editors want to distinguish newly duplicated content from existing drafts.

Duplicate Page automatically adds a “Duplicate” option to the Gutenberg editor. Look in the top toolbar → the three-dot “Options” menu (⋮) at the top right corner of the Gutenberg editor. “Duplicate” should appear in this dropdown menu. Clicking it creates a duplicate and redirects to the new duplicate post for editing. If the option does not appear, verify Duplicate Page is active and try refreshing the editor page.

Yoast’s Duplicate Post (now called “Yoast Duplicate Post”) offers more features including a “Rewrite & Republish” workflow that allows editing a live page as a draft and publishing the edited version to replace the original. Duplicate Page is simpler and more widely installed (5 million vs ~4 million). For straightforward content cloning, both work well. For the specific “edit a published post’s draft version before replacing” workflow, Yoast’s Rewrite & Republish feature is a unique capability worth considering.

Yes — Duplicate Page copies all post meta, which includes Elementor’s and Divi’s page builder data stored in post_content and post meta fields. The duplicated post should retain the complete page builder layout. After duplication, open the Elementor or Divi editor to verify the layout is intact and edit as needed. For page builders that store data in custom database tables (some older builders), the duplication may be incomplete — test with your specific page builder.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.