SleekView Feedback for Yoast Duplicate Post
Yoast Duplicate Post quietly stamps copies and rewrite drafts into wp_posts with a parent reference and a rewritten flag. SleekView Feedback turns that history into a sortable board so editors can vote on which clones survive, which rewrites ship, and which originals get retired.
♾️ Lifetime License available
From silent duplicate logs to a live editorial vote
Yoast Duplicate Post writes every clone and rewrite to wp_posts with a _dp_original meta key pointing back at the source. After six months on a busy editorial site you end up with dozens of orphan rewrite drafts, near duplicate landing pages, and old posts nobody can tell apart from their republished twins. The admin list is sorted by date, not by usefulness, so the cleanup never happens.
SleekView Feedback reads that same data and renders one card per clone, grouped by original, with a vote count, a status pill (draft, queued, published, killed), and a category tag for why it exists (rewrite, A/B, language copy, archive). Editors land on a single page, upvote the rewrites worth shipping, flag the duplicates that should be merged back, and leave a clear public trail of which clones earned their slot in the sitemap.
Votes write back to the postmeta column you map, so future Duplicate Post bulk actions can sort by score instead of by accident, and the editorial team finally has a shared view of what their clone graveyard actually contains.
Workflow
From Duplicate Post clones to a board
Point at the clone source
_dp_original is set, or filter to rewrite republish drafts only. You can scope by post type, author, or date window so the board only surfaces the clones your editors are currently reviewing.
Map vote, status, category
Embed on a private editor page
Votes write back to wp_postmeta
Sample board
Sample Yoast Duplicate Post review board
Comparison
Duplicate Post admin vs SleekView Feedback
Yoast Duplicate Post screens
- Clones land in the standard post list with no signal for which deserve to ship
- Rewrite republish drafts pile up with no shared queue or owner
- There is no way for editors to vote on which clones to keep or merge
- Status of every clone hides in row level meta only admins ever open
- Bulk delete is the only cleanup tool, so good rewrites get lost with the noise
SleekView Feedback
- One card per clone with title, votes, status pill, original link, and category tag
-
Upvote writes back to the
postmetacolumn you map, so Duplicate Post sees it too - Filter by status (draft, queued, published, killed) and by category tag
-
Works against any subset of
_dp_originalrows you query with a WHERE clause - Public or private board, perfect for internal editorial review or client sign off
Features
What SleekView Feedback gives you for Yoast Duplicate Post
Vote on every clone
Editors and reviewers see the full clone graveyard sorted by score. One click upvotes a rewrite worth shipping, downvotes a duplicate that should be merged. The numbers persist on the source row so the next bulk action sees the same data.
Filter by clone type
Slice the board by category tag (rewrite, A/B, translation, archive) or by status pill (draft, queued, published, killed). You can also filter to a single original post and see every descendant clone with its score in one column.
Two way sync with Yoast
Votes and status changes write straight back to the same postmeta or post status that Yoast Duplicate Post already uses. Nothing lives in a parallel SleekView database, so existing Duplicate Post bulk actions stay in sync.
Audience
Three ways teams run Duplicate Post boards
Editorial rewrite queue
Surface every rewrite republish draft on a single board. Editors upvote the ones ready to ship, leave low scoring drafts for revision, and the team finally has a shared queue instead of a Slack thread.
Rebrand cleanup
After a redesign you usually have hundreds of cloned landing pages. Use the board to flag duplicates for deletion, vote on which copy should be canonical, and run one informed bulk action when the dust settles.
Translation review
Cloned posts used as language stubs land on a board where translators upvote the ones ready for human review, flag the machine drafts that drifted, and clients sign off on what goes live in each locale.
The bigger picture
Why duplicate posts need a shared editorial vote
Yoast Duplicate Post is one of the most installed plugins on WordPress for a reason. It silently makes editorial work survivable. The trade off is that once your site has run for a few years, every author has cloned, rewritten, and forgotten dozens of posts.
The result is a sitemap full of near duplicates, a wp_posts table thick with rewrite drafts, and an editorial team that has no shared opinion on what should ship and what should die. The admin list view sorts by date, not by usefulness, and the bulk delete tool is binary. A SleekView Feedback board sits on top of that same data and gives every clone a public score.
Editors stop arguing in Slack and start voting on cards. Clients see exactly which rewrites are queued and which were rejected. Cleanup becomes an informed action rather than a quarterly panic.
Most importantly, the votes live on the same wp_postmeta column the plugin already reads, so the next Duplicate Post bulk action sees the score and acts on real signal instead of accident.
Questions
Common questions about SleekView Feedback for Yoast Duplicate Post
No. SleekView Feedback reads the same posts and meta that Duplicate Post writes. Votes update a postmeta column you map, status updates a post status or custom field. Duplicate Post keeps cloning and rewriting exactly as before, it just now sees a score column it can sort by.
Yes. Point SleekView at posts where _dp_is_rewrite_republish_copy is set, or filter by post status, post type, or any custom meta. Rewrite drafts, full clones, or both can sit on the same board with a category pill telling them apart.
You choose. Most teams pick an integer meta key on the cloned post itself, so the score lives next to the post and survives across plugin updates. SleekView writes through to the same key, so existing reports and bulk actions can read the votes too.
Both, on a per board basis. An internal editorial board can require logged in editor role and use one vote per user. A public client review board can allow guest votes throttled by IP and cookie. Each board has its own gating rules.
The card shows the original link as broken and the category pill switches to Orphaned if you configure that mapping. Editors can vote to delete the orphan clones or to promote one of them to the new canonical post, all from the board.
Yes. Each republish leaves a trail of meta on the original post. SleekView can render one card per republish event with the date, author, and the rewritten draft, so the board doubles as a republish changelog with votes.
Yes. SleekView exposes a sortable CSV and JSON export of every card with its current vote count, status, category, and author. Teams pipe that into Google Sheets for weekly editorial reviews or into the company BI tool for trend reporting.
Yes, because they live on wp_postmeta alongside the post itself. As long as posts and their meta migrate together, votes follow. SleekView reads votes on every page load, so nothing is cached outside the source row.
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