SleekView for Yoast Duplicate Post
SleekView reads the _dp_original and _dp_has_been_republished postmeta Yoast Duplicate Post writes on every clone, plus the dp_is_rewrite_republish_copy flag, and renders the result as a per-clone audit grid with source post, clone type, author and last edit inside WP Admin.
♾️ Lifetime License available
Cloning and rewriting are workflows. Read them as data.
Yoast Duplicate Post, originally by Joost de Valk and now maintained by the Yoast team, drives two workflows: a straight clone (Copy to a new draft) and Rewrite and Republish (clone, edit, merge back into the original on publish). Every clone gets a _dp_original postmeta entry pointing to its source ID, every rewrite copy carries the dp_is_rewrite_republish_copy flag, and once a republish is merged the original picks up _dp_has_been_republished.
SleekView reads those same meta keys and renders the result as a sortable workflow table. One row per clone, with columns for clone type (copy, active rewrite, merged republish), source post title, author, status, last modified and age in days since creation. Filter to active rewrites older than 30 days, scope to one author, sort by age to find rewrites that have stalled before merge. Editorial leads finally see where rewrites actually live.
Because the data is standard postmeta on regular post records, no extra tables are involved. The plugin keeps owning the Copy and Rewrite and Republish actions, the merge step on publish and the per-post UI; SleekView adds the workflow audit surface the standard post list cannot offer.
Workflow
How SleekView surfaces Yoast Duplicate Post data
Point at the duplicate meta
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical Yoast Duplicate Post clone audit view
wp_postmeta
| Clone | Source post | Clone type | Author | Status | Age (days) |
|---|---|---|---|---|---|
| 10 quick weeknight pasta recipes (Copy) | 10 quick weeknight pasta recipes | Rewrite | Anna L. | Draft | 42 |
| Spring sourdough starter guide (Copy) | Spring sourdough starter guide | Rewrite | Anna L. | Draft | 7 |
| Office redesign on a $500 budget | Office redesign on a $500 budget | Merged republish | Devon R. | Published | 12 |
| Founder interview: scaling to 50 staff (Copy) | Founder interview: scaling to 50 staff | Straight copy | Marie K. | Draft | 3 |
| Why we switched to four-day weeks (Copy) | Why we switched to four-day weeks | Rewrite | Marie K. | Draft | 61 |
Comparison
Default Yoast Duplicate Post admin vs SleekView
Default Yoast Duplicate Post admin
- Clones live in the standard post list with no aggregate workflow view
- Open rewrite copies blend in among normal drafts and get lost
- Source post column is not surfaced inline next to the clone
- Per-author rewrite rollups require raw SQL on postmeta
- No saved per-role view of the active rewrite queue
SleekView
- Source post, clone type and age in days as native columns
- Filter to active rewrites older than 30 days in a click
- Per-author and per-post-type rollups without custom code
- Saved views per role: editorial lead, content manager, agency report
- Same dataset the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for Yoast Duplicate Post
Workflow as real columns
Source post, clone type and republish status render as columns instead of clones blending into the standard wp-list-table among normal drafts.
Composable workflow filters
Stack filters on clone type, author, age and post type to land cohorts like stalled rewrites older than 30 days or per-author refresh queues in one query.
Export the queue
Any filtered view exports to CSV. The active-rewrites and stalled-rewrites lists become the next editorial retrospective rather than a screenshot tour.
Audience
Who uses SleekView for Yoast Duplicate Post
Editorial leads
Filter to active rewrites older than 30 days to catch stalled refreshes, then jump straight into the rewrite editor with one click on the clone title.
Content managers
Use the per-author column to spot writers actually driving refresh work versus writers always starting from a blank draft during a quarterly review cycle.
Agency consultants
Export the rewrite-in-flight list at the start of every retainer sprint and pair the clone-age column with the editorial calendar in a single review.
The bigger picture
Why duplicate posts are a workflow signal, not just noise
Yoast Duplicate Post is one of those quiet utilities that sits inside millions of WordPress installs and never gets its own dashboard. The Copy and Rewrite and Republish actions are workflow primitives the editorial team uses constantly, but the resulting clones blend into the regular post list. The cost is invisible: a rewrite started two months ago, never merged, slowly drifting from the original.
A new author who only ever creates fresh drafts instead of refreshing existing work. A content refresh quarter that nobody can prove actually happened. SleekView reads the same _dp_original and republish meta the plugin already writes and renders the result as a sortable workflow grid with source post, clone type, author and age.
Filters stack so the stalled-rewrites cohort, the per-author rollup and the post-type slices become one-click views. The plugin keeps owning the clone actions; editorial gets the workflow surface the standard post list cannot offer.
Questions
Common questions about SleekView for Yoast Duplicate Post
From wp_posts and wp_postmeta. Specifically _dp_original (source ID for a clone), dp_is_rewrite_republish_copy (flag for an active rewrite) and _dp_has_been_republished (flag on the original after a merge). No new tables and no separate sync layer.
Yes. Clone type is a native column with values straight copy, active rewrite and merged republish. The same field works as a filter and a group key for per-author or per-post-type rollups.
Yes. Group rows by post_author and surface the writers actually driving refresh work. The table respects the same WP capability layer the rest of SleekView uses, so editors only see their own scope when configured to.
Yes. Yoast Duplicate Post supports any post type that opts in, and the SleekView dataset picks up the _dp_original meta regardless of post type. Filter post_type to scope the table to products, docs or any custom type.
No. The plugin still owns the Copy and Rewrite and Republish actions, the merge step on publish and the per-post UI. SleekView adds the workflow audit surface the standard post list cannot offer.
No. The dataset is queried inside SleekView's own grid, not injected into the default WordPress post list. The plugin's own admin keeps working exactly as today.
Yes. Age in days is a computed column from post_date and serves as both a sort key and a filter. The over-30-days rewrites view is one click away and becomes the standard editorial retro starter.
Yes. Any filtered view exports to CSV with the columns the table shows. Editorial leads typically export the active-rewrites-older-than-30-days list as the start of every retrospective.
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