SleekView for Duplicate Page
SleekView identifies Duplicate Page clones from the slug and title patterns the plugin writes, joins them with author and modified date, and renders the whole clone backlog as a sortable, filterable table inside WP Admin.
♾️ Lifetime License available
Page clones become a queryable list
Duplicate Page is the simplest WordPress plugin in its category: one click on a page, post or custom post type, get a fresh draft copy. It is everywhere because it works. The problem is the same one every fast-cloning tool creates. Clones mix straight back into the Pages and Posts screens with no marker, no source reference and no easy way to filter them. A typical site running it for a year ends up with dozens of abandoned drafts that started as good ideas and never shipped.
SleekView identifies clones by the title and slug patterns Duplicate Page writes (the trailing -copy slug and the Copy of title prefix) and the optional duplicate_copy_of postmeta key. Title, source post, post type, author, status, modified date and age in days become first-class columns with sort, filter and bulk edit. An editorial lead can pull every clone in draft over 90 days, an admin can scope to a specific post type, and an agency can hand a client a single audit view ready for cleanup.
Nothing about the cloning workflow changes. The one-click duplicate stays where it is, the resulting drafts still go through the standard wp_posts save path, and editors keep editing them in the usual editor. SleekView adds the audit table the workflow has always needed.
Workflow
How SleekView surfaces Duplicate Page data
Identify clones
-copy slug pattern (configurable in settings) and a Copy of title prefix. SleekView matches both so every clone surfaces from wp_posts alone.
Join authors, dates and source
post_author, the last edit from post_modified and, when present, the source post from the duplicate_copy_of postmeta key.
Filter and sort like a database
Save and gate the view
Sample columns
A typical Duplicate Page audit view
wp_posts
| Title | Source | Type | Author | Status | Modified |
|---|---|---|---|---|---|
| Copy of Spring landing | Spring landing | page | Lena R. | Draft | 2026-04-22 |
| Copy of Pricing comparison | Pricing comparison | page | Marco D. | Draft | 2025-12-08 |
| Copy of Help center | Help center | page | Priya S. | Published | 2026-05-09 |
| Copy of Quarterly roundup | Quarterly roundup | post | Lena R. | Draft | 2025-09-14 |
| Copy of Contact | Contact | page | Marco D. | Draft | 2025-07-30 |
Comparison
Default Pages screen vs SleekView
Default Pages screen
- Clones mix with originals in the default list with no marker
- No filter for posts created via duplicate
- Per-author clone activity is invisible at any aggregate level
- Stale-clone counts are not exposed anywhere in the admin
- Cross-post-type clone reporting requires a custom WP_Query
SleekView
- Clone, source, author and status as sortable columns
- Filter to stale clones over a configurable age in one click
-
Bulk trash from the table through the standard
wp_trash_postpath - Saved views per role: admin audit, editor cleanup, agency client cleanup
- Same dataset the chart view reads, so audit and dashboard stay in sync
Features
What SleekView gives you for Duplicate Page
Clones as a measurable surface
Identify every -copy draft on the site, group them by author, type and age, and treat the pile as a queryable list rather than mixed-in noise in the default Pages screen.
Stale draft cleanup
Filter to status equals draft and modified more than 90 days ago, then bulk-trash from the table. The cleanup conversation starts from a real list, not a feeling.
Inline routes through WordPress
Bulk trash, edit and status changes all run through the standard WordPress save path, so capability checks, the recoverable trash workflow and any registered hooks continue to apply.
Audience
Who uses SleekView for Duplicate Page
Editorial cleanup
Pin a stale clone view to the dashboard, then trash the abandoned ones in bulk from the underlying table once a quarter.
Editor onboarding
Show new editors a real picture of how the team uses duplicate. Heaviest cloners surface as a sortable column, with workflow context for any onboarding conversation.
Agencies
Give clients a clone audit they can run themselves. Conversations about messy Pages screens become a table to share, not an SOS ticket.
The bigger picture
Why a tiny plugin needs a real audit table
Duplicate Page is one of the smallest plugins in any active WordPress install, and one of the most reached-for. Cloning a page for a regional variant, cloning a sales post for a follow-up campaign, cloning a template page to skip the layout work, all of it is a one-click action that the plugin nails. The downside is the one every cloning tool shares: the resulting drafts pile up.
A year of clones-as-a-habit leaves a site with dozens of stale pages mixed into the regular Pages screen, accidental publishes from the wrong copy and confusion about which version is canonical. SleekView reads the clones the plugin already produces and renders them as a scoped, sortable, filterable table. The clone audit becomes a routine view, the cleanup becomes a measurable sprint, and the workflow stays as fast as it ever was.
Questions
Common questions about SleekView for Duplicate Page
Duplicate Page writes the cloned post with a configurable suffix on the slug (often -copy or -copy-2) and a Copy of prefix on the title. SleekView matches both patterns out of wp_posts, with thresholds configurable per site to handle non-default suffixes.
Some versions of Duplicate Page leave a duplicate_copy_of postmeta key linking the clone to its source. SleekView reads that key when present and falls back to slug and title patterns otherwise, so the audit works regardless of which version is installed.
Yes. The free Duplicate Page plugin already writes the slug and title patterns the audit relies on, with no premium dependency. Pro extensions add settings such as redirect-after-duplicate, which become extra context but are not required for the table view.
Yes. Duplicate Page can be enabled for any post type, and SleekView reads the same post_type column wp_posts uses. Add a filter and the whole table narrows to pages, posts, products, case studies or any other type.
Yes. Multi-select rows in the table and trash them in bulk. The write goes through wp_trash_post, so capability checks, the standard trash workflow and any registered hooks continue to apply.
No. The audit identifies the clone pattern but the actions are filter-driven. Filter by status equals publish to scope to live clones, by modified to scope to actually stale ones, or exclude a specific author or category to protect intentional template content.
If the plugin version writes the duplicate_copy_of meta key, yes. SleekView resolves the source post by id and renders its title on the row. Versions without that meta key still get the rest of the audit through slug-pattern matching.
Yes. Any filtered view exports to CSV with the clone, source (where available), author, status and modified columns. Editorial leads use the export to brief writers on stale work before a cleanup sprint.
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