Yoast Duplicate Post stores the original post's ID on every clone using the _dp_original postmeta key. Rewrite-and-republish copies add _dp_is_rewrite_republish_copy set to 1, plus _dp_has_rewrite_republish_copy on the original pointing back. Cloned drafts inherit content, featured images, postmeta, and taxonomies based on what you toggled in the plugin's settings page.

SleekAI maps those exact meta keys into the chatbot's system message. Editors can ask which posts in draft status are clones of a published piece, which rewrites are sitting unpublished, and whether a given live post has an active rewrite copy waiting. The bot pulls the parent post's title, status, and modification date from wp_posts for context.

Generic chatbots can't see _dp_original or the rewrite-republish flags at all. They look at a draft and see a regular draft, missing the lineage entirely. Editors then duplicate the same evergreen post three times by accident, or miss a rewrite that's been ready for republish for a week. SleekAI's variable mapper exposes the relationship, and display conditions keep the bot in WP Admin only so it doesn't surface internal lineage on the public site.

Yoast Duplicate Post is the most-installed clone plugin on WordPress for a reason: it solves a real workflow problem cleanly. The catch is that lineage is invisible. A draft titled "How to choose a CRM (rewrite)" looks identical to a draft someone wrote from scratch, unless you know to check the postmeta panel for _dp_is_rewrite_republish_copy.

That hidden lineage causes real pain on content-heavy sites: duplicate clones of the same evergreen piece pile up, rewrites get forgotten for weeks past their republish window, and editors waste time digging through draft lists. SleekAI reads _dp_original, _dp_is_rewrite_republish_copy, and _dp_has_rewrite_republish_copy directly. A single chat answers what's pending republish, which posts have stale clones, and who created each duplicate.

Display conditions keep the bot in WP Admin so the lineage data never leaks to the public site. Token usage stays low because most queries are short factual reads against indexed postmeta columns. You bring your own API key so per-seat pricing doesn't apply, and the read-only default means the bot can't accidentally delete a draft someone was about to republish.

For teams running monthly evergreen refresh cycles or template-driven publishing, that visibility into clone lineage saves an hour of digging every cleanup pass.