Bulk Generation

Bulk Generation creates several articles in one go from a list of keywords — instead of setting up each article individually, you enter up to 50 keywords and each one becomes its own article draft. In the background, every keyword runs through the same pipeline as single-article generation: first an outline (storyline) is generated, then the text is written section by section. The bulk itself and every article inside it carry their own status, which you can track live — if one keyword fails, the others keep running.

What it can do

• Up to 50 keywords per bulk (keywords[], at least 2 characters each) — every keyword becomes its own article draft.
• Fully asynchronous — runs as a background queue job, you can leave the page, progress is reloaded from the database.
• Two status layers: the bulk itself (pending → processing → completed/failed) and every individual item (pending → generating → completed/failed).
• Fault tolerance — one failed keyword doesn't block the others; the bulk is marked completed as soon as at least one article finished.
• Form options (UI only, not via the REST API): word count, style profile, content goal and link list as generation defaults.
• API options: article type (blog-post, guide, listicle) and language (de, en, es, fr) directly in the request.

When to use

• You want to produce 10, 20 or 30 articles for related keywords without kicking off each one individually.
• A site rollout or a new category needs several article drafts at once.
• You have a ready keyword list from Keyword Explorer and want to turn it into content directly.
• You don't need a fully automated, ongoing solution (that's Automation) but a one-off, controlled batch of new articles.

Workflow

1. Start a bulk — POST /v1/bulk-generations with {project_id, name, keywords: [...], type?, language?} → 202 with {bulk_id, total_articles}. Rate limit: max. 10 starts per minute.
2. Check status — GET /v1/bulk-generations/{bulk} returns the bulk including all items (status, keyword, article ID, credits spent, error message).
3. Overview — GET /v1/bulk-generations?project_id=&status= lists all bulks for the team, paginated.
4. Handle errors — items with status: failed carry an error_message; the remaining items in the same bulk keep running independently.
5. Continue processing — finished articles (items[].article_id) land as drafts in the project and can be sharpened further via, for example, Content Optimizer.

API

Bulk status values: pending, processing, completed, failed. Item status values: pending, generating, completed, failed.

Example:

POST /v1/bulk-generations
{
  "project_id": 42,
  "name": "August guide series",
  "keywords": ["descale water heater", "boiler maintenance", "tankless heater fault"],
  "language": "en"
}

Credits & Limits

• 4 credits per article (config/credits.php → bulk_generation_article), total price = keyword count × 4.
• On an API start, credits are fully deducted when the bulk is created; if the balance is insufficient, the endpoint returns 402 (insufficient_credits).
• Maximum 50 keywords per bulk call.
• Starting a bulk is rate-limited to 10 requests per minute.

Related modules

• Keyword Explorer — the typical source for the keyword list that feeds the bulk.
• Storylines — Bulk Generation uses the same outline-and-section pipeline internally.
• Content Optimizer — the natural next step to sharpen finished bulk drafts.
• Automation — once you no longer want to trigger this manually but keep it running automatically.