Duplicate Page Pro creates new wp_posts rows when you clone a page or custom post, copies the source's wp_postmeta, and records the original post ID via meta keys like _dp_original. The default WordPress posts list mixes those clones in with everything else, so editors lose track of which drafts are duplicates of which live pages.

SleekView reads the same wp_posts and wp_postmeta rows and joins each clone back to its source via the original-post meta key. Status, author, parent slug, and last modified date become first-class columns. Filters surface clones older than thirty days, drafts that were never published, and pages duplicated by users who have since left.

Inline edits route through the standard WordPress CRUD layer, so wp_insert_post and the usual save hooks still fire. Bulk delete, bulk trash, and bulk re-assign clean up duplicate sprawl in one pass instead of a hundred row clicks.

Duplicate Page Pro is brilliant for kicking off a new variation of a landing page, but it scatters partial drafts across wp_posts faster than most teams clean them up. Editors clone a page, abandon it after a campaign change, and the clone lingers forever in the default posts list with no link back to its origin. Over months that turns into hundreds of orphan rows that confuse search results, sitemaps, and editor handovers.

The standard WordPress admin has no concept of a clone, so the cleanup falls to whoever notices first. SleekView gives that audit a home: one grid that joins each clone to its source, surfaces the author and the date, and lets you trash or re-assign in bulk. Content teams reclaim hours every quarter and the live site stays tighter.

Site administrators get a repeatable review cycle they can hand to junior staff. The net effect is a smaller, healthier wp_posts table and editors who actually know which drafts matter.