Once you’ve configured a campaign the way you want it — with the right AI provider, tone presets, Base data schedule, category, Extra AI instructions — replicating that configuration for a second cluster is a chore if you do it from scratch. AI Content Generator’s clone feature copies every setting from an existing campaign into a new one, so you only have to change what actually needs to be different (usually just the Main keywords, the category and maybe the schedule).
This tutorial covers cloning end-to-end: how to trigger a clone, what gets copied and what doesn’t, the three practical patterns where cloning saves you an hour of setup, and the operational tip to keep clones from drifting apart when you update the original later.
How to trigger a clone
Go to AI Content Generator → Campaigns. Hover the campaign row you want to clone. In the row actions link list — where you’d normally see Edit / Quick Edit / Trash / View — click Clone. WordPress creates a new campaign with the same settings and opens it in the editor with title “Copy of [original name]”.
Rename it immediately (the campaign name is internal-only but you’ll be grateful later), change what needs to be different, save. The clone is now a standalone campaign — modifying it doesn’t affect the original.
What gets copied
- AI Provider selection and configuration overrides.
- Base data: content type, output status, articles per day, time window, minimum gap, active days, fixed times, jitter, blackout dates, catch-up checkbox, author mode.
- SEO brief (titles): main keywords, title instructions, audience, output language, language mode, translation model, anti-duplicates setting, how many titles to generate, title tone preset, additional tone notes.
- SEO brief (content): min/max words, content preset, tone preset.
- Featured image + inline images configuration.
- Live News Mode configuration (source, query, cadence, title preset).
- Extra AI instructions.
- Categories, tags.
What doesn’t get copied
- Generated titles in the queue (you start with an empty title queue on the clone).
- Article log and Campaign error log (these are per-campaign runtime data).
- Scheduled cron events (the clone doesn’t inherit the original’s next-run time).
Effectively: everything you configured in the editor gets copied; nothing that was generated at runtime does. That’s the right split — you clone a template, not a running state.
Pattern 1 — Adjacent topical cluster
You have a working “WordPress tutorials” campaign. You want a parallel “Shopify tutorials” campaign with the same tone and structure. Clone the first, change Main keywords (“Shopify” instead of “WordPress”), change the category, adjust the Extra AI instructions references, save. Total setup time: 2 minutes vs 30 for a fresh campaign.
Pattern 2 — A/B testing tone or provider
You want to A/B test “Neutral professional” vs “Authoritative / Expert” on the same keyword set. Clone the campaign, change only the Content tone preset on the clone, let both run for two weeks, compare in analytics. Same idea for A/B testing AI providers (Claude on original, GPT-4o on clone).
Pattern 3 — Multi-language rollout
You publish in English. You want to add Italian and Spanish. Clone the campaign twice — one clone per new language. On each clone, change Output language, verify Translation model is appropriate, change the category if you use language-specific categories, save. Three campaigns publishing in three languages from the same editorial voice.
Keep clones aligned: use Extra AI instructions as source of truth
The biggest risk with cloning is drift: you update the original’s Extra AI instructions six months later, forget to update the clones, and each starts producing subtly different output. Two practical habits.
- Keep a “master” Extra AI instructions block in a text file outside WordPress. When you edit it, copy-paste into every clone.
- Use campaign naming that surfaces the group: “Tutorials — EN”, “Tutorials — IT”, “Tutorials — ES”. At a glance you know which campaigns share DNA.
When NOT to clone
Cloning is wrong when the new campaign genuinely differs in most settings — different provider, different tone, different length band, different scheduling. Then cloning saves you 30 seconds but forces you to touch every field anyway. Fresh campaign wins.
Troubleshooting
- Clone link doesn’t appear — user doesn’t have the right capability. Grant edit_others_posts to the role or use an admin account.
- Cloned campaign doesn’t inherit AI Provider — global default override wasn’t set explicitly on the original. Set the provider explicitly, then clone.
- Categories missing on clone — the original had category IDs no longer present. Re-tick current categories.
You’re done
That’s cloning: right-click the row, hit Clone, rename, change what’s different, save. From here, adjacent clusters, A/B tests and multi-language rollouts each take 2 minutes instead of 30. The saved time compounds across every new campaign your editorial calendar demands.