Bulk Publishing from a Keyword List
What it does: Paste up to 200 keywords — the AI writes every article (with SEO meta and optional images), sorts each into the right category, and publishes or drip-schedules them. Built for agencies.
Applies to Antradus AI Publisher v2.8.0 · Last updated 2026-08-28
Where it lives
Antradus AI → Bulk Publishing — a dedicated page whose first three tabs are ➕ New Batch, ⏳ Queue and 📊 Reports. The tabs beside them belong to other features on the same queue: 🎯 SEO Cluster, 📈 Trends, and on Studio the show pipeline.
Step by step
- Open ➕ New Batch and choose the AI-writing mode.
- Enter keywords, one line per article:
best budget espresso machines how to descale an espresso machine espresso vs drip coffee - Fine-grained control per line with pipes —
keyword | category | title:best budget espresso machines | Buying Guides | 7 Best Budget Espresso Machines We Actually Tested(Leave parts empty to let the AI decide:
keyword | | my exact titleworks too.)
An exact title is a promise the article must keep (v2.0.2): the writer receives it as a requirement, covers every product or model the title names (saying so explicitly when one lacks the capability), and derives the SEO keyphrase from it. - Pick the batch options (below) and start the batch.
- Watch progress in ⏳ Queue. Keeping that tab open is the fastest way to run a batch — see what happens when you close it before you walk away from a big one.
Batch options explained
| Option | What it does |
|---|---|
| Style / Tone / Language | Applies to every article in the batch |
| Publish status | Drafts (review first — recommended for new clients), publish immediately, or drip |
| Drip schedule | Spread the batch over time (pick the interval unit) — e.g. one post every 6 hours. Posts schedule natively; WordPress publishes them on time |
| Category | The fixed category for the whole batch. It follows the Post type box next to it, so choosing Product shows your product categories rather than your blog ones |
| AI categorizer | Files each post under one of your existing categories — and only invents a new category when nothing genuinely fits. Overrides the Category dropdown |
| Images | Off by default. Tick it to generate a featured image per post. Each image is a separate paid request on your provider account and slows every job down, so a 100-keyword batch means 100 extra image charges — leave it off for text-only batches and add images per post later. Image failures never kill an article; the post completes with a warning |
| Web search | Research each topic live before writing (details) |
💡 The topic suggester (content-gap finder)
No keyword list yet? Click 💡 Suggest topics:
- Give it a seed phrase ("home espresso").
- The AI reads your existing post titles and your categories, then proposes topics you haven’t covered — real gap-filling, not random ideas. Suggested titles must be honest (v2.0.2): specific products or models are only named in a title when they genuinely offer the capability it implies.
- Approve the ones you like — they’re written into the list (with suggested title + category) ready to run.
Allow NEW categories controls where suggested topics get filed. Ticked: each idea gets one of your existing categories only when its name genuinely describes the topic — otherwise the AI invents a fitting new one (marked new in the preview). Unticked: topics that match nothing get an empty category for you to fill in yourself. Either way, a topic is never forced into an unrelated category.
Managing a running batch (⏳ Queue tab)
- Live per-job status: queued → running → done (or failed with the reason).
- Interrupted jobs heal themselves (v2.0.2): if the server times out or restarts mid-article, the job is not lost — it’s automatically re-queued and finished on a later run (opening the Queue tab also triggers this recovery). A job that keeps getting interrupted is marked failed with an explanation, so nothing ever sits on "writing" forever.
- Retry failed re-queues only the failures.
- Cancel stops what hasn’t started; finished posts stay.
- Delete a batch’s records when you’re done with them.
What happens when you close the tab
Two things process your queue, and they are not equally reliable.
The tab you have open is the fast one. While the Queue tab is showing, it pulls one job after another as quickly as your provider answers. This is how a batch is meant to be run.
WordPress’s own scheduler is the fallback, and here is the part worth knowing: WordPress has no background service. What people call "WP-Cron" is a check that runs when someone loads a page on your site. Traffic is the clock.
That means:
| Your site | What happens with the tab closed |
|---|---|
| Live, with visitors | The queue keeps crawling forward on its own, roughly 2 articles a minute |
| Local (XAMPP / Local / MAMP), staging, or brand new with no visitors | Nothing happens at all until you load a page yourself |
This is normal WordPress behaviour, not a fault in the plugin — and it is why a batch can look frozen overnight on a site nobody visited.
The Queue tab tells you which situation you’re in (v2.3.0). A box at the top reports when the background runner last ran, and warns you in plain language when jobs are waiting and nothing is processing them.
What to do about it:
- Running a batch now? Leave the Queue tab open. Press ▶ Process now and let it work — this is always the fastest route.
- Want batches to finish overnight, unattended? Ask your host to run a real cron job every minute. Most managed WordPress hosts have a one-click setting for this; otherwise the command is
wp cron event run --due-now, or a scheduled request to your site’swp-cron.php. The Queue tab prints your exact URL so you can hand it over. - Drip-scheduled posts are not affected the same way. Once an article is written and given a future date, WordPress publishes it natively — though that too waits on a page load on a site with no traffic.
📊 Reports tab
Per-batch summary — written/failed counts and links to every created post — exportable as a CSV report you can send to a client. Full cost accounting is on the Reporting page.
Tips & gotchas
- Start with drafts for a new site or client — review a handful, tune your System Prompt if needed, then switch to publish/drip for the next batch.
- Drip + drafts don’t mix: drafts stay drafts (nothing auto-publishes that you marked for review).
- Keep the keyword lines specific — "espresso machine maintenance schedule" beats "coffee" 200 times.