SleekView for Yoast Duplicate Post
SleekView reads the _dp_original and _dp_is_rewrite_republish_copy meta keys Yoast Duplicate Post writes and resolves source posts in line, so every clone becomes one row in a real audit table.
♾️ Lifetime License available
Duplicate Post is fast. The cleanup is the hard part.
Yoast Duplicate Post is one of the most installed plugins in the WordPress directory, and for good reason: cloning a post for a new variant, a localisation or a rewrite-and-republish flow is a daily editorial task. The plugin handles the clone cleanly, but the resulting drafts mix straight back into the standard Posts list with no marker, no source reference and no easy way to filter them.
SleekView reads the _dp_original meta that the plugin writes on every clone and resolves the source post in line. Each clone becomes a row with clone title, source title, author, cloned date, status and a tag for whether the clone is part of a rewrite-and-republish. Filter to clones in draft for more than ninety days to identify abandoned variants. Filter to author equals an outgoing editor to inherit their open clone work cleanly. Sort by source to see how many drafts have spawned from a single canonical post.
Inline edits flow through the standard WordPress save path, the same way Yoast Duplicate Post expects. Bulk trash actions respect capability checks and the WordPress trash. The result is the audit view that turns a fast-cloning workflow into something that does not silently accumulate drafts.
Workflow
Turn cloned drafts into a real audit table
Detect clones
Resolve the source
Filter abandoned
Bulk cleanup
Sample columns
Duplicate audit
wp_postmeta
| Clone | Source | Author | Cloned | Status | State |
|---|---|---|---|---|---|
| Homepage v2 | Homepage | Anna | 2026-04-22 | Draft | Active |
| Pricing Test | Pricing | Marc | 2025-11-04 | Draft | Stale |
| Old Newsletter | Newsletter Q1 | Lina | 2024-02-01 | Trash | Abandoned |
| Holiday Banner v2 | Holiday Banner | Anna | 2026-04-23 | Pending | Active |
Comparison
Default Posts screen vs SleekView
Default Posts screen
- Cloned posts mix with originals in the default list
- No filter for posts created via duplicate
- Source post is not shown in the list table
- Bulk cleanup of stale clones is not exposed
- Rewrite-and-republish status is invisible from the list
SleekView
- Detects clones via the _dp_original meta key
- Joins each clone with its source post in the same row
- Filter by status, author and clone date
- Inline edit status, slug and author
- Bulk trash stale clones safely with one action
Features
What SleekView gives you for Yoast Duplicate Post
Clone audit
Every post that started as a clone in one table with its source resolved, current status and a tag for rewrite-and-republish copies.
Find stale drafts
Filter to clones in draft for more than ninety days and decide whether to keep, finish or trash them, instead of letting the pile grow quietly.
Bulk cleanup
Multi-select abandoned clones and trash them with the same capability checks the default admin uses, leaving sources untouched and trash recoverable.
Audience
What teams use SleekView for
Site audits
Group clones by author and status to spot patterns of unfinished work, useful when planning an editorial cleanup sprint or onboarding a new editor.
Rewrite and republish queues
Filter to clones tagged as rewrite-and-republish to manage the workflow as a real queue with submitted dates and assigned editors visible.
Editor handoffs
Filter by an outgoing editor's authorship and inherit their open clone work cleanly, so unfinished variants do not get orphaned when access is revoked.
The bigger picture
Why fast cloning needs an audit habit
Yoast Duplicate Post is so easy to use that teams reach for it constantly: a marketer clones a campaign page for a new region, a writer clones an article to draft a follow-up, an editor clones a product post for a copy refresh. The plugin does its job perfectly each time, and the cumulative effect is a draft pile that nobody owns. After a year of clones-as-a-habit, a typical site carries dozens of stale drafts that started as good ideas and never shipped.
The cost is real: cluttered editor lists, slow autosave on heavy postmeta tables, accidental publishes from the wrong draft, confusion about which version is canonical. A clone audit turns the fast-cloning workflow from a debt machine into a sustainable practice. Quarterly cleanups, queue-based rewrite-and-republish workflows and clean editor handoffs all become possible once you can see every clone as data rather than as a draft mixed in with everything else.
Questions
Common questions about SleekView for Yoast Duplicate Post
Only a small set of postmeta keys, primarily _dp_original which holds the source post ID, and _dp_is_rewrite_republish_copy which marks rewrite-and-republish drafts. SleekView uses those to identify clones, resolve sources and render the right tag for each row, without depending on any premium add-on.
Yes. SleekView only needs the meta keys the free Yoast Duplicate Post plugin already writes. There is no premium dependency on the Yoast side, and the free version covers the cases editorial teams actually run into: standard cloning, rewrite-and-republish and the meta tracking that goes with both flows.
No. Edits flow through the standard WordPress save path, the same way Yoast Duplicate Post expects. Inline updates to slug, status or author behave identically to changes made in the post editor, with the same capability checks, the same revisions and the same hook integration as any other post update.
Yes. The source column resolves the original post by ID and renders its title with a one-click jump. If a source has been deleted, the row shows a flagged orphan state, which is usually the cheapest cleanup signal: a clone whose source is gone is rarely worth keeping.
Yes. The _dp_is_rewrite_republish_copy meta key marks them, and SleekView surfaces those rows with a dedicated tag in the status column. Editorial leads can filter to that tag to manage the rewrite-and-republish workflow as its own queue separate from straight clone work.
Yes. Any filtered view can be exported as CSV with the columns and order you see on screen. Editorial leads typically use this to share quarterly cleanup proposals or to brief an external editor on the backlog of clone drafts before a focused sprint of work.
Yes. Yoast Duplicate Post and Yoast SEO are independent plugins despite the shared brand. SleekView reads only Duplicate Post's meta keys for this view, so the audit works on installs that run Yoast SEO, an alternative SEO plugin or no SEO plugin at all without configuration changes.
Yes. Yoast Duplicate Post can be enabled for any post type, and SleekView mirrors that. A site that clones products, case studies and standard posts can audit all three from the same ledger with post type as a filterable column or scope the table to one type at a time.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout